[16NG] ARP and NAT for IPv4CS (removing or keeping)
Daniel Park <soohong.park@samsung.com> Thu, 20 December 2007 04:21 UTC
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1J5CuO-0000vB-G0; Wed, 19 Dec 2007 23:21:20 -0500
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
id 1J5CuN-0000v2-MU
for 16ng-confirm+ok@megatron.ietf.org; Wed, 19 Dec 2007 23:21:19 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1J5CuN-0000ut-8r
for 16ng@ietf.org; Wed, 19 Dec 2007 23:21:19 -0500
Received: from mailout1.samsung.com ([203.254.224.24])
by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5CuM-0007Zi-IZ
for 16ng@ietf.org; Wed, 19 Dec 2007 23:21:18 -0500
Received: from epmmp1 (mailout1.samsung.com [203.254.224.24])
by mailout1.samsung.com
(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
with ESMTP id <0JTB001ANYRHS6@mailout1.samsung.com> for 16ng@ietf.org;
Thu, 20 Dec 2007 13:21:17 +0900 (KST)
Received: from samsungcf414c4 ([168.219.198.109])
by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
2004))
with ESMTPA id <0JTB00I9VYRGUD@mmp1.samsung.com> for 16ng@ietf.org; Thu,
20 Dec 2007 13:21:16 +0900 (KST)
Date: Thu, 20 Dec 2007 13:21:05 +0900
From: Daniel Park <soohong.park@samsung.com>
To: 16ng@ietf.org
Message-id: <0JTB00I9WYRGUD@mmp1.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=ks_c_5601-1987
Content-transfer-encoding: 7BIT
Thread-index: AchCv7yCmeaGQWe9S6+Gp49n6wU53g==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [16NG] ARP and NAT for IPv4CS (removing or keeping)
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org
Folks, <chair hat on> At the last IETF, I got a rough consensus for pulling out ARP and NAT section from IPv4CS document. AFIAC, the most concerns on those parts are implementation specific, not part of RFC standard. This is an initial straw poll for 16ng folks consensus. What do you think ? <chair hat off> Personally, those parts can be included in the 16ng deployment scenario document if removed. That's my personal opinion on this subject. Daniel Park _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] ARP and NAT for IPv4CS (removing or keepin… Daniel Park
- Re: [16NG] ARP and NAT for IPv4CS (removing or ke… Jongtaek Oh