< draft-gont-numeric-ids-generation-02.txt   draft-gont-numeric-ids-generation-03.txt >
Network Working Group F. Gont Network Working Group F. Gont
Internet-Draft SI6 Networks / UTN-FRH Internet-Draft SI6 Networks / UTN-FRH
Intended status: Best Current Practice I. Arce Intended status: Best Current Practice I. Arce
Expires: September 1, 2018 Quarkslab Expires: September 12, 2019 Quarkslab
February 28, 2018 March 11, 2019
On the Generation of Transient Numeric Identifiers On the Generation of Transient Numeric Identifiers
draft-gont-numeric-ids-generation-02 draft-gont-numeric-ids-generation-03
Abstract Abstract
This document performs an analysis of the security and privacy This document performs an analysis of the security and privacy
implications of different types of "numeric identifiers" used in IETF implications of different types of "numeric identifiers" used in IETF
protocols, and tries to categorize them based on their protocols, and tries to categorize them based on their
interoperability requirements and the associated failure severity interoperability requirements and the associated failure severity
when such requirements are not met. Subsequently, it provides advice when such requirements are not met. Subsequently, it provides advice
on possible algorithms that could be employed to satisfy the on possible algorithms that could be employed to satisfy the
interoperability requirements of each identifier type, while interoperability requirements of each identifier type, while
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 1, 2018. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 52 skipping to change at page 2, line 52
Identifiers Categories . . . . . . . . . . . . . . . . . . . 19 Identifiers Categories . . . . . . . . . . . . . . . . . . . 19
9.1. Category #1: Uniqueness (soft failure) . . . . . . . . . 19 9.1. Category #1: Uniqueness (soft failure) . . . . . . . . . 19
9.2. Category #2: Uniqueness (hard failure) . . . . . . . . . 20 9.2. Category #2: Uniqueness (hard failure) . . . . . . . . . 20
9.3. Category #3: Uniqueness, constant within context (soft 9.3. Category #3: Uniqueness, constant within context (soft
failure) . . . . . . . . . . . . . . . . . . . . . . . . 20 failure) . . . . . . . . . . . . . . . . . . . . . . . . 20
9.4. Category #4: Uniqueness, monotonically increasing within 9.4. Category #4: Uniqueness, monotonically increasing within
context (hard failure) . . . . . . . . . . . . . . . . . 20 context (hard failure) . . . . . . . . . . . . . . . . . 20
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11. Security Considerations . . . . . . . . . . . . . . . . . . . 22 11. Security Considerations . . . . . . . . . . . . . . . . . . . 22
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
13.1. Normative References . . . . . . . . . . . . . . . . . . 23 13.1. Normative References . . . . . . . . . . . . . . . . . . 23
13.2. Informative References . . . . . . . . . . . . . . . . . 23 13.2. Informative References . . . . . . . . . . . . . . . . . 24
Appendix A. Flawed Algorithms . . . . . . . . . . . . . . . . . 27 Appendix A. Flawed Algorithms . . . . . . . . . . . . . . . . . 27
A.1. Predictable Linear Identifiers Algorithm . . . . . . . . 27 A.1. Predictable Linear Identifiers Algorithm . . . . . . . . 27
A.2. Random-Increments Algorithm . . . . . . . . . . . . . . . 28 A.2. Random-Increments Algorithm . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
Network protocols employ a variety of numeric identifiers for Network protocols employ a variety of numeric identifiers for
different protocol entities, ranging from DNS Transaction IDs (TxIDs) different protocol entities, ranging from DNS Transaction IDs (TxIDs)
to transport protocol numbers (e.g. TCP ports) or IPv6 Interface to transport protocol numbers (e.g. TCP ports) or IPv6 Interface
skipping to change at page 22, line 47 skipping to change at page 22, line 47
The entire document is about the security and privacy implications of The entire document is about the security and privacy implications of
identifiers. identifiers.
12. Acknowledgements 12. Acknowledgements
The authors would like to thank (in alphabetical order) Steven The authors would like to thank (in alphabetical order) Steven
Bellovin, Joseph Lorenzo Hall, Gre Norcie, and Martin Thomson, for Bellovin, Joseph Lorenzo Hall, Gre Norcie, and Martin Thomson, for
providing valuable comments on earlier versions of this document. providing valuable comments on earlier versions of this document.
The authors would like to thank Diego Armando Maradona for his magic
and inspiration.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, DOI 10.17487/RFC0793, September 1981, RFC 793, DOI 10.17487/RFC0793, September 1981,
<https://www.rfc-editor.org/info/rfc793>. <https://www.rfc-editor.org/info/rfc793>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
 End of changes. 8 change blocks. 
7 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/