[157066] in North American Network Operators' Group
Re: IPv4 address length technical design
daemon@ATHENA.MIT.EDU (William Herrin)
Thu Oct 4 16:34:48 2012
In-Reply-To: <E761E31A-92AC-48B8-B401-11AD49A37D09@consultant.com>
From: William Herrin <bill@herrin.us>
Date: Thu, 4 Oct 2012 16:34:17 -0400
To: Cutler James R <james.cutler@consultant.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Oct 4, 2012 at 4:17 PM, Cutler James R
<james.cutler@consultant.com> wrote:
> On Oct 4, 2012, at 4:00 PM, William Herrin <bill@herrin.us> wrote:
>> On Wed, Oct 3, 2012 at 7:12 PM, Cutler James R
>> <james.cutler@consultant.com> wrote:
>> Or did you mean use DNS as it fits in the current system, which
>> doesn't actually satisfy (1) at all since the layer 4 protocols
>> continue to build the connection identity from the layer 3 network
>> identity instead of the external host/service identity.
>>
> Why does the connection identity have to include the host identifier. Is that not a problem under the control of applications?
Nope. It's under the control of the layer 4 protocol, generally TCP or
UDP, and implemented at the OS level. For example, in TCP the
connection identity is composed of the source and destination IP
addresses and port numbers. Together, these 96 bits of information
comprise the unique identity of that TCP connection which the OS
matches to the socket number the application interacts with.
Regards,
Bill Herrin
--
William D. Herrin ................ herrin@dirtside.com bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
