From simon.perreault@viagenie.ca Wed Apr 11 11:17:35 2012 Return-Path: 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 708E411E80BB for ; Wed, 11 Apr 2012 11:17:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.575 X-Spam-Level: X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, NO_RELAYS=-0.001] 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 yARZgzVkYAGH for ; Wed, 11 Apr 2012 11:17:35 -0700 (PDT) Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id C927E11E808D for ; Wed, 11 Apr 2012 11:17:34 -0700 (PDT) Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:c44f:f235:37d9:77c2]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 041514009E for ; Wed, 11 Apr 2012 14:17:33 -0400 (EDT) Message-ID: <4F85CABD.4000604@viagenie.ca> Date: Wed, 11 Apr 2012 14:17:33 -0400 From: Simon Perreault User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: "behave@ietf.org" References: <20120411181500.18192.37775.idtracker@ietfa.amsl.com> In-Reply-To: <20120411181500.18192.37775.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20120411181500.18192.37775.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [BEHAVE] Fwd: New Version Notification for draft-perreault-behave-new-nat-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 18:17:35 -0000 Hi, We have just published the initial version of the new NAT MIB, as discussed in the interim meetings. Any comments would be highly appreciated. http://tools.ietf.org/html/draft-perreault-behave-new-nat-mib-00 Thanks, Simon, Tina, Senthil -------- Original Message -------- Subject: New Version Notification for draft-perreault-behave-new-nat-mib-00.txt Date: Wed, 11 Apr 2012 11:15:00 -0700 From: internet-drafts@ietf.org To: simon.perreault@viagenie.ca CC: ssenthil@cisco.com, tina.tsou.zouting@huawei.com A new version of I-D, draft-perreault-behave-new-nat-mib-00.txt has been successfully submitted by Simon Perreault and posted to the IETF repository. Filename: draft-perreault-behave-new-nat-mib Revision: 00 Title: Additional Definitions of Managed Objects for Network Address Translators (NAT) Creation date: 2012-04-11 WG ID: Individual Submission Number of pages: 17 Abstract: This memo defines a portion of the Management Information Base (MIB) for devices implementing Network Address Translator (NAT) function. This MIB module may be used for monitoring of a device capable of NAT function. The IETF Secretariat From dean.cheng@huawei.com Mon Apr 16 08:33:05 2012 Return-Path: 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 F3F5D21F8597 for ; Mon, 16 Apr 2012 08:33:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 J-INg3LXJV9R for ; Mon, 16 Apr 2012 08:33:04 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0ADB321F8593 for ; Mon, 16 Apr 2012 08:33:03 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AEY56258; Mon, 16 Apr 2012 11:33:03 -0400 (EDT) Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 16 Apr 2012 08:30:38 -0700 Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 16 Apr 2012 08:30:36 -0700 Received: from SZXEML523-MBX.china.huawei.com ([169.254.3.43]) by szxeml413-hub.china.huawei.com ([10.82.67.152]) with mapi id 14.01.0323.003; Mon, 16 Apr 2012 23:30:30 +0800 From: Dean cheng To: "behave@ietf.org" Thread-Topic: I-D Action: draft-cheng-behave-cgn-cfg-radius-ext-03.txt Thread-Index: AQHNG+Ni1KjeC6472Uext3pZGSw6oZadj6uA Date: Mon, 16 Apr 2012 15:30:29 +0000 Message-ID: Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.212.246.13] Content-Type: multipart/alternative; boundary="_000_DC7880973D477648AC15A3BA66253F68371A0F46szxeml523mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [BEHAVE] FW: I-D Action: draft-cheng-behave-cgn-cfg-radius-ext-03.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2012 15:33:05 -0000 --_000_DC7880973D477648AC15A3BA66253F68371A0F46szxeml523mbxchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We've just posted a new revision of the draft as draft-cheng-behave-cgn-cfg-radius-ext-03. The major changes are: 1) Med Boucadair joined us as co-author. 2) Changed the title of the draft. The proposed RADIUS attributes are now with a wider usage scope not only for CGN related applications, but in general for port-based device. 3) For the proposed Port-Session-Range Attribute, the code points have been changed so that both contiguous and non-contiguous port ranges are supported. 4) Section 4.2 is added to illustrate an application where the proposed RADIUS attributes are used in WiFi service deployment. Please provide comments. Cheers Dean -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] = On Behalf Of internet-drafts@ietf.org Sent: Monday, April 16, 2012 8:12 AM To: i-d-announce@ietf.org Subject: I-D Action: draft-cheng-behave-cgn-cfg-radius-ext-03.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : RADIUS Extensions for Port Set Configuration and Re= porting Author(s) : Dean Cheng Jouni Korhonen Mohamed Boucadair Filename : draft-cheng-behave-cgn-cfg-radius-ext-03.txt Pages : 24 Date : 2012-04-16 This document defines new RADIUS attributes that can be used by a device implementing port ranges to communicate with a RADIUS server to configure and/or report TCP/UDP port sets and ICMP identifiers mapping behavior for specific hosts. This mechanism can be used in various deployment scenarios such as CGN, NAT64, Provider WiFi Gateway, etc. This document does not make any assumption about the deployment context. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-cheng-behave-cgn-cfg-radius-ext-0= 3.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-cheng-behave-cgn-cfg-radius-ext-03= .txt _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --_000_DC7880973D477648AC15A3BA66253F68371A0F46szxeml523mbxchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We've jus= t posted a new revision of the

draft as draft-cheng-behave-cgn-cfg-radius-ext-03.

&nbs= p;

The major= changes are:

&nbs= p;

1)     Med Boucadair join= ed us as co-author.

2)     Changed the title = of the draft. The proposed RADIUS

attributes are now with a wider usage = scope not only

for CGN related applications, but in g= eneral for port-based

device.

3)     For the proposed P= ort-Session-Range Attribute, the

code points have been changed so that = both contiguous

and non-contiguous port ranges are sup= ported.

4)     Section 4.2 is add= ed to illustrate an application where

the proposed RADIUS attributes are use= d in WiFi service

deployment.

&nbs= p;

Please pr= ovide comments.

&nbs= p;

Cheers

Dean=

 

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] = On Behalf Of internet-drafts@ietf.org
Sent: Monday, April 16, 2012 8:12 AM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-cheng-behave-cgn-cfg-radius-ext-03.txt

 

 

A New Internet-Draft is available from the on-line Internet-Drafts = directories.

 

      Title     &= nbsp;     : RADIUS Extensions for Port Set Configuratio= n and Reporting

      Author(s)    &nb= sp;  : Dean Cheng

           &= nbsp;           &nbs= p;  Jouni Korhonen

           &= nbsp;            &nb= sp; Mohamed Boucadair

      Filename    &nbs= p;   : draft-cheng-behave-cgn-cfg-radius-ext-03.txt

      Pages     &= nbsp;     : 24

      Date     &n= bsp;      : 2012-04-16

 

   This document defines new RADIUS attributes that can b= e used by a

   device implementing port ranges to communicate with a = RADIUS server

   to configure and/or report TCP/UDP port sets and ICMP = identifiers

   mapping behavior for specific hosts.  This mechan= ism can be used in

   various deployment scenarios such as CGN, NAT64, Provi= der WiFi

   Gateway, etc.

 

   This document does not make any assumption about the d= eployment

   context.

 

 

 

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-cheng-behave-cgn-cfg-radi= us-ext-03.txt

 

Internet-Drafts are also available by anonymous FTP at:<= /span>

ftp://ftp.ietf.org/internet-drafts/

 

This Internet-Draft can be retrieved at:

ftp://ftp.ietf.org/internet-drafts/draft-cheng-behave-cgn-cfg-radiu= s-ext-03.txt

 

_______________________________________________

I-D-Announce mailing list

I-D-Announce@ietf.org

https://www.ietf.org/mailman/listinfo/i-d-announce

Internet-Draft directories: http://www.ietf.org/shadow.html

or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--_000_DC7880973D477648AC15A3BA66253F68371A0F46szxeml523mbxchi_-- From internet-drafts@ietf.org Tue Apr 17 08:04:45 2012 Return-Path: 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 DF00221F85A7; Tue, 17 Apr 2012 08:04:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.53 X-Spam-Level: X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, 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 yhGPA7onY+SF; Tue, 17 Apr 2012 08:04:41 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7010321F85AA; Tue, 17 Apr 2012 08:04:41 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120417150441.27259.40625.idtracker@ietfa.amsl.com> Date: Tue, 17 Apr 2012 08:04:41 -0700 Cc: behave@ietf.org Subject: [BEHAVE] I-D Action: draft-ietf-behave-nat-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 15:04:46 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Behavior Engineering for Hindrance Av= oidance Working Group of the IETF. Title : Additional Definitions of Managed Objects for Network Ad= dress Translators (NAT) Author(s) : Simon Perreault Tina Tsou Senthil Sivakumar Filename : draft-ietf-behave-nat-mib-00.txt Pages : 17 Date : 2012-04-17 This memo defines a portion of the Management Information Base (MIB) for devices implementing Network Address Translator (NAT) function. This MIB module may be used for monitoring of a device capable of NAT function. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-behave-nat-mib-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-behave-nat-mib-00.txt From iesg-secretary@ietf.org Tue Apr 24 10:44:14 2012 Return-Path: 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 87B5321E8090; Tue, 24 Apr 2012 10:44:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.511 X-Spam-Level: X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, 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 dLf3DIoLlXnc; Tue, 24 Apr 2012 10:44:14 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AFED21E809D; Tue, 24 Apr 2012 10:44:14 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: IESG Secretary To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 4.01p1 Message-ID: <20120424174414.15033.37196.idtracker@ietfa.amsl.com> Date: Tue, 24 Apr 2012 10:44:14 -0700 Cc: behave@ietf.org Subject: [BEHAVE] BEHAVE Working Group Virtual Interim Meeting: Thursday, May 17, 2012 X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2012 17:44:14 -0000 The BEHAVE working group will hold a virtual interim on Thursday, May = 17, 2012 at 7 AM PDT (2 PM UTC), using WebEx. Agenda and dialin information will be posted at: http://tools.ietf.org/wg/behave/trac/wiki From teemu.savolainen@nokia.com Thu Apr 26 00:43:23 2012 Return-Path: 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 8337C21F87AA for ; Thu, 26 Apr 2012 00:43:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 Hclje3BXouro for ; Thu, 26 Apr 2012 00:43:23 -0700 (PDT) Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id DA43C21F87A9 for ; Thu, 26 Apr 2012 00:43:22 -0700 (PDT) Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q3Q7gxAf027217 for ; Thu, 26 Apr 2012 10:43:17 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.24]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 26 Apr 2012 10:43:11 +0300 Received: from 008-AM1MPN1-053.mgdnok.nokia.com ([169.254.3.46]) by 008-AM1MMR1-008.mgdnok.nokia.com ([65.54.30.24]) with mapi id 14.02.0283.004; Thu, 26 Apr 2012 09:43:10 +0200 From: To: Thread-Topic: Two changes proposed for draft-ietf-behave-nat64-discovery-heuristic (to be done before interim) Thread-Index: Ac0jfQ6tEdy+1zC8SECLXrPNI+EhDw== Date: Thu, 26 Apr 2012 07:43:10 +0000 Message-ID: <916CE6CF87173740BC8A2CE4430969620434C8AE@008-AM1MPN1-053.mgdnok.nokia.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None; x-titus-version: 3.3.8.1 x-headerinfofordlp: None x-tituslabs-classificationhash-30: lRdGDfGIN8wlCPRly3WQX5iTbNGNoS7/2IqB+JMkzjIL76cx4P9mFZ/HRWEKNtCpF0ejvNb79eRLYPXoE0LJC8u0rY7SWONI0pTOIyBzmV0eKcxQ1O/nuPl57bEDRg0nJFFZ2iU9mjDvWTbW6iLr5BG3Ovj0lnFL+sC8j6OKzZxi2CcgjHXT7XLNwXCKeBZ6jLPI9lfcn5xARV8ehaUcvtdcUOCpTHDYNkog7YdBFt029mh6AfLeDpcie1aumlxriq3KQvDHvRbbdU5Cyidcpvnidlk792queKmyEoXUGKFUXKKdXPbu5nUUc0js+Lb4VBX/7LnaaVg/5Hkz9UxGlA== x-originating-ip: [10.163.16.185] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 26 Apr 2012 07:43:11.0884 (UTC) FILETIME=[3B2774C0:01CD2380] X-Nokia-AV: Clean Subject: [BEHAVE] Two changes proposed for draft-ietf-behave-nat64-discovery-heuristic (to be done before interim) X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2012 07:43:23 -0000 Hi, There are two issues we'd like to update for the draft-ietf-behave-nat64-di= scovery-heuristic before interim. Please comment. 1. Clarify that IANA needs to assign two IPv4 addresses for the well-known = name. I.e. update IANA section to say something like: -- This document requests IANA to assign at least one, but preferably two, pub= lic IPv4 addresses for the well-known name. The addresses must be reserved = from public IPv4 address space that is not allocated for any special use as= per RFC5735 section 3. This is because RFC6052 section 3.1 forbids IPv6 ad= dress synthesis using well-known prefix if IPv4 address is from any address= space described in the RFC5735 section 3. --=20 The RFC6052 section 3.1. limitation is quite hard, as it seems to rule out = use of 192.0.0.0/24 (and 240.0.0.0/4) address spaces even if I'm not sure t= hose are "non-global"? 2. Remove the infrastructure & volume comment from section 4: -- It is expected that volumes for well-known name related queries are roughly SOMETHING, TBD. The infrastructure required to serve well- known name is SOMETHING, TBD. -- At least I don't know what else to do, as we have not received any figures = for what kind of volumes there could be and what kind of infrastructure is = required... and if that information is really needed for protocol specifica= tion at first place. Best regards, Teemu=20 From sm@resistor.net Thu Apr 26 16:05:26 2012 Return-Path: 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 29C4A21E80B0 for ; Thu, 26 Apr 2012 16:05:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.552 X-Spam-Level: X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, 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 c0gl+2fEfVTE for ; Thu, 26 Apr 2012 16:05:23 -0700 (PDT) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2FA21E8029 for ; Thu, 26 Apr 2012 16:05:21 -0700 (PDT) Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3QN5Cuf003562; Thu, 26 Apr 2012 16:05:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1335481520; i=@resistor.net; bh=pB9jFlcQgF170JpGGqummjO2KrVeuAwSqQ3r/CSdi38=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Nu+3L17D8HLKpAiXlrB4c4oxPNkA+wCgd6dJcA3zTXrPkB6NOkFgwDiUzNPnBbreV afIteiuNO2A3YMi5mllLOsX+0dqdeU8rZ8zR4KmAAiDhGUfLnXIv6oT+7JQe0HGLRk V4bfsMQLEvMles1bruTI7SSn52POk8emhy1OnQPw= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1335481520; i=@resistor.net; bh=pB9jFlcQgF170JpGGqummjO2KrVeuAwSqQ3r/CSdi38=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y+eCx6G5MuNyE/tp0sZPQ2WXaCORI4kqHvKKLz8YOSSNEQAnTwIsUvVF9+Q/GQRQX KkQ1ypxf32HOWeduKoPF/WBcjsX2exdyqWjz7bsZhWDI8gUZ1PKi5SMm7/58mgzCHk FKBgoryrQfIQnpUyMRgstihS9FU2IjwgVspxEqhc= Message-Id: <6.2.5.6.2.20120426155411.09bbd820@resistor.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Thu, 26 Apr 2012 16:04:42 -0700 To: teemu.savolainen@nokia.com From: SM In-Reply-To: <916CE6CF87173740BC8A2CE4430969620434C8AE@008-AM1MPN1-053.m gdnok.nokia.com> References: <916CE6CF87173740BC8A2CE4430969620434C8AE@008-AM1MPN1-053.mgdnok.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: behave@ietf.org Subject: Re: [BEHAVE] Two changes proposed for draft-ietf-behave-nat64-discovery-heuristic (to be done before interim) X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2012 23:05:26 -0000 At 00:43 26-04-2012, teemu.savolainen@nokia.com wrote: >1. Clarify that IANA needs to assign two IPv4 addresses for the >well-known name. I.e. update IANA section to say something like: >-- >This document requests IANA to assign at least one, but preferably >two, public IPv4 addresses for the well-known name. The addresses >must be reserved from public IPv4 address space that is not >allocated for any special use as per RFC5735 section 3. This is >because RFC6052 section 3.1 forbids IPv6 address synthesis using >well-known prefix if IPv4 address is from any address space >described in the RFC5735 section 3. IANA does not get to choose. The draft asks and it does the assignment. IANA cannot assign an IPv4 address from 10/8, for example, as it is already reserved. The draft is supposed to specify how the IPv4 address is used. Instead of wordsmithing the IANA Considerations section, it's easier to focus on the other parts of the draft and fix that section once the IPv4 needs are clear. Regards, -sm From iesg-secretary@ietf.org Mon Apr 30 09:37:48 2012 Return-Path: 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 2E72621F8773; Mon, 30 Apr 2012 09:37:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.527 X-Spam-Level: X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, 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 n+Vsa91SWPog; Mon, 30 Apr 2012 09:37:47 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6A521F8778; Mon, 30 Apr 2012 09:37:47 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.02 Message-ID: <20120430163747.8753.84205.idtracker@ietfa.amsl.com> Date: Mon, 30 Apr 2012 09:37:47 -0700 Cc: behave mailing list , behave chair , RFC Editor Subject: [BEHAVE] Document Action: 'Analysis of solution proposals for hosts to learn NAT64 prefix' to Informational RFC (draft-ietf-behave-nat64-learn-analysis-03.txt) X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 16:37:48 -0000 The IESG has approved the following document: - 'Analysis of solution proposals for hosts to learn NAT64 prefix' (draft-ietf-behave-nat64-learn-analysis-03.txt) as Informational RFC This document is the product of the Behavior Engineering for Hindrance Avoidance Working Group. The IESG contact persons are Wesley Eddy and Martin Stiemerling. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-behave-nat64-learn-analysis/ Technical Summary Hosts and applications may benefit from the knowledge of whether an IPv6 address is synthesized, which would mean a NAT64 is used to reach the IPv4 network or Internet. This document analyses a number of proposed solutions for communicating whether the synthesis is taking place, the address format used, and the IPv6 prefix used by the NAT64 and DNS64. The solutions enable both NAT64 avoidance and intentional utilization by allowing local IPv6 address synthesis. The document concludes by recommending standardization of a heuristic discovery solution. Working Group Summary Concern was raised that we should define a new DNS resource record to retrieve this information, rather than concluding we should do a heuristic. The document explains why the working group reached the consensus to recommend a heuristic approach. Document Quality Authors would like to thank Dan Wing and Christian Huitema especially for the STUN idea and for their valuable comments and discussions. Personnel Document Shepherd: Dan Wing, dwing@cisco.com Responsible Area Director: David Harrington (ietfdbh@comcast.net) RFC Editor Note (1) Please re-include the Informative References that were part of version -02 of the document (section 10.2) but removed in version -03 (section 11.2): http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-nat64-learn-analysis-03.txt (2) In paragraph 5 of section 1, please change: "analyzes all known solutions proposals known" to: "analyzes all proposed solutions known" (3) In section 4, please change: "the Framework document" to: "the IPv4/IPv6 translation framework document" (4) In the Security Considerations, following the reference to RFC 6147, please add: "The document also talks about Man-in-the-middle and Denial-of-Service attacks caused by forging of information required for IPv6 synthesis from corresponding IPv4 addresses." (5) In the Security Considerations, please change: "unless DHCPv6 authentication or SEND are used)."" to: "unless DHCPv6 authentication (described in [RFC3315] or SEND [RFC3971] are used)." and add an Informative Reference to RFC 3315 and RFC 3971. (6) In the Security Considerations, please change: "authenticate all DNS responses" to: "authenticate all DNS responses (e.g. via DNSSEC [RFC4033]" and add an Informative Reference to RFC 4033. (7) In the Section 5.2.2 and 5.3.2 "cons" lists, please add: "- EDNS0 flags and options are typically hop-by-hop only, severely limiting the applicability of these approaches, unless the EDNS0 capable DNS64 is the first DNS server the end host talks to, as it is otherwise not possible to guarantee that the EDNS0 option survives through all DNS proxies and servers in between." (8) Please change the Abstract to: Hosts and applications may benefit from learning if an IPv6 address is synthesized and if NAT64 and DNS64 are present in a network. This document analyses a number of proposed solutions for detection of IPv6 address synthesis, IPv6 address format, and IPv6 prefix used for the protocol translation. These solutions enable both NAT64 avoidance and local IPv6 address synthesis. The document concludes by recommending the standardization of the heuristic discovery based approach. (9) Please remove the 3rd paragraph of Section 5.1.1