Re: [BEHAVE] NAPGT request for comments, THANKS!

Dan Wing <dwing@cisco.com> Tue, 16 July 2013 22:31 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312E721F9D8A for <behave@ietfa.amsl.com>; Tue, 16 Jul 2013 15:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.498
X-Spam-Level:
X-Spam-Status: No, score=-110.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 lfQ07f+ILF9M for <behave@ietfa.amsl.com>; Tue, 16 Jul 2013 15:31:11 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id CAFEE21F9F6E for <behave@ietf.org>; Tue, 16 Jul 2013 15:31:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3325; q=dns/txt; s=iport; t=1374013871; x=1375223471; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=/iJnIx2PLMgr1ncIKqSlDqVcNOLPH4Nlj4YHzU45OAo=; b=ABgBYKe9g57l5wJPgjCD4smiKFj3OUdRJjOqh766KPwhNw2buyDQSzHd be7ozLbi2n29D1ZIuSaKTYc1dklbpTGyhoegMTAM0A5O5ByLtOk4tDrXo ayBIv0Q5EDoczG/B4LagfkB2R0Y8rcrlM1kK6ZshIFLsGcYc64OCIf8lD E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAFAKHI5VGrRDoJ/2dsb2JhbABagwY0hRa0fYg9gQ8WdIIjAQEBAwF5BQsLBEJXGYgKBQ21TI4TgUgEBxaCdm0DiSeONYEpkCSDMhyBNQ
X-IronPort-AV: E=Sophos; i="4.89,679,1367971200"; d="scan'208,217"; a="83696027"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 16 Jul 2013 22:30:50 +0000
Received: from sjc-vpn3-945.cisco.com (sjc-vpn3-945.cisco.com [10.21.67.177]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6GMUkQ6003367; Tue, 16 Jul 2013 22:30:50 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_2F65D268-C10A-44CC-8D87-C5C08664C25F"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <OF36CCC8D7.D36790EB-ON48257BA9.0034A5D5-48257BA9.00357F94@zte.com.cn>
Date: Tue, 16 Jul 2013 15:30:49 -0700
Message-Id: <DD1BBBAF-661B-47CF-A329-032A7E04FA84@cisco.com>
References: <OF36CCC8D7.D36790EB-ON48257BA9.0034A5D5-48257BA9.00357F94@zte.com.cn>
To: meng.wei2@zte.com.cn
X-Mailer: Apple Mail (2.1508)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAPGT request for comments, THANKS!
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 22:31:16 -0000

On Jul 15, 2013, at 2:43 AM, meng.wei2@zte.com.cn wrote:

>     I have submitted a new draft. The objective is to solve a problem that 
>     prevents an external client from accessing an internal server. 
> 
>     https://datatracker.ietf.org/doc/draft-meng-behave-napgt/ 
> 
>     I expect your comments. Thanks a lot! 

Draft-meng-behave-napgt appears to describe something that is very similar to the long-standing "DMZ host" configuration available on almost all residential-class NAT devices.  I don't think we could standardize that behavior, but perhaps that is possible.

Draft-meng-behave-napgt also describes an update to the port assignment behavior described in http://tools.ietf.org/html/rfc5382#section-7.1 (TCP) and http://tools.ietf.org/html/rfc4787#section-4.2.1 (UDP).  If I understand Section 4 of draft-meng-behave-napgt properly, it is saying that NATs should not assign ports below 1024 to dynamic connections.  This might be something worth considering for draft-ietf-behave-requirements-update?

-d