#IRAPP THIN CLIENT HOW TO#

FIREWALL AND SYSTEM ADMINISTRATORS SHOULD * * CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF * * THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER * * REGISTERED OR NOT. ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN * * ENDORSEMENT OF AN APPLICATION OR PRODUCT, AND THE FACT THAT NETWORK * * TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT * * IT IS 'GOOD' TRAFFIC. THE IANA WILL ASSIGN * * THE NUMBER FOR THE PORT AFTER YOUR APPLICATION HAS BEEN APPROVED. UNASSIGNED PORT NUMBERS SHOULD NOT BE USED. THIS ALLOCATION SHOULD NOT * * BE AUTOMATIC, BUT MAY OCCUR UPON APPLICATION BY AN INTERESTED * * PARTY WHOSE APPLICATION WOULD OTHERWISE FIT IANA'S POLICIES.

************************************************************************ * PLEASE NOTE THE FOLLOWING: * * * * IESG STATEMENT TO THE IANA * * THE IESG BELIEVES THAT IANA MAY ALLOCATE AN ADDITIONAL PORT IN * * THE 'USER PORT' RANGE TO PROTOCOLS WHOSE CURRENT PORT ALLOCATION * * REQUIRES ACCESS TO A PRIVILEGED PORT.

The Dynamic and/or Private Ports are those from 49152 through 65535 A value of 0 in the port numbers registry below indicates that no port has been allocated. The registration procedure is defined in, Section 19.9. The Registered Ports are those from 1024 through 49151 DCCP Registered ports SHOULD NOT be used without IANA registration. DCCP Well Known ports SHOULD NOT be used without IANA registration. The Well Known Ports are those from 0 through 1023. PORT NUMBERS (last updated ) The port numbers are divided into three ranges: the Well Known Ports, the Registered Ports, and the Dynamic and/or Private Ports.

Irapp thin client