Re: Guidance needed on well known ports
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guidance needed on well known ports



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, all,

In response to some discussion on this mailing list, the following ID
has been submitted. It's intended to become a TCPM work item (thus the
header) if there's sufficient interest.

PLEASE TAKE FURTHER DISCUSSION TO THAT LIST (tcpm at ietf.org)

For the original discussion, see the ietf at ietf.org archives, and look
for "Guidance needed on well known ports".

The draft available at the following URL until it's in the ID repositories:
http://www.isi.edu/touch/pubs/draft-touch-tcp-portnames-00.txt

Joe

- ----

TCPM WG                                                        J. Touch
Internet Draft                                                  USC/ISI
Expires: October 2006                                    April 14, 2006

                        A TCP Option for Port Names
                     draft-touch-tcp-portnames-00.txt
...
Abstract

   This document specifies a new TCP option that specifies services by a
   string name. This option separates the use of port numbers for
   connection demultiplexing from their use as a service identifier. The
   option allows a larger number of concurrent connections for a
   particular service, as well as potentially enabling more explicitly
   coordination of services behind NATs and firewalls. This option
   should be supported in new TCP implementations.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEQCY0E5f5cImnZrsRAsCqAKDOYDDorIRcA04GDZBTtWX2NUfHKQCfbfi3
qVbx2jZQAcPDyeo+5/2x35Y=
=wJb2
-----END PGP SIGNATURE-----

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.