IETF Logo Mail Archive

[midcom] Port preservation

"Yutaka Takeda" <takeday@pcrla.com> Fri, 23 April 2004 19:21 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02402 for <midcom-archive@odin.ietf.org>; Fri, 23 Apr 2004 15:21:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH61c-0002Tt-Kk for midcom-archive@odin.ietf.org; Fri, 23 Apr 2004 15:07:48 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NJ7mRY009491 for midcom-archive@odin.ietf.org; Fri, 23 Apr 2004 15:07:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH5lQ-00067j-4f; Fri, 23 Apr 2004 14:51:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH5IY-0001sT-NH for midcom@optimus.ietf.org; Fri, 23 Apr 2004 14:21:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24861 for <midcom@ietf.org>; Fri, 23 Apr 2004 14:21:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BH5IW-0006Nf-5L for midcom@ietf.org; Fri, 23 Apr 2004 14:21:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BH5HY-00069B-00 for midcom@ietf.org; Fri, 23 Apr 2004 14:20:13 -0400
Received: from 67.105.118.114.ptr.us.xo.net ([67.105.118.114] helo=mail.kmerl.com) by ietf-mx with esmtp (Exim 4.12) id 1BH5HE-0005ue-00 for midcom@ietf.org; Fri, 23 Apr 2004 14:19:52 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
x-mimeole: Produced By Microsoft Exchange V6.0.6249.0
Date: Fri, 23 Apr 2004 11:19:21 -0700
Message-ID: <B002AA5B97382E40935F83502A566F20010CAF@mail.kmerl.com>
Thread-Topic: Port preservation
Thread-Index: AcQpX37U9XM5Ab20Ss6rfFdN0kbryg==
From: Yutaka Takeda <takeday@pcrla.com>
To: Midcom <midcom@ietf.org>, stun@www.vovida.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [midcom] Port preservation
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Does anyone know what the real motivation for NAT designers to 
implement the port preservation[1] is? Is there an actual service 
or application that depends on this behavior? I just realized that 
I know such NATs exist but why...

[1] http://www.ietf.org/internet-drafts/draft-jennings-midcom-stun-results-00.txt

Yutaka

_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom

v2.23.0 | Report a Bug | By Email