Re: [Int-area] introducing a new IPv4 option [was RE: [BEHAVE] Revealing identity of TCP client connection when sharing IPv4 address]
jnc@mercury.lcs.mit.edu (Noel Chiappa) Tue, 05 October 2010 23:54 UTC
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 059263A6E87 for <int-area@core3.amsl.com>; Tue, 5 Oct 2010 16:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.135
X-Spam-Level:
X-Spam-Status: No, score=-6.135 tagged_above=-999 required=5 tests=[AWL=0.464, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMVjZvTAFYnS for <int-area@core3.amsl.com>; Tue, 5 Oct 2010 16:54:25 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id D28813A6E10 for <int-area@ietf.org>; Tue, 5 Oct 2010 16:54:24 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E9B786BE567; Tue, 5 Oct 2010 19:55:22 -0400 (EDT)
To: int-area@ietf.org
Message-Id: <20101005235522.E9B786BE567@mercury.lcs.mit.edu>
Date: Tue, 05 Oct 2010 19:55:22 -0400
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [Int-area] introducing a new IPv4 option [was RE: [BEHAVE] Revealing identity of TCP client connection when sharing IPv4 address]
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 23:54:26 -0000
> From: Bob Hinden <bob.hinden@gmail.com> > At the IP and Transport level functionality, the IPv4 Internet is > essentially frozen somewhere in the 1990's. It's certainly difficult to introduce change, but not impossible - one just has to be smarter, and be prepared to live with some ugliness (and non-optimality) in some aspects of one's protocol. Noel
- Re: [Int-area] introducing a new IPv4 option [was… Noel Chiappa
- Re: [Int-area] introducing a new IPv4 option [was… Noel Chiappa
- Re: [Int-area] introducing a new IPv4 option [was… Noel Chiappa
- Re: [Int-area] introducing a new IPv4 option [was… Joel Jaeggli