[sunset4] FW: draft-li-behave-NAT444-Test and draft-tsou-stateless-nat44

"George, Wes" <wesley.george@twcable.com> Wed, 11 July 2012 14:23 UTC

Return-Path: <wesley.george@twcable.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7593921F86CE for <sunset4@ietfa.amsl.com>; Wed, 11 Jul 2012 07:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.679
X-Spam-Level:
X-Spam-Status: No, score=-0.679 tagged_above=-999 required=5 tests=[AWL=-0.215, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BhnVDmxaRguY for <sunset4@ietfa.amsl.com>; Wed, 11 Jul 2012 07:23:25 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 9C41A21F8691 for <sunset4@ietf.org>; Wed, 11 Jul 2012 07:23:25 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.77,567,1336363200"; d="scan'208";a="390907812"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 11 Jul 2012 10:23:47 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Wed, 11 Jul 2012 10:23:52 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "sunset4@ietf.org" <sunset4@ietf.org>
Date: Wed, 11 Jul 2012 10:23:50 -0400
Thread-Topic: draft-li-behave-NAT444-Test and draft-tsou-stateless-nat44
Thread-Index: Ac1fcMoO82YK7HwnScqfG82fGbA0+Q==
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791745B84055@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sunset4] FW: draft-li-behave-NAT444-Test and draft-tsou-stateless-nat44
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sunset4>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 14:23:26 -0000

The answers to our questions on two drafts are below. Please review and comment on the content of the answers, either together or separately. I'd like some discussion on the draft or the questions on-list before we get into the meeting.

Thanks

Wes George


-----Original Message-----
From: Will Liu (Shucheng) [mailto:liushucheng@huawei.com]
Sent: Wednesday, July 11, 2012 5:42 AM
To: George, Wes
Cc: sunset4-chairs@tools.ietf.org
Subject: Asking for two 10min slots

Hi George,

Thanks for your kindly reminding. Sorry for my carelessness. :D May I ask for 2 time slots for draft-Li-Behave-NAT444-Test-00 and draft-tsou-stateless-nat44?Each presentation would last for 10min and the presenter will be Will Liu.

Following are my answers to your three question for both drafts:
Q:
1) describe the problem to be solved and show that there is widespread demand for a solution
2) demonstrate that the problem can not be solved with existing technologies
3) provide a description of the proposed solution along with its impact on current IPv4-only use and justification that it does not harm or delay the deployment of IPv6

A:
draft-Li-Behave-NAT444-Test-00
1) NAT444 is a common scenario in operators’ network.  Operators are worried whether applications will be affected when they pass though multi-level NAT. This test document provides experiences for both operators and researchers.
2) During testing, we find some problems such as QQ online Gaming doesn’t permit two user with the same public IP address in same game room.
3) This is a testing draft. Proposed solution is not related.

draft-tsou-stateless-nat44-00
1)  To let the NAT44 CGN simple, to reduce the cost of CGN. Different from traditional NAT44: no per-session state on the CGN, no binding table, no per-flow state to be maintained, zero log, high speed, easy to deploy hot backup.
2)  Traditional NAT44 CGN need per-session state on the CGN, binding table, per-flow state to be maintained. These make the CGN expensive and difficult to achieve CGN hot backup.
3)  Solve the exhaustion of IPv4 address when the network migrate to IPv6. Because it is stateless, the ISPs don’t need too much cost to deploy it. It can also be implemented in dual-stack network(IPv4 traffic pass through stateless NAT44 and IPv6 traffic pass by stateless NAT44), so the network can migrate to IPv6 smoothly.

Regards,
Will


-----Original Message-----
From: George, Wes [mailto:wesley.george@twcable.com]
Sent: Wednesday, July 11, 2012 12:48 PM
To: Will Liu (Shucheng); sunset4-chairs@tools.ietf.org
Subject: RE: Asking for a 10min slot

Please see the message I sent to the list this AM.

Thanks,

Wes

> -----Original Message-----
> From: Will Liu (Shucheng) [mailto:liushucheng@huawei.com]
> Sent: Tuesday, July 10, 2012 5:30 AM
> To: sunset4-chairs@tools.ietf.org
> Subject: Asking for a 10min slot
>
> Hi Chairs,
>
> I am writing to ask for a 10 min slot for a presentation for
> draft-tsou- stateless-nat44.
> Presenter name is Will Liu and length of presentation is 10 minutes.
> Thanks.
>
> Have a nice day!
> Will

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.