TSVWG J. Touch
Internet Draft USC/ISI
Intended status: Best Current Practice March 25, 2015
Expires: September 2015
Recommendations on Using Assigned Transport Port Numbers
draft-ietf-tsvwg-port-use-10.txt
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 25, 2015.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Touch Expires September 25, 2015 [Page 1]Internet-Draft Recommendations for Transport Port Use March 2015Abstract
This document provides recommendations to application and service
protocol designers on how to use the assigned transport protocol
port number space and when to request a port assignment from IANA.
It provides designer guidelines on how to interact with the IANA
processes defined in RFC6335, thus serving to complement (but not
update) that document.
Table of Contents
1. Introduction...................................................2
2. Conventions used in this document..............................3
3. History........................................................3
4. Current Port Number Use........................................5
5. What is a Port Number?.........................................5
6. Conservation...................................................7
6.1. Guiding Principles........................................7
6.2. Firewall and NAT Considerations...........................8
7. Considerations for Requesting Port Number Assignments..........9
7.1. Is a port number assignment necessary?....................9
7.2. How Many Assigned Port Numbers?..........................11
7.3. Picking an Assigned Port Number..........................12
7.4. Support for Security.....................................13
7.5. Support for Future Versions..............................14
7.6. Transport Protocols......................................15
7.7. When to Request an Assignment............................16
7.8. Squatting................................................17
7.9. Other Considerations.....................................18
8. Security Considerations.......................................18
9. IANA Considerations...........................................19
10. References...................................................19
10.1. Normative References....................................19
10.2. Informative References..................................20
11. Acknowledgments..............................................22
1. Introduction
This document provides information and advice to application and
service designers on the use of assigned transport port numbers. It
provides a detailed historical background of the evolution of
transport port numbers and their multiple meanings. It also provides
specific recommendations to designers on how to use assigned port
numbers. Note that this document provides information to potential
port number applicants that complements the IANA process described
in BCP165 [RFC6335], but it does not change any of the port number
Touch Expires September 25, 2015 [Page 2]