
From wwwrun@core3.amsl.com  Tue Jun  1 12:51:36 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 4FAE03A6A5A; Tue,  1 Jun 2010 12:51:35 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100601195136.4FAE03A6A5A@core3.amsl.com>
Date: Tue,  1 Jun 2010 12:51:36 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-address-format (IPv6 Addressing of IPv4/IPv6 Translators) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Jun 2010 19:51:36 -0000

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'IPv6 Addressing of IPv4/IPv6 Translators '
   <draft-ietf-behave-address-format-08.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-15. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-address-format-08.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=19017&rfc_flag=0


From wwwrun@core3.amsl.com  Tue Jun  1 12:53:15 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id E49E93A6A99; Tue,  1 Jun 2010 12:53:15 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100601195315.E49E93A6A99@core3.amsl.com>
Date: Tue,  1 Jun 2010 12:53:15 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-dns64 (DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Jun 2010 19:53:16 -0000

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'DNS64: DNS extensions for Network Address Translation from IPv6 
   Clients to IPv4 Servers '
   <draft-ietf-behave-dns64-09.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-15. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-dns64-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18762&rfc_flag=0


From wwwrun@core3.amsl.com  Tue Jun  1 13:04:00 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id A7A553A6A6C; Tue,  1 Jun 2010 13:04:00 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100601200400.A7A553A6A6C@core3.amsl.com>
Date: Tue,  1 Jun 2010 13:04:00 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-v6v4-framework (Framework for IPv4/IPv6 Translation) to Informational RFC
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Jun 2010 20:04:00 -0000

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'Framework for IPv4/IPv6 Translation '
   <draft-ietf-behave-v6v4-framework-09.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-15. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-framework-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18851&rfc_flag=0


From wwwrun@core3.amsl.com  Tue Jun  1 13:16:07 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id BC0333A6AD8; Tue,  1 Jun 2010 13:16:07 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100601201607.BC0333A6AD8@core3.amsl.com>
Date: Tue,  1 Jun 2010 13:16:07 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-v6v4-xlate (IP/ICMP Translation Algorithm) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Jun 2010 20:16:07 -0000

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'IP/ICMP Translation Algorithm '
   <draft-ietf-behave-v6v4-xlate-20.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-15. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-20.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18712&rfc_flag=0


From wwwrun@core3.amsl.com  Tue Jun  1 13:17:13 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 867C53A6AF3; Tue,  1 Jun 2010 13:17:13 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100601201713.867C53A6AF3@core3.amsl.com>
Date: Tue,  1 Jun 2010 13:17:13 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-v6v4-xlate-stateful (Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Jun 2010 20:17:13 -0000

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'Stateful NAT64: Network Address and Protocol Translation from IPv6 
   Clients to IPv4 Servers '
   <draft-ietf-behave-v6v4-xlate-stateful-11.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-06-15. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-stateful-11.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18764&rfc_flag=0


From lars.eggert@nokia.com  Wed Jun  2 08:38:30 2010
Return-Path: <lars.eggert@nokia.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 928E028C136 for <behave@core3.amsl.com>; Wed,  2 Jun 2010 08:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.926
X-Spam-Level: 
X-Spam-Status: No, score=-5.926 tagged_above=-999 required=5 tests=[AWL=0.673,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VPqqzsr5wLFk for <behave@core3.amsl.com>; Wed,  2 Jun 2010 08:38:28 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id D4E4528C13B for <behave@ietf.org>; Wed,  2 Jun 2010 08:38:27 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o52FbuC7026272 for <behave@ietf.org>; Wed, 2 Jun 2010 18:38:10 +0300
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Jun 2010 18:37:41 +0300
Received: from mgw-sa01.ext.nokia.com ([147.243.1.47]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 2 Jun 2010 18:37:32 +0300
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa01.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o52FbWOv025686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <behave@ietf.org>; Wed, 2 Jun 2010 18:37:32 +0300
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.1 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/signed; boundary=Apple-Mail-55-833102519; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <D6FC8B15-3506-4546-B0B9-AA593211EB0A@nokia.com>
Date: Wed, 2 Jun 2010 18:37:25 +0300
Message-Id: <467D00E1-4061-4E27-838E-EFC37BB2212F@nokia.com>
References: <D6FC8B15-3506-4546-B0B9-AA593211EB0A@nokia.com>
To: IETF BEHAVE WG <behave@ietf.org>
X-Mailer: Apple Mail (2.1078)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (mail.fit.nokia.com); Wed, 02 Jun 2010 18:37:25 +0300 (EEST)
X-OriginalArrivalTime: 02 Jun 2010 15:37:32.0551 (UTC) FILETIME=[845A1970:01CB0269]
X-Nokia-AV: Clean
Cc: nat-study@fit.nokia.com
Subject: Re: [BEHAVE] wanted: your old NAT home router
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: nat-study@fit.nokia.com
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Jun 2010 15:38:30 -0000

--Apple-Mail-55-833102519
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

FYI, a first report with test results for 34 devices is available =
athttp://fit.nokia.com/lars/tmp/2010-hgw-study.pdf. Slides that =
summarize the results are at =
http://fit.nokia.com/lars/tmp/2010-hgw-study-slides.pdf.

We have received another 30-odd devices as donations, which we'll add to =
the testbed and include in a follow-up study.

If you have an unused, spare home gateway to donate to this effort, =
please contact us at nat-study@fit.nokia.com. We're also interested in =
obtaining a DSLAM and a CMTS.

Thanks,
Lars


On 2010-4-29, at 12:36, Lars Eggert wrote:
> Hi,
>=20
> for a measurement study done together with Markku Kojo's team at the =
University of Helsinki, we're looking to collect as many different NAT =
home routers as possible. If you have an old clunker lying around =
somewhere, please contact me off-list. I'll cover shipping via DHL. Feel =
free to forward this email as you see fit.
>=20
> The boxes will find a permanent home at the University of Helsinki. =
Study results will be published openly. The intent is that this =
collection become a resource for the community to be shared for future =
studies.=20
>=20
> Caveat: The boxes should NAT between Ethernet interfaces - we don't =
have DSL or cable access equipment in the lab setup at the moment.
>=20
> Thanks,
> Lars


--Apple-Mail-55-833102519
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAyUw
ggKOoAMCAQICEAdjk36sXKbnVn15S0/qUp0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDYxNTExMjYxNFoXDTEwMDYxNTExMjYx
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA7mR8A+Pn0/FsUkMX6Pyjw+FL3IFcJk8GaKV5VJ40TMI0Wh8oq20cqA9X
uqnVDW9WztKwH+o+msJenLwWpprbpJm4TImYGbnUJxYyN8gb81aiX1Bw2xCpJ5z3H2+8DsReJLuY
Rdl4bVvaIxLIL4odmfsRwzPyNkOK8LRtfl6OPcaDOlFWzbikULfIVGGu7BqK4lxQSpYwwpZkOMOB
6nnBSfUOtBEmqO+qZG/nL/JxWFV5vxQgg4XHbsMMTxFf6+ji18BD09BUIfDLTuJoCzFmQhrM9vLT
VuRhHWSL20LoafGjXv6mPt3i9IGJHpVb2dMQUgOgRyWHTKiUJVU/rUTdWwIDAQABo14wXDAqBgUr
ZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCAGA1UdEQQZMBeBFWxhcnMu
ZWdnZXJ0QG5va2lhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADUx+67n98wt
I1vydB90HeSZP4Y64VCxxb0NxGGFvfc2+JdVKeHJ/xT+l+ygYKsWNwJJprkPi4WZ5G0crkq4VK1H
5drEJIztpSPVfWI05vPidaaGuuuCR+6MvJMtOTEYEvc/6eovBnkrzRf9x5x5EyuJXAWTeuBADg80
QI3vQ1tZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT
BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg
Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIG
A1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h
bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjEL
MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV
BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUA
A4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAK
MNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAw
QwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJl
ZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl
TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9M
Ibj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq
BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAHY5N+rFym51Z9eUtP
6lKdMAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTEwMDYwMjE1MzcyNlowIwYJKoZIhvcNAQkEMRYEFJoA/7CTZENg1kye943u+sPtPRn+MIGF
BgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu
ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD
QQIQB2OTfqxcpudWfXlLT+pSnTCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQB2OTfqxcpudWfXlLT+pSnTANBgkqhkiG9w0BAQEF
AASCAQCH1zqLHoKU004lWKVXyp2mIXC77lBVVPrCa4g8INekrnq6bmmrmsMXhzUOpQfPR7+w+II3
VqUYXTeaM5hsXKkuTa44fNL3vE+Rud4+e7izUEo1cYVZS0r61HC5ykaq+RoSJKCNdi5FgQHA4gG8
1CwYdj37q++2euzfytoyBjTNu852rJ8Vh7LyteOLXYpb7R8kkoMU6kf1tL6SPlJ6P62yum9PA859
g6pNJSwYvcyM5Q6ltyq5TBmHakshoy2qSiTSD0ATKu9WBOT5gKoXUBPb8GAqKsS1AilOn8dwoR3C
ybpNnheLTr1NxqNe018RO5jXXyhled0ZSKxzv5fRFKKiAAAAAAAA

--Apple-Mail-55-833102519--

From rpenno@juniper.net  Wed Jun  2 15:23:57 2010
Return-Path: <rpenno@juniper.net>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1901728C14D for <behave@core3.amsl.com>; Wed,  2 Jun 2010 15:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzHxBmsouqaN for <behave@core3.amsl.com>; Wed,  2 Jun 2010 15:23:56 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by core3.amsl.com (Postfix) with ESMTP id CA5A728C119 for <behave@ietf.org>; Wed,  2 Jun 2010 15:23:49 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKTAbZ6OuIZMuvTR8pCnMyRqmolQ1FVDye@postini.com; Wed, 02 Jun 2010 15:23:43 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 2 Jun 2010 15:20:37 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 2 Jun 2010 18:20:36 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: "nat-study@fit.nokia.com" <nat-study@fit.nokia.com>, Lars Eggert <lars.eggert@nokia.com>, IETF BEHAVE WG <behave@ietf.org>
Date: Wed, 2 Jun 2010 18:20:34 -0400
Thread-Topic: [BEHAVE] wanted: your old NAT home router
Thread-Index: AcsCaaMotnchqXDmRUGXLFwZICGcyQAOC533
Message-ID: <C82C2742.1FDC7%rpenno@juniper.net>
In-Reply-To: <467D00E1-4061-4E27-838E-EFC37BB2212F@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.4.0.100208
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BEHAVE] wanted: your old NAT home router
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Jun 2010 22:23:57 -0000

Very interesting and useful. Some of the issues are not surprising though
(timeouts a classic example), but eager to see follow up results.

Have you looked at this page by any chance? They a mile long page of CPE
tests.

http://nattest.net.in.tum.de/?mod=3Dresults

Thanks,

Reinaldo


On 6/2/10 8:37 AM, "Lars Eggert" <lars.eggert@nokia.com> wrote:

> Hi,
>=20
> FYI, a first report with test results for 34 devices is available
> athttp://fit.nokia.com/lars/tmp/2010-hgw-study.pdf. Slides that summarize=
 the
> results are at http://fit.nokia.com/lars/tmp/2010-hgw-study-slides.pdf.
>=20
> We have received another 30-odd devices as donations, which we'll add to =
the
> testbed and include in a follow-up study.
>=20
> If you have an unused, spare home gateway to donate to this effort, pleas=
e
> contact us at nat-study@fit.nokia.com. We're also interested in obtaining=
 a
> DSLAM and a CMTS.
>=20
> Thanks,
> Lars
>=20
>=20
> On 2010-4-29, at 12:36, Lars Eggert wrote:
>> Hi,
>>=20
>> for a measurement study done together with Markku Kojo's team at the
>> University of Helsinki, we're looking to collect as many different NAT h=
ome
>> routers as possible. If you have an old clunker lying around somewhere,
>> please contact me off-list. I'll cover shipping via DHL. Feel free to fo=
rward
>> this email as you see fit.
>>=20
>> The boxes will find a permanent home at the University of Helsinki. Stud=
y
>> results will be published openly. The intent is that this collection bec=
ome a
>> resource for the community to be shared for future studies.
>>=20
>> Caveat: The boxes should NAT between Ethernet interfaces - we don't have=
 DSL
>> or cable access equipment in the lab setup at the moment.
>>=20
>> Thanks,
>> Lars
>=20


From lars.eggert@nokia.com  Wed Jun  2 22:46:47 2010
Return-Path: <lars.eggert@nokia.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F0323A68F1 for <behave@core3.amsl.com>; Wed,  2 Jun 2010 22:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.962
X-Spam-Level: 
X-Spam-Status: No, score=-5.962 tagged_above=-999 required=5 tests=[AWL=0.637,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lqe26WbOMoRn for <behave@core3.amsl.com>; Wed,  2 Jun 2010 22:46:44 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 9BA403A67F3 for <behave@ietf.org>; Wed,  2 Jun 2010 22:46:43 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o535kILs029343; Thu, 3 Jun 2010 08:46:27 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Jun 2010 08:45:56 +0300
Received: from mgw-sa02.ext.nokia.com ([147.243.1.48]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 3 Jun 2010 08:45:56 +0300
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa02.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o535jslm026225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jun 2010 08:45:54 +0300
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.1 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/signed; boundary=Apple-Mail-6-883999158; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <C82C2742.1FDC7%rpenno@juniper.net>
Date: Thu, 3 Jun 2010 08:45:42 +0300
Message-Id: <D60A37DE-9800-4F98-B871-85E2EE2E940E@nokia.com>
References: <C82C2742.1FDC7%rpenno@juniper.net>
To: Reinaldo Penno <rpenno@juniper.net>
X-Mailer: Apple Mail (2.1078)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (mail.fit.nokia.com); Thu, 03 Jun 2010 08:45:43 +0300 (EEST)
X-OriginalArrivalTime: 03 Jun 2010 05:45:56.0359 (UTC) FILETIME=[0962C970:01CB02E0]
X-Nokia-AV: Clean
Cc: nat-study@fit.nokia.com, IETF BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] wanted: your old NAT home router
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 03 Jun 2010 05:46:47 -0000

--Apple-Mail-6-883999158
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2010-6-3, at 1:20, Reinaldo Penno wrote:
> Have you looked at this page by any chance? They a mile long page of =
CPE
> tests.
>=20
> http://nattest.net.in.tum.de/?mod=3Dresults

no, I haven't - thanks for the link! I know Georg Carle and will follow =
up with him.

Lars=

--Apple-Mail-6-883999158
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAyUw
ggKOoAMCAQICEAdjk36sXKbnVn15S0/qUp0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDYxNTExMjYxNFoXDTEwMDYxNTExMjYx
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA7mR8A+Pn0/FsUkMX6Pyjw+FL3IFcJk8GaKV5VJ40TMI0Wh8oq20cqA9X
uqnVDW9WztKwH+o+msJenLwWpprbpJm4TImYGbnUJxYyN8gb81aiX1Bw2xCpJ5z3H2+8DsReJLuY
Rdl4bVvaIxLIL4odmfsRwzPyNkOK8LRtfl6OPcaDOlFWzbikULfIVGGu7BqK4lxQSpYwwpZkOMOB
6nnBSfUOtBEmqO+qZG/nL/JxWFV5vxQgg4XHbsMMTxFf6+ji18BD09BUIfDLTuJoCzFmQhrM9vLT
VuRhHWSL20LoafGjXv6mPt3i9IGJHpVb2dMQUgOgRyWHTKiUJVU/rUTdWwIDAQABo14wXDAqBgUr
ZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCAGA1UdEQQZMBeBFWxhcnMu
ZWdnZXJ0QG5va2lhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADUx+67n98wt
I1vydB90HeSZP4Y64VCxxb0NxGGFvfc2+JdVKeHJ/xT+l+ygYKsWNwJJprkPi4WZ5G0crkq4VK1H
5drEJIztpSPVfWI05vPidaaGuuuCR+6MvJMtOTEYEvc/6eovBnkrzRf9x5x5EyuJXAWTeuBADg80
QI3vQ1tZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT
BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg
Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIG
A1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h
bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjEL
MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV
BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUA
A4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAK
MNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAw
QwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJl
ZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl
TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9M
Ibj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq
BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAHY5N+rFym51Z9eUtP
6lKdMAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTEwMDYwMzA1NDU0MlowIwYJKoZIhvcNAQkEMRYEFPZhbo/P+XnCleuCpd1JX+bpbPVNMIGF
BgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu
ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD
QQIQB2OTfqxcpudWfXlLT+pSnTCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQB2OTfqxcpudWfXlLT+pSnTANBgkqhkiG9w0BAQEF
AASCAQDrsjg0VDu4zM6VDzkAFkBeZq+qcZmbIJCn9VbjLlrqCzNUiLYOU2m1le5Mc9A5CW4v4vhw
DGf+My5WgJQOecLEI1Rhg2IcrxiWnJhGYFc7D9TzKbTg9IX/MjVVKrPQnEitl5HeCnXw1jRCwpXU
myJ0jHGh1zmgvDFSDe7HqDfv12B4cYLcpoKwp1KGfUpgzQTLEcx35LGESKiEmfLeuCad7wmyulxm
87eU2S/ej397CYxcdOh5HZYUVCPFjG2x96qhAn0yvWHv+9/lRLcNq4COgjn7vwMOPPn+FiFGAbE1
Os6pNQX8ukj5Y9XiisnL09PLz5kl6+LL6h2OjErDTNxBAAAAAAAA

--Apple-Mail-6-883999158--

From pekkas@netcore.fi  Thu Jun  3 02:07:22 2010
Return-Path: <pekkas@netcore.fi>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D61CE28C0F3; Thu,  3 Jun 2010 02:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[AWL=0.700,  BAYES_50=0.001, GB_I_LETTER=-2, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28OHvnTsW6K5; Thu,  3 Jun 2010 02:07:21 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 288AB3A694E; Thu,  3 Jun 2010 02:07:19 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id o5396pif006526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jun 2010 12:06:51 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id o5396ofD006522; Thu, 3 Jun 2010 12:06:51 +0300
Date: Thu, 3 Jun 2010 12:06:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
In-Reply-To: <20100601201713.867C53A6AF3@core3.amsl.com>
Message-ID: <alpine.LRH.2.00.1006031204440.6191@netcore.fi>
References: <20100601201713.867C53A6AF3@core3.amsl.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: clamav-milter 0.96 at otso.netcore.fi
X-Virus-Status: Clean
Cc: draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org, behave@ietf.org, behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] Last Call: draft-ietf-behave-v6v4-xlate-stateful (Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 03 Jun 2010 09:07:23 -0000

On Tue, 1 Jun 2010, The IESG wrote:
> - 'Stateful NAT64: Network Address and Protocol Translation from IPv6
>   Clients to IPv4 Servers '
>   <draft-ietf-behave-v6v4-xlate-stateful-11.txt> as a Proposed Standard

I've reviewed draft-ietf-behave-v6v4-xlate-stateful-11 for ops-dir.

I believe the document is ready for publication, but there are a couple
of areas where minor clarifications could improve the document.

As a general comment, spec has good detail (esp S 3.5) on how to 
handle TCP, UDP and ICMP query traffic, but I did not find similar 
detail on how ICMP errors sent in response to such traffic would 
affect packet processing, state tables, etc.

It would be great if e.g. TCPM WG reviewed Section 3.5.2, especially its
state table and said it's OK. There could be a number of unthought-of
cornercases.

>From O&M perspective, the specification appears to be sufficiently operable
and configurable in IPv6->IPv4 translation. IPv4->IPv6 translation requires
manually configured or unspecified bindings. Operationally this is not going
to be sufficiently as the management interface is unspecified and e.g. MIB
module or other configuration methods do not exist and are not in Behave WG
charter.  But this issue should not delay the publication of this document
and rather should be tackled later, if needed.

The default TCP maximum session lifetime is 2 hours (from RFC5382). I
personally believe this is too small for long-lived sessions.

some detailed comments:
-----------------------

    This document may contain material from IETF Documents or IETF
    Contributions published or made publicly available before November
    10, 2008. [...]

.. which material is potentially covered by this?  While the non-WG version
was available prior to Nov 10, 2008, the authors should be able to say so.
It would be better if this disclaimer could be removed.  License info is
also an older version (from id-nits checker).

In S 3.4:

    If the incoming packet is an IPv6 packet that contains a protocol
    other than TCP, UDP or ICMPv6 in the last Next Header, then the
    packet SHOULD be discarded and, if the security policy permits, the
    NAT64 SHOULD send an ICMPv6 Destination Unreachable error message
    with Code 3 (Destination Unreachable) to the source address of the
    received packet.  NOTE: This behaviour may be updated by future
    documents that define how other protocols such as SCTP or DCCP are
    processed by NAT64.

.. I suppose this assumes the packet is unicast, as NAT64 is an unicast-only
specification. Nonetheless I'd suggest that somewhere (probably earlier in
the spec) you'd explicitly say about one sentence on multicast; it's
currently not mentioned at all.  E.g. "A NAT64 device MUST ignore any
translation or actions when IPv4 or IPv6 destination address is a multicast
or the limited broadcast address (255.255.255.255)." (maybe with more
precise definition what to do instead.)

The same applies but more strongly to the following IPv4 paragraph.  More
strongly because IPv4 spec does not allow generating ICMPv4's in response to
multicast packets while in ICMPv6 this is acceptable under certain
conditions.

NB: I see that IPv6 destination address is covered under 2nd paragraph of S
3.5 but a more explicit mention might be worthwhile.

In S 3.5.1:

       *  The STE destination IPv4 transport is set to (Z(Y'),y), y being
          the same port as the STE destination IPv6 transport address and
          Z(Y') being algorithmically generated from the IPv6 destination
          address (i.e.  Y') using the reverse algorithm as specified in
          Section 3.5.4.

.. S 3.5.2 can hardly be said to specify any algorithm, but it certainly
doesn't even mention the reverse algorithm (however trivial it might be).

In S 3.5.2:

       V4 SYN RCV: An IPv4 packet containing a TCP SYN was received by
       the NAT64, implying that a TCP connection is being initiated from
       the IPv4 side.  The NAT64 is now waiting for a matching IPv6
       packet containing the TCP SYN in the opposite direction.
...
    A TCP segment with the SYN flag set that is received through the IPv6
    interface is called a V6 SYN, similarly, V4 SYN, V4 FIN, V6 FIN, V6
    FIN + V4 FIN, V6 RST and V4 RST.

.. this is somewhat confusing because you appear to be using "V4 SYN RCV" to
mean "only SYN flag set" (due to "being initiated from ...") while "V4 SYN"
later means "SYN [and possibly ACK] flag set". The same applies to V6 of course.
Maybe reword?  Maybe "being initiated from.." and this distinction is not
even necessary, because you don't have it on V4 FIN RCV side either? (Though
when creating sessions, the semantics differ slightly depending on the
initiator.)

V4 FIN RCV, V6 FIN RCV and V4 FIN + V6 FIN are listed in the state diagram
without "RCV" keyword, and this should be corrected.

I'm also a bit hesitant to include 4 min T.O., 2hrs etc. in the diagram as
these seem to be certain _minimum_ values and the implementation would be
free to use some other values as well.  More general description would be
slightly better.

A cornercase from specification language point of view are those TCP flags
that could at least in theory be applicable alongside "state flags": URG and
PSH.

In S 3.5.2.2:

          +  The STE transport IPv6 source address is left unspecified
             and may be populated by other protocols out of the scope of
             this specification.


... what does leaving source address unspecified mean in the context of TCP
session table searches, packets on the wire etc.?

          The lifetime of the STE entry is set to TCP_INCOMING_SYN as per
          [RFC5382] and the packet is stored.  The result is that the
          NAT64 will not drop the packet based on the filtering, nor
          create a BIB entry.  Instead, the NAT64 will only create the
          session table entry and store the packet.  The motivation for
          this is to support simultaneous open of TCP connections.

... for how long is the packet supposed to be stored?  Will it ever be sent
out on the wire? If yes, what will replace the "unspecified" IPv6 source
address then?  If not, what's the point of storing a packet in the first
place (instead of just creating a state entry and dropping it)?  An explicit
reference how the packet processing continues could be useful here (it seems
it does not continue).  The same also applies in the case a TCP BIB entry
exist (similar description).

    *** ESTABLISHED ***

    If a V4 FIN packet is received, the packet is translated and
    forwarded.  The state is moved to V4 FIN RCV.

    If a V6 FIN packet is received, the packet is translated and
    forwarded.  The state is moved to V6 FIN RCV.

.. I suppose you're referring here to _only_ FIN flag set. Does a V4 FIN
packet with FIN+ACK flag set more the state to V4 FIN RCV?

In S 3.5.3,

           If the packet is discarded, then an ICMP error message
       MAY be sent to the original sender of the packet, unless the
       discarded packet is itself an ICMP message.

.. there are copy/paste/logical errors here, and this also seems to apply to
similar sections on UDP (at least).  First of all, under UDP section, isn't
it already known which kind of packet is in question?  Isn't the 
"itself an ICMP message" condition wrong and should be "itself an ICMP error
message"?  Is it intentional that the "ICMP packet" condition is different
for BIB entry search and address-dependent filtering search?

S 3.5.3 deals with ICMP Query sessions, so from that perspective, this
should always result in an ICMP error message generation?

In S 3.6.1:

    When translating in the IPv4 --> IPv6 direction, let the incoming
    source and destination transport addresses in the 5-tuple be (S,s)
    and (D,d) respectively.  The outgoing source transport address is
    computed as follows:

       The outgoing source transport address is generated from S using
       the address transformation algorithm described in Section 3.5.4.

       The BIB table is searched for an entry (X',x) <--> (D,d), and if
       one is found, the outgoing destination transport address is set to
       (X',x).

.. you don't mention what happens if an entry is not found in the BIB table.
(maybe the assumption is that you should never arrive at this step if the BIB
entry does not exist..) -- the same also applies in 3.6.2.

5.3.  Attacks on NAT64

.. it might be worth also mentioning the "packet is stored" case already
mentioned above in the context of simultaneous opens.

editorial:
----------

In S 3.2 also later:

(X',Y',I1) <--> (T,Z,I2)

.. because ICMP identifier corresponds to a port number in some sense, and
port numbers are designated with lower-case letters, I wonder if in this
case as well it would be better to use 'i1' and 'i2'.

*  The NAT64 MAY require that the UDP, TCP, or ICMP header be
          completely contained within the fragment that contains OFFSET
          equal to zero.

s/OFFSET/fragment offset/

    o  When the protocol following the IP header is ICMP (Sections 3.4
       and 4.4) and it is an ICMP error message, the source and
       destination transport addresses in the embedded packet are set to
       the destination and source transport addresses from the outgoing
       5-tuple (note the swap of source and destination).

.. you're referring to S 3.4 & S 4.4 of [I-D.ietf-behave-v6v4-xlate], not
this document, and this may be confusing.  But reference to S 3.4 and 4.4
appears to be redundant and could maybe be removed here altogether.

    [I-D.ietf-mmusic-ice]
               Rosenberg, J., "Interactive Connectivity Establishment
               (ICE): A Protocol for Network Address Translator (NAT)
               Traversal for Offer/Answer Protocols",
               draft-ietf-mmusic-ice-19 (work in progress), October 2007.

.. now published as an RFC.

From marcelo@it.uc3m.es  Thu Jun  3 04:41:52 2010
Return-Path: <marcelo@it.uc3m.es>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AC6A3A679F; Thu,  3 Jun 2010 04:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.999
X-Spam-Level: 
X-Spam-Status: No, score=-107.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CDrYVziYstsk; Thu,  3 Jun 2010 04:41:50 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id EF7C328C0F8; Thu,  3 Jun 2010 04:41:49 -0700 (PDT)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro.local (127.30.18.95.dynamic.jazztel.es [95.18.30.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id AF65DBDECF9; Thu,  3 Jun 2010 13:41:29 +0200 (CEST)
Message-ID: <4C0794E8.8090007@it.uc3m.es>
Date: Thu, 03 Jun 2010 13:41:28 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; es-ES; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <20100601201713.867C53A6AF3@core3.amsl.com> <alpine.LRH.2.00.1006031204440.6191@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.1006031204440.6191@netcore.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.0.0.1038-17422.003
Cc: behave@ietf.org, draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org, ietf@ietf.org, behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] Last Call: draft-ietf-behave-v6v4-xlate-stateful (Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 03 Jun 2010 11:41:52 -0000

Thanks for the review. I will address the comments and come back to you.

Regards, marcelo



El 03/06/10 11:06, Pekka Savola escribió:
> On Tue, 1 Jun 2010, The IESG wrote:
>> - 'Stateful NAT64: Network Address and Protocol Translation from IPv6
>>   Clients to IPv4 Servers '
>> <draft-ietf-behave-v6v4-xlate-stateful-11.txt> as a Proposed Standard
>
> I've reviewed draft-ietf-behave-v6v4-xlate-stateful-11 for ops-dir.
>
> I believe the document is ready for publication, but there are a couple
> of areas where minor clarifications could improve the document.
>
> As a general comment, spec has good detail (esp S 3.5) on how to 
> handle TCP, UDP and ICMP query traffic, but I did not find similar 
> detail on how ICMP errors sent in response to such traffic would 
> affect packet processing, state tables, etc.
>
> It would be great if e.g. TCPM WG reviewed Section 3.5.2, especially its
> state table and said it's OK. There could be a number of unthought-of
> cornercases.
>
>> From O&M perspective, the specification appears to be sufficiently 
>> operable
> and configurable in IPv6->IPv4 translation. IPv4->IPv6 translation 
> requires
> manually configured or unspecified bindings. Operationally this is not 
> going
> to be sufficiently as the management interface is unspecified and e.g. 
> MIB
> module or other configuration methods do not exist and are not in 
> Behave WG
> charter.  But this issue should not delay the publication of this 
> document
> and rather should be tackled later, if needed.
>
> The default TCP maximum session lifetime is 2 hours (from RFC5382). I
> personally believe this is too small for long-lived sessions.
>
> some detailed comments:
> -----------------------
>
>    This document may contain material from IETF Documents or IETF
>    Contributions published or made publicly available before November
>    10, 2008. [...]
>
> .. which material is potentially covered by this?  While the non-WG 
> version
> was available prior to Nov 10, 2008, the authors should be able to say 
> so.
> It would be better if this disclaimer could be removed.  License info is
> also an older version (from id-nits checker).
>
> In S 3.4:
>
>    If the incoming packet is an IPv6 packet that contains a protocol
>    other than TCP, UDP or ICMPv6 in the last Next Header, then the
>    packet SHOULD be discarded and, if the security policy permits, the
>    NAT64 SHOULD send an ICMPv6 Destination Unreachable error message
>    with Code 3 (Destination Unreachable) to the source address of the
>    received packet.  NOTE: This behaviour may be updated by future
>    documents that define how other protocols such as SCTP or DCCP are
>    processed by NAT64.
>
> .. I suppose this assumes the packet is unicast, as NAT64 is an 
> unicast-only
> specification. Nonetheless I'd suggest that somewhere (probably 
> earlier in
> the spec) you'd explicitly say about one sentence on multicast; it's
> currently not mentioned at all.  E.g. "A NAT64 device MUST ignore any
> translation or actions when IPv4 or IPv6 destination address is a 
> multicast
> or the limited broadcast address (255.255.255.255)." (maybe with more
> precise definition what to do instead.)
>
> The same applies but more strongly to the following IPv4 paragraph.  More
> strongly because IPv4 spec does not allow generating ICMPv4's in 
> response to
> multicast packets while in ICMPv6 this is acceptable under certain
> conditions.
>
> NB: I see that IPv6 destination address is covered under 2nd paragraph 
> of S
> 3.5 but a more explicit mention might be worthwhile.
>
> In S 3.5.1:
>
>       *  The STE destination IPv4 transport is set to (Z(Y'),y), y being
>          the same port as the STE destination IPv6 transport address and
>          Z(Y') being algorithmically generated from the IPv6 destination
>          address (i.e.  Y') using the reverse algorithm as specified in
>          Section 3.5.4.
>
> .. S 3.5.2 can hardly be said to specify any algorithm, but it certainly
> doesn't even mention the reverse algorithm (however trivial it might be).
>
> In S 3.5.2:
>
>       V4 SYN RCV: An IPv4 packet containing a TCP SYN was received by
>       the NAT64, implying that a TCP connection is being initiated from
>       the IPv4 side.  The NAT64 is now waiting for a matching IPv6
>       packet containing the TCP SYN in the opposite direction.
> ...
>    A TCP segment with the SYN flag set that is received through the IPv6
>    interface is called a V6 SYN, similarly, V4 SYN, V4 FIN, V6 FIN, V6
>    FIN + V4 FIN, V6 RST and V4 RST.
>
> .. this is somewhat confusing because you appear to be using "V4 SYN 
> RCV" to
> mean "only SYN flag set" (due to "being initiated from ...") while "V4 
> SYN"
> later means "SYN [and possibly ACK] flag set". The same applies to V6 
> of course.
> Maybe reword?  Maybe "being initiated from.." and this distinction is not
> even necessary, because you don't have it on V4 FIN RCV side either? 
> (Though
> when creating sessions, the semantics differ slightly depending on the
> initiator.)
>
> V4 FIN RCV, V6 FIN RCV and V4 FIN + V6 FIN are listed in the state 
> diagram
> without "RCV" keyword, and this should be corrected.
>
> I'm also a bit hesitant to include 4 min T.O., 2hrs etc. in the 
> diagram as
> these seem to be certain _minimum_ values and the implementation would be
> free to use some other values as well.  More general description would be
> slightly better.
>
> A cornercase from specification language point of view are those TCP 
> flags
> that could at least in theory be applicable alongside "state flags": 
> URG and
> PSH.
>
> In S 3.5.2.2:
>
>          +  The STE transport IPv6 source address is left unspecified
>             and may be populated by other protocols out of the scope of
>             this specification.
>
>
> ... what does leaving source address unspecified mean in the context 
> of TCP
> session table searches, packets on the wire etc.?
>
>          The lifetime of the STE entry is set to TCP_INCOMING_SYN as per
>          [RFC5382] and the packet is stored.  The result is that the
>          NAT64 will not drop the packet based on the filtering, nor
>          create a BIB entry.  Instead, the NAT64 will only create the
>          session table entry and store the packet.  The motivation for
>          this is to support simultaneous open of TCP connections.
>
> ... for how long is the packet supposed to be stored?  Will it ever be 
> sent
> out on the wire? If yes, what will replace the "unspecified" IPv6 source
> address then?  If not, what's the point of storing a packet in the first
> place (instead of just creating a state entry and dropping it)?  An 
> explicit
> reference how the packet processing continues could be useful here (it 
> seems
> it does not continue).  The same also applies in the case a TCP BIB entry
> exist (similar description).
>
>    *** ESTABLISHED ***
>
>    If a V4 FIN packet is received, the packet is translated and
>    forwarded.  The state is moved to V4 FIN RCV.
>
>    If a V6 FIN packet is received, the packet is translated and
>    forwarded.  The state is moved to V6 FIN RCV.
>
> .. I suppose you're referring here to _only_ FIN flag set. Does a V4 FIN
> packet with FIN+ACK flag set more the state to V4 FIN RCV?
>
> In S 3.5.3,
>
>           If the packet is discarded, then an ICMP error message
>       MAY be sent to the original sender of the packet, unless the
>       discarded packet is itself an ICMP message.
>
> .. there are copy/paste/logical errors here, and this also seems to 
> apply to
> similar sections on UDP (at least).  First of all, under UDP section, 
> isn't
> it already known which kind of packet is in question?  Isn't the 
> "itself an ICMP message" condition wrong and should be "itself an ICMP 
> error
> message"?  Is it intentional that the "ICMP packet" condition is 
> different
> for BIB entry search and address-dependent filtering search?
>
> S 3.5.3 deals with ICMP Query sessions, so from that perspective, this
> should always result in an ICMP error message generation?
>
> In S 3.6.1:
>
>    When translating in the IPv4 --> IPv6 direction, let the incoming
>    source and destination transport addresses in the 5-tuple be (S,s)
>    and (D,d) respectively.  The outgoing source transport address is
>    computed as follows:
>
>       The outgoing source transport address is generated from S using
>       the address transformation algorithm described in Section 3.5.4.
>
>       The BIB table is searched for an entry (X',x) <--> (D,d), and if
>       one is found, the outgoing destination transport address is set to
>       (X',x).
>
> .. you don't mention what happens if an entry is not found in the BIB 
> table.
> (maybe the assumption is that you should never arrive at this step if 
> the BIB
> entry does not exist..) -- the same also applies in 3.6.2.
>
> 5.3.  Attacks on NAT64
>
> .. it might be worth also mentioning the "packet is stored" case already
> mentioned above in the context of simultaneous opens.
>
> editorial:
> ----------
>
> In S 3.2 also later:
>
> (X',Y',I1) <--> (T,Z,I2)
>
> .. because ICMP identifier corresponds to a port number in some sense, 
> and
> port numbers are designated with lower-case letters, I wonder if in this
> case as well it would be better to use 'i1' and 'i2'.
>
> *  The NAT64 MAY require that the UDP, TCP, or ICMP header be
>          completely contained within the fragment that contains OFFSET
>          equal to zero.
>
> s/OFFSET/fragment offset/
>
>    o  When the protocol following the IP header is ICMP (Sections 3.4
>       and 4.4) and it is an ICMP error message, the source and
>       destination transport addresses in the embedded packet are set to
>       the destination and source transport addresses from the outgoing
>       5-tuple (note the swap of source and destination).
>
> .. you're referring to S 3.4 & S 4.4 of [I-D.ietf-behave-v6v4-xlate], not
> this document, and this may be confusing.  But reference to S 3.4 and 4.4
> appears to be redundant and could maybe be removed here altogether.
>
>    [I-D.ietf-mmusic-ice]
>               Rosenberg, J., "Interactive Connectivity Establishment
>               (ICE): A Protocol for Network Address Translator (NAT)
>               Traversal for Offer/Answer Protocols",
>               draft-ietf-mmusic-ice-19 (work in progress), October 2007.
>
> .. now published as an RFC.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>


From dthaler@microsoft.com  Thu Jun  3 19:02:44 2010
Return-Path: <dthaler@microsoft.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED6173A6870 for <behave@core3.amsl.com>; Thu,  3 Jun 2010 19:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.198
X-Spam-Level: 
X-Spam-Status: No, score=-108.198 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fEZt9IOnnDPe for <behave@core3.amsl.com>; Thu,  3 Jun 2010 19:02:37 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 56A5C3A6782 for <behave@ietf.org>; Thu,  3 Jun 2010 19:02:37 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 3 Jun 2010 19:02:24 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft SMTP Server (TLS) id 14.1.160.4; Thu, 3 Jun 2010 19:02:23 -0700
Received: from TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.203]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Thu, 3 Jun 2010 19:02:23 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "draft-ietf-behave-dns64@tools.ietf.org" <draft-ietf-behave-dns64@tools.ietf.org>
Thread-Topic: DNS64 draft feedback
Thread-Index: AcsDglGoCHRMw8TBTZ2Rs5w8z/bd+gABxpfA
Date: Fri, 4 Jun 2010 02:02:22 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF652C011F18@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
References: <849F300114E0BB499C0CDDB5A9922FF148585803@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <849F300114E0BB499C0CDDB5A9922FF148585803@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_9B57C850BB53634CACEC56EF4853FF652C011F18TK5EX14MBXW603w_"
MIME-Version: 1.0
Cc: "'behave' \(behave@ietf.org\)" <behave@ietf.org>
Subject: [BEHAVE] FW: DNS64 draft feedback
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Jun 2010 02:02:45 -0000

--_000_9B57C850BB53634CACEC56EF4853FF652C011F18TK5EX14MBXW603w_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Below are some IETF last call comments on this draft, which were sent to me=
 from Jeff Westhead (jwesth@microsoft.com<mailto:jwesth@microsoft.com>)

-Dave

From: Jeff Westhead
Sent: Thursday, June 03, 2010 6:16 PM
To: Dave Thaler
Subject: DNS64 draft feedback

Here is my feedback. A lot of my issues I think stem from the fact that the=
 draft authors envision DNS64 as a component grafted into existing DNS impl=
ementations, which would give them all kinds of DNS protocol handling for f=
ree. I'm not sure this is a suitable approach to take in this context. I th=
ink some acknowledgement should be made of various DNS protocol issues that=
 will have to be taken into account during DNS64 processing. Some implement=
ors may choose to build a DNS64 server from scratch.

I also have some reservations about the piecemeal approach to working confi=
gurations. When DNSSEC is used, the DNS64 server is fairly broken. Instead =
DNS64 must be implemented on clients. This is ok, except that a) it is up t=
o administrators and/or implementors to ensure that only working DNS64 depl=
oyment models are used, and b) if DNS64 is implemented on clients then DNS6=
4 configuration becomes more difficult to distribute.

Specific feedback on draft-ietf-behave-dns64-09:
*        There is no mention if the following aspects of the DNS protocol S=
HOULD or MUST be implemented or otherwise handled by DNS64:
o   Listen on UDP, TCP, or both
o   EDNS support, although this is implied by the use of the DO bit
o   If EDNS is supported, is support for UDP packets of a specific size man=
dated?
o   Caching of remote query results
o   When synthesizing AAAA records, what if the response becomes too large
o   TC bit handling, either in responses received to remote servers or in r=
esponses sent to clients
o   Packet assembly may be complicated if the DNS64 server uses a larger ED=
NS packet size than some of its clients; or if truncation applies to some c=
lients but not others because of client EDNS packet size variations
o   Note that all of these items above may be handled already if one treats=
 DNS64 as a "logical function" as noted in the first paragraph of Section 5=
; however there are many elements of the draft, such as anything discussing=
 the DO and CD bits, and requiring the algorithm to generate remote queries=
, where this definition is violated and the DNS protocol is brought into th=
e realm of DNS64
*        There are a number of DNSSEC scenarios that are broken for certain=
 types of DNS64. The draft does not contain much precise guidance for this.=
 Specifically:
o   Section 3, case 4: the draft only says this will be "problematic" which=
 is at best an understatement.
o   Section 3, case 5: this case is fine but does not allow for any deviati=
on in application or OS behavior; this artificial restriction will be "prob=
lematic" for some vendors as not all applications and OSes are guaranteed t=
o conform.
o   Section 3, case 7: the downstream validator will ignore the synthesized=
 data; the draft should in my opinion more clearly state that DNS64 is fund=
amentally broken for this case .
*        The phrase "ought to work" seems a bit imprecise (section 3, case =
6).
*        Section 5.1 does not mention if cached results from previous queri=
es should be consulted. The DNS64 should probably cache results as per stan=
dard DNS practice.
*        Section 5.1.1 states "as per normal DNS semantics". This is not qu=
ite as trivial as the draft makes it sound. The DNS64 will have to deal wit=
h truncation caused by mismatched EDNS packet sizes.
*        Section 5.1.2 oversimplifies error handling. I understand the moti=
vation but were a server to return SERVFAIL for some unknown reason, a norm=
al DNS server would attempt resolution against another server. DNS64 will c=
hange that behavior and may impact general DNS robustness. I'm not sure it'=
s a good idea to treat all error codes as an empty response. Also, if DNS64=
 is being purposefully designed in violation of the spirit of the DNS proto=
col to work around deployed name server behavior, I think a reference justi=
fying this would be appropriate.
*        In 5.1.3, if a timeout occurs shouldn't the query be sent to anoth=
er server if one is available?
*        Section 5.1.6, caching is not mentioned here, as above.
*        Section 5.1.6 mentions "transient errors" and seems to contradict =
the error handling algorithm presented in Section 5.1.2.
*        Section 5.1.7: When synthesizing a AAAA record, why is the TTL "mi=
n (TTL of A record, SOA MinimumTTL)" and not just the TTL of the A record? =
If there is a good reason for this, perhaps the draft should state the rati=
onale.
*        Section 5.3.2: The additional section will contain records, but th=
e client will be unable to use them. I believe that some clients will not r=
e-query for additional section data in this case. Some test/prototyping mig=
ht be advisable.
*        Section 5.4: This section should discuss truncation and the EDNS O=
PT record.
*        Section 7.1: Step #3 contains two plural/singular typos.






--_000_9B57C850BB53634CACEC56EF4853FF652C011F18TK5EX14MBXW603w_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m=3D"http://sc=
hemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-=
html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; chars=
et=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:45033173;
	mso-list-template-ids:-386776382;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:412552357;
	mso-list-template-ids:-1800904640;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2
	{mso-list-id:939485943;
	mso-list-template-ids:-1856710198;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3
	{mso-list-id:1522159827;
	mso-list-template-ids:263735486;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4
	{mso-list-id:1825395620;
	mso-list-template-ids:482358182;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5
	{mso-list-id:1967855531;
	mso-list-template-ids:1664222312;}
@list l5:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6
	{mso-list-id:1989554032;
	mso-list-template-ids:859632404;}
@list l6:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l6:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Below are some IETF last call comments on this draft, which w=
ere sent to me from Jeff Westhead (<a href=3D"mailto:jwesth@microsoft.com">=
jwesth@microsoft.com</a>)<o:p></o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'color:#1F497D'>-Dave<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=
=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><=
p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma"=
,"sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:=
"Tahoma","sans-serif"'> Jeff Westhead <br><b>Sent:</b> Thursday, June 03, 2=
010 6:16 PM<br><b>To:</b> Dave Thaler<br><b>Subject:</b> DNS64 draft feedba=
ck<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p><p class=3DMsoNormal>Here is my feedback. A lot of my issues I think ste=
m from the fact that the draft authors envision DNS64 as a component grafte=
d into existing DNS implementations, which would give them all kinds of DNS=
 protocol handling for free. I&#8217;m not sure this is a suitable approach=
 to take in this context. I think some acknowledgement should be made of va=
rious DNS protocol issues that will have to be taken into account during DN=
S64 processing. Some implementors may choose to build a DNS64 server from s=
cratch.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>I also have some reservations about the piecemeal approach to wor=
king configurations. When DNSSEC is used, the DNS64 server is fairly broken=
. Instead DNS64 must be implemented on clients. This is ok, except that a) =
it is up to administrators and/or implementors to ensure that only working =
DNS64 deployment models are used, and b) if DNS64 is implemented on clients=
 then DNS64 configuration becomes more difficult to distribute. <o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Specific=
 feedback on draft-ietf-behave-dns64-09:<o:p></o:p></p><p class=3DMsoNormal=
 style=3D'margin-left:27.0pt;text-indent:-.25in;mso-list:l1 level1 lfo2;ver=
tical-align:middle'><![if !supportLists]><span style=3D'font-size:10.0pt;fo=
nt-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<span style=3D'fo=
nt:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </sp=
an></span></span><![endif]>There is no mention if the following aspects of =
the DNS protocol SHOULD or MUST be implemented or otherwise handled by DNS6=
4:<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o=
:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-in=
dent:-.25in;mso-list:l1 level2 lfo2;vertical-align:middle'><![if !supportLi=
sts]><span style=3D'font-size:10.0pt;font-family:"Courier New"'><span style=
=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&n=
bsp; </span></span></span><![endif]>Listen on UDP, TCP, or both<span style=
=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></sp=
an></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;m=
so-list:l1 level2 lfo2;vertical-align:middle'><![if !supportLists]><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:=
Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span><=
/span></span><![endif]>EDNS support, although this is implied by the use of=
 the DO bit<span style=3D'font-size:12.0pt;font-family:"Times New Roman","s=
erif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.75i=
n;text-indent:-.25in;mso-list:l1 level2 lfo2;vertical-align:middle'><![if !=
supportLists]><span style=3D'font-size:10.0pt;font-family:"Courier New"'><s=
pan style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'=
>&nbsp;&nbsp; </span></span></span><![endif]>If EDNS is supported, is suppo=
rt for UDP packets of a specific size mandated?<span style=3D'font-size:12.=
0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l1 leve=
l2 lfo2;vertical-align:middle'><![if !supportLists]><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><!=
[endif]>Caching of remote query results<span style=3D'font-size:12.0pt;font=
-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNorm=
al style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l1 level2 lfo2;ve=
rtical-align:middle'><![if !supportLists]><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span style=3D'f=
ont:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![endif]>Wh=
en synthesizing AAAA records, what if the response becomes too large<span s=
tyle=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p>=
</span></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25=
in;mso-list:l1 level2 lfo2;vertical-align:middle'><![if !supportLists]><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'mso-l=
ist:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </sp=
an></span></span><![endif]>TC bit handling, either in responses received to=
 remote servers or in responses sent to clients<span style=3D'font-size:12.=
0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l1 leve=
l2 lfo2;vertical-align:middle'><![if !supportLists]><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><!=
[endif]>Packet assembly may be complicated if the DNS64 server uses a large=
r EDNS packet size than some of its clients; or if truncation applies to so=
me clients but not others because of client EDNS packet size variations<spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o=
:p></span></p><p class=3DMsoNormal style=3D'margin-left:.75in;text-indent:-=
.25in;mso-list:l1 level2 lfo2;vertical-align:middle'><![if !supportLists]><=
span style=3D'font-size:10.0pt;font-family:"Courier New"'><span style=3D'ms=
o-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; <=
/span></span></span><![endif]>Note that all of these items above may be han=
dled already if one treats DNS64 as a &quot;logical function&quot; as noted=
 in the first paragraph of Section 5; however there are many elements of th=
e draft, such as anything discussing the DO and CD bits, and requiring the =
algorithm to generate remote queries, where this definition is violated and=
 the DNS protocol is brought into the realm of DNS64<span style=3D'font-siz=
e:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p cl=
ass=3DMsoNormal style=3D'margin-left:27.0pt;text-indent:-.25in;mso-list:l0 =
level1 lfo4;vertical-align:middle'><![if !supportLists]><span style=3D'font=
-size:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<s=
pan style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </span></span></span><![endif]>There are a number of DNSSEC scen=
arios that are broken for certain types of DNS64. The draft does not contai=
n much precise guidance for this. Specifically:<span style=3D'font-size:12.=
0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 leve=
l2 lfo4;vertical-align:middle'><![if !supportLists]><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><!=
[endif]>Section 3, case 4: the draft only says this will be &quot;problemat=
ic&quot; which is at best an understatement.<span style=3D'font-size:12.0pt=
;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=3DMs=
oNormal style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 level2 lf=
o4;vertical-align:middle'><![if !supportLists]><span style=3D'font-size:10.=
0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span></span><![endi=
f]>Section 3, case 5: this case is fine but does not allow for any deviatio=
n in application or OS behavior; this artificial restriction will be &quot;=
problematic&quot; for some vendors as not all applications and OSes are gua=
ranteed to conform.<span style=3D'font-size:12.0pt;font-family:"Times New R=
oman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-l=
eft:.75in;text-indent:-.25in;mso-list:l0 level2 lfo4;vertical-align:middle'=
><![if !supportLists]><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New=
 Roman"'>&nbsp;&nbsp; </span></span></span><![endif]>Section 3, case 7: the=
 downstream validator will ignore the synthesized data; the draft should in=
 my opinion more clearly state that DNS64 is fundamentally broken for this =
case .<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"=
'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;te=
xt-indent:-.25in;mso-list:l2 level1 lfo6;vertical-align:middle'><![if !supp=
ortLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span style=
=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Th=
e phrase &quot;ought to work&quot; seems a bit imprecise (section 3, case 6=
).<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o=
:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;text-i=
ndent:-.25in;mso-list:l4 level1 lfo8;vertical-align:middle'><![if !supportL=
ists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'ms=
o-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Section =
5.1 does not mention if cached results from previous queries should be cons=
ulted. The DNS64 should probably cache results as per standard DNS practice=
.<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:=
p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;text-in=
dent:-.25in;mso-list:l4 level1 lfo8;vertical-align:middle'><![if !supportLi=
sts]><span style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'mso=
-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Section 5=
.1.1 states &quot;as per normal DNS semantics&quot;. This is not quite as t=
rivial as the draft makes it sound. The DNS64 will have to deal with trunca=
tion caused by mismatched EDNS packet sizes.<span style=3D'font-size:12.0pt=
;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=3DMs=
oNormal style=3D'margin-left:27.0pt;text-indent:-.25in;mso-list:l3 level1 l=
fo10;vertical-align:middle'><![if !supportLists]><span style=3D'font-size:1=
0.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<span sty=
le=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span></span></span><![endif]>Section 5.1.2 oversimplifies error handl=
ing. I understand the motivation but were a server to return SERVFAIL for s=
ome unknown reason, a normal DNS server would attempt resolution against an=
other server. DNS64 will change that behavior and may impact general DNS ro=
bustness. I'm not sure it's a good idea to treat all error codes as an empt=
y response. Also, if DNS64 is being purposefully designed in violation of t=
he spirit of the DNS protocol to work around deployed name server behavior,=
 I think a reference justifying this would be appropriate.<span style=3D'fo=
nt-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p=
><p class=3DMsoNormal style=3D'margin-left:27.0pt;text-indent:-.25in;mso-li=
st:l6 level1 lfo12;vertical-align:middle'><![if !supportLists]><span style=
=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&m=
iddot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>In 5.1.3, if a timeout oc=
curs shouldn't the query be sent to another server if one is available? <sp=
an style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></=
o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;text-indent=
:-.25in;mso-list:l6 level1 lfo12;vertical-align:middle'><![if !supportLists=
]><span style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D'mso-li=
st:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Section 5.1.=
6, caching is not mentioned here, as above.<span style=3D'font-size:12.0pt;=
font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=3DMso=
Normal style=3D'margin-left:27.0pt;text-indent:-.25in;mso-list:l6 level1 lf=
o12;vertical-align:middle'><![if !supportLists]><span style=3D'font-size:10=
.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<span styl=
e=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span></span></span><![endif]>Section 5.1.6 mentions &quot;transient er=
rors&quot; and seems to contradict the error handling algorithm presented i=
n Section 5.1.2.<span style=3D'font-size:12.0pt;font-family:"Times New Roma=
n","serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left=
:27.0pt;text-indent:-.25in;mso-list:l6 level1 lfo12;vertical-align:middle'>=
<![if !supportLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><s=
pan style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![=
endif]>Section 5.1.7: When synthesizing a AAAA record, why is the TTL &quot=
;min (TTL of A record, SOA MinimumTTL)&quot; and not just the TTL of the A =
record? If there is a good reason for this, perhaps the draft should state =
the rationale.<span style=3D'font-size:12.0pt;font-family:"Times New Roman"=
,"serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:2=
7.0pt;text-indent:-.25in;mso-list:l6 level1 lfo12;vertical-align:middle'><!=
[if !supportLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><spa=
n style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Ro=
man"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![en=
dif]>Section 5.3.2: The additional section will contain records, but the cl=
ient will be unable to use them. I believe that some clients will not re-qu=
ery for additional section data in this case. Some test/prototyping might b=
e advisable.<span style=3D'font-size:12.0pt;font-family:"Times New Roman","=
serif"'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.=
0pt;text-indent:-.25in;mso-list:l6 level1 lfo12;vertical-align:middle'><![i=
f !supportLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endi=
f]>Section 5.4: This section should discuss truncation and the EDNS OPT rec=
ord.<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>=
<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-left:27.0pt;text=
-indent:-.25in;mso-list:l5 level1 lfo14;vertical-align:middle'><![if !suppo=
rtLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span style=3D=
'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New Roman"'>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Secti=
on 7.1: Step #3 contains two plural/singular typos.<span style=3D'font-size=
:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p cla=
ss=3DMsoNormal style=3D'margin-left:27.0pt'>&nbsp;<o:p></o:p></p><p class=
=3DMsoNormal style=3D'margin-left:27.0pt'>&nbsp;<o:p></o:p></p><p class=3DM=
soNormal style=3D'margin-left:27.0pt'>&nbsp;<o:p></o:p></p><p class=3DMsoNo=
rmal style=3D'margin-left:27.0pt'>&nbsp;<o:p></o:p></p><p class=3DMsoNormal=
><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_9B57C850BB53634CACEC56EF4853FF652C011F18TK5EX14MBXW603w_--

From ajs@shinkuro.com  Wed Jun  9 12:33:16 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2EA83A6783 for <behave@core3.amsl.com>; Wed,  9 Jun 2010 12:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.198
X-Spam-Level: *
X-Spam-Status: No, score=1.198 tagged_above=-999 required=5 tests=[AWL=1.197,  BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPHX-wX+yB9l for <behave@core3.amsl.com>; Wed,  9 Jun 2010 12:33:15 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id D7E913A67D1 for <behave@ietf.org>; Wed,  9 Jun 2010 12:33:14 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id A0EA81ECB408; Wed,  9 Jun 2010 19:33:14 +0000 (UTC)
Date: Wed, 9 Jun 2010 15:33:10 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: Dave Thaler <dthaler@microsoft.com>
Message-ID: <20100609193304.GG62459@shinkuro.com>
References: <849F300114E0BB499C0CDDB5A9922FF148585803@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF652C011F18@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF652C011F18@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "'behave' \(behave@ietf.org\)" <behave@ietf.org>, "draft-ietf-behave-dns64@tools.ietf.org" <draft-ietf-behave-dns64@tools.ietf.org>
Subject: Re: [BEHAVE] FW: DNS64 draft feedback
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 09 Jun 2010 19:33:16 -0000

These are some fantastic comments.  Thanks.  Some elaboration inline.
Should I contact Jeff Westhead directly, or do you want to play
intermediary?

On Fri, Jun 04, 2010 at 02:02:22AM +0000, Dave Thaler wrote:
> 
> Here is my feedback. A lot of my issues I think stem from the fact
> that the draft authors envision DNS64 as a component grafted into
> existing DNS implementations, which would give them all kinds of DNS
> protocol handling for free. I'm not sure this is a suitable approach
> to take in this context. 

Something came up during some testing that caused me to have a similar
reaction.  The -10 draft (which is not out yet because the final
touches went on about three seconds before I saw the IETF LC
announcement) includes the following text:

   The final response from the DNS64 is subject to all the standard DNS
   rules, including truncation [RFC1035] and EDNS0 handling [RFC2671].

It goes at the end of section 5.4.  The -09 text also says (and the
-10 text retains) at the top of section 5:

   DNS64 is a logical function that synthesizes AAAA records from A
   records.  The DNS64 function may be implemented in a stub resolver,
   in a recursive resolver, or in an authoritative name server.

Does the combination of those now make it clear that everything you
need to know when implementing "plain" DNS you also need to know for
DNS64?  I am really not keen to try to respecify general DNS handling
in this document.

> I also have some reservations about the piecemeal approach to
> working configurations. When DNSSEC is used, the DNS64 server is
> fairly broken. Instead DNS64 must be implemented on clients. This is
> ok, except that a) it is up to administrators and/or implementors to
> ensure that only working DNS64 deployment models are used, and b) if
> DNS64 is implemented on clients then DNS64 configuration becomes
> more difficult to distribute.

This is true, but it's completely insurmountable.  The answer to "gee,
DNS64 doesn't get along well with DNS64-oblivious DNS clients" is
"don't use DNS64, then."  By design, DNSSEC detects intermediate
mucking with DNS answers.  By design, DNS64 mucks with answers.  These
are never going to play nice. 

> Specific feedback on draft-ietf-behave-dns64-09:
> *        There is no mention if the following aspects of the DNS protocol SHOULD or MUST be implemented or otherwise handled by DNS64:
> o   Listen on UDP, TCP, or both
> o   EDNS support, although this is implied by the use of the DO bit
> o   If EDNS is supported, is support for UDP packets of a specific size mandated?
> o   Caching of remote query results

I don't really understand why the document ought to specify these:
those are questions for what you are doing when implementing a stub or
recursive resolver, or an authoritative server, I think.

> o   When synthesizing AAAA records, what if the response becomes too large
> o   TC bit handling, either in responses received to remote servers or in responses sent to clients
> o   Packet assembly may be complicated if the DNS64 server uses a larger EDNS packet size than some of its clients; or if truncation applies to some clients but not others because of client EDNS packet size variations

Does the additional sentence to be in -10 help?

> o   Note that all of these items above may be handled already if one treats DNS64 as a "logical function" as noted in the first paragraph of Section 5; however there are many elements of the draft, such as anything discussing the DO and CD bits, and requiring the algorithm to generate remote queries, where this definition is violated and the DNS protocol is brought into the realm of DNS64

That isn't the intention.  The intention instead is to make the
logical function fit within the bounds of what a regular DNS server or
client is going to expect.  But if there's a way to make this clearer,
text would be appreciated.

> *        There are a number of DNSSEC scenarios that are broken for certain types of DNS64. The draft does not contain much precise guidance for this. Specifically:
> o   Section 3, case 4: the draft only says this will be "problematic" which is at best an understatement.

Would "broken" instead be better?  It is in fact not going to work, period.

> o   Section 3, case 5: this case is fine but does not allow for any deviation in application or OS behavior; this artificial restriction will be "problematic" for some vendors as not all applications and OSes are guaranteed to conform.

I don't understand the objection here.  What's the artificial
restriction?  There is no guarantee to a client of what they get
(DNSSEC-wise) from an intermediate resolver if CD=0 or DO=0.  If you
don't set those both, you cannot rely on your validation to be complete.

> o   Section 3, case 7: the downstream validator will ignore the synthesized data; the draft should in my opinion more clearly state that DNS64 is fundamentally broken for this case .

So if we added, "So DNS64 will not work with an unmodified validating
node of this sort," would that address the objection?

> *        The phrase "ought to work" seems a bit imprecise (section 3, case 6).

s/ought to/will/?

> *        Section 5.1 does not mention if cached results from previous queries should be consulted. The DNS64 should probably cache results as per standard DNS practice.

It does not say that because some kinds of implementations just don't
cache.  So this would depend entirely on whether you're building a cache.

> *        Section 5.1.1 states "as per normal DNS semantics". This is not quite as trivial as the draft makes it sound. The DNS64 will have to deal with truncation caused by mismatched EDNS packet sizes.

It's not trivial, of course, but it is as per normal DNS semantics.
Is there something more that should be said here?

> *        Section 5.1.2 oversimplifies error handling. I understand the motivation but were a server to return SERVFAIL for some unknown reason, a normal DNS server would attempt resolution against another server. DNS64 will change that behavior and may impact general DNS robustness. I'm not sure it's a good idea to treat all error codes as an empty response. Also, if DNS64 is being purposefully designed in violation of the spirit of the DNS protocol to work around deployed name server behavior, I think a reference justifying this would be appropriate.

I was nor real happy with this change in the first place, as some
participants may recall, but there seemed to be a lot of voices in
favour of this approach.  SERVFAIL in particular was a target, because
that seems to be a common (bogus, IMO) cases where one gets SERVFAIL
for v6 records instead of something reasonable.  I'm not sure how to
put references in for unpublished test results.  Chairs?

> *        In 5.1.3, if a timeout occurs shouldn't the query be sent to another server if one is available?

This was again an attempt to cope with deployed systems that just
don't respond to AAAA queries.  ISTR that one of the large content
network systems does this, but I don't have my finger on it at the
moment.  So yes, this makes the system more subject to failure.

I'd be interested to hear whether those who argued strongly for this
error handling in the past are influenced by these objections.

> *        Section 5.1.6, caching is not mentioned here, as above.

Again, I am not sure we ought to be opening that topic in this draft.

> *        Section 5.1.6 mentions "transient errors" and seems to contradict the error handling algorithm presented in Section 5.1.2.

Good catch.  This will have to be resolved along with the discussion
of errors above.

> *        Section 5.1.7: When synthesizing a AAAA record, why is the TTL "min (TTL of A record, SOA MinimumTTL)" and not just the TTL of the A record? If there is a good reason for this, perhaps the draft should state the rationale.

This is for the same reason one uses this approach in negative
caching.  We want the shortest TTL possible, so that a cache that gets
the synthetic AAAA does not keep it longer than the zone operator
expects (so that if the zone operator adds a real AAAA record, it
starts to get used as soon as possible).  I can add some rationale for it.

> *        Section 5.3.2: The additional section will contain records, but the client will be unable to use them. I believe that some clients will not re-query for additional section data in this case. Some test/prototyping might be advisable.

If they don't, they're completely broken already today.  We had this
argument when this section was changed, and Mark Andrews pointed out
that a client that didn't re-query because of existing additional data
is already broken, because there's no promise the additional section
is ever complete.

> *        Section 5.4: This section should discuss truncation and the EDNS OPT record.

This is where we added the sentence mentioned near the beginning of
this message.  Thanks.

> *        Section 7.1: Step #3 contains two plural/singular typos.

Hrm. I guess the problem is that it talks about "single records" as
opposed to RRSets.  Thanks.

A
-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From simon.perreault@viagenie.ca  Wed Jun  9 14:41:19 2010
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A540B3A6827 for <behave@core3.amsl.com>; Wed,  9 Jun 2010 14:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eY0hxSLExeal for <behave@core3.amsl.com>; Wed,  9 Jun 2010 14:41:18 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by core3.amsl.com (Postfix) with ESMTP id 177FE3A681E for <behave@ietf.org>; Wed,  9 Jun 2010 14:41:18 -0700 (PDT)
Received: from balaise.nomis80.org (modemcable245.152-21-96.mc.videotron.ca [96.21.152.245]) by jazz.viagenie.ca (Postfix) with ESMTPSA id BDB9F20D0A for <behave@ietf.org>; Wed,  9 Jun 2010 17:41:17 -0400 (EDT)
Message-ID: <4C100A7D.4080805@viagenie.ca>
Date: Wed, 09 Jun 2010 17:41:17 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4
MIME-Version: 1.0
To: behave@ietf.org
References: <849F300114E0BB499C0CDDB5A9922FF148585803@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<9B57C850BB53634CACEC56EF4853FF652C011F18@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <20100609193304.GG62459@shinkuro.com>
In-Reply-To: <20100609193304.GG62459@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] FW: DNS64 draft feedback
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 09 Jun 2010 21:41:19 -0000

On 06/09/2010 03:33 PM, Andrew Sullivan wrote:
> Something came up during some testing that caused me to have a similar
> reaction.  The -10 draft (which is not out yet because the final
> touches went on about three seconds before I saw the IETF LC
> announcement) includes the following text:
> 
>    The final response from the DNS64 is subject to all the standard DNS
>    rules, including truncation [RFC1035] and EDNS0 handling [RFC2671].
> 
> It goes at the end of section 5.4.  The -09 text also says (and the
> -10 text retains) at the top of section 5:
> 
>    DNS64 is a logical function that synthesizes AAAA records from A
>    records.  The DNS64 function may be implemented in a stub resolver,
>    in a recursive resolver, or in an authoritative name server.
> 
> Does the combination of those now make it clear that everything you
> need to know when implementing "plain" DNS you also need to know for
> DNS64?  I am really not keen to try to respecify general DNS handling
> in this document.

As an implementor, I found it to be more than enough already. It is very
important that DNS64 be considered a separate and optional logical
function, not a rigidly-defined pyramid of protocols. DNS64 could
conceivably be implemented on top of, underneath, or alongside other
RFCs that we didn't think of or that are yet to be written. So please
leave the text as it is.

>> *        Section 5.1.2 oversimplifies error handling. I understand the motivation but were a server to return SERVFAIL for some unknown reason, a normal DNS server would attempt resolution against another server. DNS64 will change that behavior and may impact general DNS robustness. I'm not sure it's a good idea to treat all error codes as an empty response. Also, if DNS64 is being purposefully designed in violation of the spirit of the DNS protocol to work around deployed name server behavior, I think a reference justifying this would be appropriate.
> 
> I was nor real happy with this change in the first place, as some
> participants may recall, but there seemed to be a lot of voices in
> favour of this approach.  SERVFAIL in particular was a target, because
> that seems to be a common (bogus, IMO) cases where one gets SERVFAIL
> for v6 records instead of something reasonable.  I'm not sure how to
> put references in for unpublished test results.  Chairs?

It's common in these cases to put references to WG mailing list
archives. Why not reference this?

http://www.ietf.org/mail-archive/web/behave/current/msg07686.html

>> *        In 5.1.3, if a timeout occurs shouldn't the query be sent to another server if one is available?
> 
> This was again an attempt to cope with deployed systems that just
> don't respond to AAAA queries.  ISTR that one of the large content
> network systems does this, but I don't have my finger on it at the
> moment.  So yes, this makes the system more subject to failure.
> 
> I'd be interested to hear whether those who argued strongly for this
> error handling in the past are influenced by these objections.

I think that the OP is misinterpreting the text. Here it is:

5.1.3. Dealing with timeouts

   If the query receives no answer before the timeout, it is treated as
   RCODE=2 (Server failure).

It doesn't say "no answer *from a single server*". Of course you're
supposed to do what a recursive DNS implementation usually does! ;)

>> *        Section 5.1.6, caching is not mentioned here, as above.
> 
> Again, I am not sure we ought to be opening that topic in this draft.

+1

>> *        Section 5.1.6 mentions "transient errors" and seems to contradict the error handling algorithm presented in Section 5.1.2.
> 
> Good catch.  This will have to be resolved along with the discussion
> of errors above.

Just scrap the sentence. It's functionality that should be part of the
normal DNS stuff, not DNS64.

>> *        Section 5.1.7: When synthesizing a AAAA record, why is the TTL "min (TTL of A record, SOA MinimumTTL)" and not just the TTL of the A record? If there is a good reason for this, perhaps the draft should state the rationale.
> 
> This is for the same reason one uses this approach in negative
> caching.  We want the shortest TTL possible, so that a cache that gets
> the synthetic AAAA does not keep it longer than the zone operator
> expects (so that if the zone operator adds a real AAAA record, it
> starts to get used as soon as possible).  I can add some rationale for it.

Just for the OP's information, here's where this was discussed:

http://www.ietf.org/mail-archive/web/behave/current/msg05948.html

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org

From ajs@shinkuro.com  Wed Jun  9 14:50:43 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA0003A6857 for <behave@core3.amsl.com>; Wed,  9 Jun 2010 14:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.177
X-Spam-Level: 
X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5 tests=[AWL=2.422,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hu4f+btToEMc for <behave@core3.amsl.com>; Wed,  9 Jun 2010 14:50:43 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 2DF103A683A for <behave@ietf.org>; Wed,  9 Jun 2010 14:50:43 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id F38E91ECB408 for <behave@ietf.org>; Wed,  9 Jun 2010 21:50:43 +0000 (UTC)
Date: Wed, 9 Jun 2010 17:50:42 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100609215041.GC310@shinkuro.com>
References: <849F300114E0BB499C0CDDB5A9922FF148585803@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF652C011F18@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <20100609193304.GG62459@shinkuro.com> <4C100A7D.4080805@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C100A7D.4080805@viagenie.ca>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] FW: DNS64 draft feedback
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 09 Jun 2010 21:50:44 -0000

On Wed, Jun 09, 2010 at 05:41:17PM -0400, Simon Perreault wrote:
> 5.1.3. Dealing with timeouts
> 
>    If the query receives no answer before the timeout, it is treated as
>    RCODE=2 (Server failure).
> 
> It doesn't say "no answer *from a single server*". Of course you're
> supposed to do what a recursive DNS implementation usually does! ;)

That's reasonable.  It does seem to me that we could clean this up
slightly, though, because even though I wrote the sentence, I still
interpreted it as "the timeout for the server".  What about this:

    If the query receives no answer before the timeout (which might be
    the timeout from every authoritative server, depending on whether
    DNS64 is implemented as part of a recursive name server), it is
    treated as RCODE=2 (Server failure).

?  I'll need to check the language for consistency (I've already had
my knuckles rapped once for being careless about "recursive name
server", "recursive mode", "recursor", &c.), but you get the idea.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From dwing@cisco.com  Wed Jun  9 23:42:34 2010
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 163D43A6885 for <behave@core3.amsl.com>; Wed,  9 Jun 2010 23:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rPsluAxlSMM for <behave@core3.amsl.com>; Wed,  9 Jun 2010 23:42:29 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 92F883A68BF for <behave@ietf.org>; Wed,  9 Jun 2010 23:42:29 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicLAKMlEEyrR7Hu/2dsb2JhbACHZIEUiViMF3GjKJojhRgEg0s
X-IronPort-AV: E=Sophos;i="4.53,396,1272844800"; d="scan'208";a="142211924"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 10 Jun 2010 06:27:11 +0000
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5A6RAps007926; Thu, 10 Jun 2010 06:27:11 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Wed, 9 Jun 2010 23:27:10 -0700
Message-ID: <066f01cb0865$f57fbea0$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcsIZfUnt0WVfr30Sp2Ue6ikysGNTg==
Cc: behave-chairs@tools.ietf.org
Subject: [BEHAVE] survey on charter update
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Jun 2010 06:42:34 -0000

As we discussed in IETF77, the chairs would like to gather input from
the working group.  We designed a survey which is based on the
presentations given in BEHAVE at IETF77.

We received feedback from ADs that Port Control Protocol is more
appropriate for BEHAVE than SOFTWIRE.  So the questions include some
additions (Port Control Protocol, generic referral object) and
expansion of detail (multicast).

Results of this survey will be made public, including names and email
addresses.  Results of this survey will be *part* of the decision for
BEHAVE's new charter and milestone dates; the survey will not be the
only input into that decision.  Please answer all the questions in the
survey -- there are check boxes for "don't know" which I used when
filling out the survey.

Survey is located at:
http://www.surveymonkey.com/s/QJYNJCB

-d


From brian.e.carpenter@gmail.com  Thu Jun 10 00:20:53 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D34933A68E1 for <behave@core3.amsl.com>; Thu, 10 Jun 2010 00:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.273
X-Spam-Level: 
X-Spam-Status: No, score=-0.273 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sdYqhyruszn3 for <behave@core3.amsl.com>; Thu, 10 Jun 2010 00:20:52 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 6F3113A68D1 for <behave@ietf.org>; Thu, 10 Jun 2010 00:20:52 -0700 (PDT)
Received: by wya21 with SMTP id 21so420091wya.31 for <behave@ietf.org>; Thu, 10 Jun 2010 00:20:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=oh5eX1FMZwnMVABF6Fh5m3VKjiEW6XXeKuLEVSWbYN0=; b=iSnyTOnml5waKaK6ENV1OdN2af7QLnR8dKorhbpzO1DgQTHugm8OXzp/BFHcyC1+t/ lIWn8iZYYHtbVk4C7PRrw5/S7SXUbw/MFdU/nOPW78f0XQeiCWnlxgdFpoLIsRzALhXE Q8jH0eDshi2codXHyb6aLTwmwQxCL8hMjZ0DM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=RfI7ysepsIXRoqJCEURVQw1VLIFg1N4WD8//uX19O871LDCuA1b83R23Uw0se1uyNj vr5zFd/hLro1Wg0etHojYJ8rbmzDBxPCvJ6HHAVGzbQhjNQwY8HVANP9Z+A5mspVlGvT AAQxqHddUBeYpbu1pIs8aDDR6vpef3B28GxDc=
Received: by 10.216.88.83 with SMTP id z61mr1411366wee.85.1276154450734; Thu, 10 Jun 2010 00:20:50 -0700 (PDT)
Received: from [192.168.0.5] (5acb8b9b.bb.sky.com [90.203.139.155]) by mx.google.com with ESMTPS id l60sm450560wej.15.2010.06.10.00.20.49 (version=SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 00:20:49 -0700 (PDT)
Message-ID: <4C10924A.5090705@gmail.com>
Date: Thu, 10 Jun 2010 19:20:42 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <066f01cb0865$f57fbea0$c6f0200a@cisco.com>
In-Reply-To: <066f01cb0865$f57fbea0$c6f0200a@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org, behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] survey on charter update
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Jun 2010 07:20:54 -0000

Slight objection...

In view of the current state of discussion about referrals,
could we say "Generic IP address referral mechanism" instead
of "Generic IP address referral object"?

Regards
   Brian Carpenter

On 2010-06-10 18:27, Dan Wing wrote:
> As we discussed in IETF77, the chairs would like to gather input from
> the working group.  We designed a survey which is based on the
> presentations given in BEHAVE at IETF77.
> 
> We received feedback from ADs that Port Control Protocol is more
> appropriate for BEHAVE than SOFTWIRE.  So the questions include some
> additions (Port Control Protocol, generic referral object) and
> expansion of detail (multicast).
> 
> Results of this survey will be made public, including names and email
> addresses.  Results of this survey will be *part* of the decision for
> BEHAVE's new charter and milestone dates; the survey will not be the
> only input into that decision.  Please answer all the questions in the
> survey -- there are check boxes for "don't know" which I used when
> filling out the survey.
> 
> Survey is located at:
> http://www.surveymonkey.com/s/QJYNJCB
> 
> -d
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

From dwing@cisco.com  Thu Jun 10 00:33:07 2010
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7B753A67A7 for <behave@core3.amsl.com>; Thu, 10 Jun 2010 00:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.299
X-Spam-Level: 
X-Spam-Status: No, score=-9.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99cUL+nqI0lT for <behave@core3.amsl.com>; Thu, 10 Jun 2010 00:33:07 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 1614E3A682A for <behave@ietf.org>; Thu, 10 Jun 2010 00:33:07 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEKAFYxEEyrR7Hu/2dsb2JhbACHZIEUlW9xowmaHoUYBINL
X-IronPort-AV: E=Sophos;i="4.53,397,1272844800"; d="scan'208";a="142261918"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 10 Jun 2010 07:31:54 +0000
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5A7VsC6013157; Thu, 10 Jun 2010 07:31:54 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>, <draft-ietf-behave-ftp64@tools.ietf.org>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: 
Date: Thu, 10 Jun 2010 00:31:54 -0700
Message-ID: <069101cb086f$003a6490$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Acr3lJRfY+LSK0zsSAmayAsFLDea/AQ2iqGA
In-Reply-To: 
Cc: 'Behave Chairs' <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Jun 2010 07:33:08 -0000

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Wednesday, May 19, 2010 1:48 PM
> To: 'behave@ietf.org'
> Cc: 'Behave Chairs'; 'draft-ietf-behave-ftp64@tools.ietf.org'
> Subject: WGLC, draft-ietf-behave-ftp64-03
> 
> This email announces WGLC for draft-ietf-behave-ftp64-03,
> 
>   http://tools.ietf.org/html/draft-ietf-behave-ftp64-03
> 
> Please send comments to the author and the mailing list.
> 
> WGLC ends in two weeks on Wednesday, June 2.

The only comments received were from me.

Iljitsch, please update ftp64 with the comments received and
I will advance the document to our AD.

-d


From dwing@cisco.com  Thu Jun 10 00:33:45 2010
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C53533A6868 for <behave@core3.amsl.com>; Thu, 10 Jun 2010 00:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.742
X-Spam-Level: 
X-Spam-Status: No, score=-8.742 tagged_above=-999 required=5 tests=[AWL=-0.557, BAYES_40=-0.185, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1co4b-gewrvc for <behave@core3.amsl.com>; Thu, 10 Jun 2010 00:33:44 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id AA32E3A67A7 for <behave@ietf.org>; Thu, 10 Jun 2010 00:33:44 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEKAEcyEEyrR7Ht/2dsb2JhbACHZIEUlW9xoxGaHoUYBINL
X-IronPort-AV: E=Sophos;i="4.53,397,1272844800"; d="scan'208";a="142263268"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 10 Jun 2010 07:33:20 +0000
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5A7XKIE009751; Thu, 10 Jun 2010 07:33:20 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <066f01cb0865$f57fbea0$c6f0200a@cisco.com> <4C10924A.5090705@gmail.com>
Date: Thu, 10 Jun 2010 00:33:20 -0700
Message-ID: <06db01cb086f$334ce2e0$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcsIbnRAPgXv0usaSa69e6CDDcIlMgAALqoQ
In-Reply-To: <4C10924A.5090705@gmail.com>
Cc: behave@ietf.org, behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] survey on charter update
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Jun 2010 07:33:45 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Thursday, June 10, 2010 12:21 AM
> To: Dan Wing
> Cc: behave@ietf.org; behave-chairs@tools.ietf.org
> Subject: Re: [BEHAVE] survey on charter update
> 
> Slight objection...
> 
> In view of the current state of discussion about referrals,
> could we say "Generic IP address referral mechanism" instead
> of "Generic IP address referral object"?

Adjusted.

-d


> Regards
>    Brian Carpenter
> 
> On 2010-06-10 18:27, Dan Wing wrote:
> > As we discussed in IETF77, the chairs would like to gather 
> input from
> > the working group.  We designed a survey which is based on the
> > presentations given in BEHAVE at IETF77.
> > 
> > We received feedback from ADs that Port Control Protocol is more
> > appropriate for BEHAVE than SOFTWIRE.  So the questions include some
> > additions (Port Control Protocol, generic referral object) and
> > expansion of detail (multicast).
> > 
> > Results of this survey will be made public, including names 
> and email
> > addresses.  Results of this survey will be *part* of the 
> decision for
> > BEHAVE's new charter and milestone dates; the survey will not be the
> > only input into that decision.  Please answer all the 
> questions in the
> > survey -- there are check boxes for "don't know" which I used when
> > filling out the survey.
> > 
> > Survey is located at:
> > http://www.surveymonkey.com/s/QJYNJCB
> > 
> > -d
> > 
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> > 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From zheng.linfeng@zte.com.cn  Thu Jun 10 00:43:44 2010
Return-Path: <zheng.linfeng@zte.com.cn>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF9773A6847; Thu, 10 Jun 2010 00:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -90.19
X-Spam-Level: 
X-Spam-Status: No, score=-90.19 tagged_above=-999 required=5 tests=[BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001,  MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1re+-WASwaM; Thu, 10 Jun 2010 00:43:43 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 15A323A68E3; Thu, 10 Jun 2010 00:43:42 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 552342650103148; Thu, 10 Jun 2010 15:43:35 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 55465.8064196326; Thu, 10 Jun 2010 15:33:41 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o5A7VlIq090204; Thu, 10 Jun 2010 15:37:56 +0800 (CST) (envelope-from zheng.linfeng@zte.com.cn)
In-Reply-To: <4C10924A.5090705@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFD7EA29CB.9831E24F-ON4825773E.00295873-4825773E.002A16C9@zte.com.cn>
From: zheng.linfeng@zte.com.cn
Date: Thu, 10 Jun 2010 15:32:33 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-06-10 15:37:44, Serialize complete at 2010-06-10 15:37:44
Content-Type: multipart/alternative; boundary="=_alternative 002A16C74825773E_="
X-MAIL: mse2.zte.com.cn o5A7VlIq090204
Cc: behave-bounces@ietf.org, behave@ietf.org, behave-chairs@tools.ietf.org, Dan Wing <dwing@cisco.com>
Subject: [BEHAVE] =?gb2312?b?tPC4tDogUmU6ICBzdXJ2ZXkgb24gY2hhcnRlciB1cGRh?= =?gb2312?b?dGU=?=
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Jun 2010 07:43:45 -0000

This is a multipart message in MIME format.
--=_alternative 002A16C74825773E_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SSBzZWNvbmQgQnJpYW4ncyB3b3Jkcy4NCg0KTGluZmVuZyANClpURQ0KDQogDQoNCg0KDQpCcmlh
biBFIENhcnBlbnRlciA8YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPiANCreivP7IyzogIGJl
aGF2ZS1ib3VuY2VzQGlldGYub3JnDQoyMDEwLTA2LTEwIDE1OjIwDQoNCsrVvP7Iyw0KRGFuIFdp
bmcgPGR3aW5nQGNpc2NvLmNvbT4NCrOty80NCmJlaGF2ZUBpZXRmLm9yZywgYmVoYXZlLWNoYWly
c0B0b29scy5pZXRmLm9yZw0K1vfM4g0KUmU6IFtCRUhBVkVdIHN1cnZleSBvbiBjaGFydGVyIHVw
ZGF0ZQ0KDQoNCg0KDQoNCg0KU2xpZ2h0IG9iamVjdGlvbi4uLg0KDQpJbiB2aWV3IG9mIHRoZSBj
dXJyZW50IHN0YXRlIG9mIGRpc2N1c3Npb24gYWJvdXQgcmVmZXJyYWxzLA0KY291bGQgd2Ugc2F5
ICJHZW5lcmljIElQIGFkZHJlc3MgcmVmZXJyYWwgbWVjaGFuaXNtIiBpbnN0ZWFkDQpvZiAiR2Vu
ZXJpYyBJUCBhZGRyZXNzIHJlZmVycmFsIG9iamVjdCI/DQoNClJlZ2FyZHMNCiAgIEJyaWFuIENh
cnBlbnRlcg0KDQpPbiAyMDEwLTA2LTEwIDE4OjI3LCBEYW4gV2luZyB3cm90ZToNCj4gQXMgd2Ug
ZGlzY3Vzc2VkIGluIElFVEY3NywgdGhlIGNoYWlycyB3b3VsZCBsaWtlIHRvIGdhdGhlciBpbnB1
dCBmcm9tDQo+IHRoZSB3b3JraW5nIGdyb3VwLiAgV2UgZGVzaWduZWQgYSBzdXJ2ZXkgd2hpY2gg
aXMgYmFzZWQgb24gdGhlDQo+IHByZXNlbnRhdGlvbnMgZ2l2ZW4gaW4gQkVIQVZFIGF0IElFVEY3
Ny4NCj4gDQo+IFdlIHJlY2VpdmVkIGZlZWRiYWNrIGZyb20gQURzIHRoYXQgUG9ydCBDb250cm9s
IFByb3RvY29sIGlzIG1vcmUNCj4gYXBwcm9wcmlhdGUgZm9yIEJFSEFWRSB0aGFuIFNPRlRXSVJF
LiAgU28gdGhlIHF1ZXN0aW9ucyBpbmNsdWRlIHNvbWUNCj4gYWRkaXRpb25zIChQb3J0IENvbnRy
b2wgUHJvdG9jb2wsIGdlbmVyaWMgcmVmZXJyYWwgb2JqZWN0KSBhbmQNCj4gZXhwYW5zaW9uIG9m
IGRldGFpbCAobXVsdGljYXN0KS4NCj4gDQo+IFJlc3VsdHMgb2YgdGhpcyBzdXJ2ZXkgd2lsbCBi
ZSBtYWRlIHB1YmxpYywgaW5jbHVkaW5nIG5hbWVzIGFuZCBlbWFpbA0KPiBhZGRyZXNzZXMuICBS
ZXN1bHRzIG9mIHRoaXMgc3VydmV5IHdpbGwgYmUgKnBhcnQqIG9mIHRoZSBkZWNpc2lvbiBmb3IN
Cj4gQkVIQVZFJ3MgbmV3IGNoYXJ0ZXIgYW5kIG1pbGVzdG9uZSBkYXRlczsgdGhlIHN1cnZleSB3
aWxsIG5vdCBiZSB0aGUNCj4gb25seSBpbnB1dCBpbnRvIHRoYXQgZGVjaXNpb24uICBQbGVhc2Ug
YW5zd2VyIGFsbCB0aGUgcXVlc3Rpb25zIGluIHRoZQ0KPiBzdXJ2ZXkgLS0gdGhlcmUgYXJlIGNo
ZWNrIGJveGVzIGZvciAiZG9uJ3Qga25vdyIgd2hpY2ggSSB1c2VkIHdoZW4NCj4gZmlsbGluZyBv
dXQgdGhlIHN1cnZleS4NCj4gDQo+IFN1cnZleSBpcyBsb2NhdGVkIGF0Og0KPiBodHRwOi8vd3d3
LnN1cnZleW1vbmtleS5jb20vcy9RSllOSkNCDQo+IA0KPiAtZA0KPiANCj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gQmVoYXZlIG1haWxpbmcgbGlz
dA0KPiBCZWhhdmVAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9iZWhhdmUNCj4gDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KQmVoYXZlIG1haWxpbmcgbGlzdA0KQmVoYXZlQGlldGYub3JnDQpodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQ0KDQoNCg0K
--=_alternative 002A16C74825773E_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkkgc2Vjb25kIEJyaWFuJ3Mgd29y
ZHMuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5MaW5m
ZW5nIDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+WlRFPGJyPg0K
PGJyPg0KIDwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRy
IHZhbGlnbj10b3A+DQo8dGQgd2lkdGg9MzQlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlm
Ij48Yj5CcmlhbiBFIENhcnBlbnRlciAmbHQ7YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tJmd0
OzwvYj4NCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+t6K8/sjL
OiAmbmJzcDtiZWhhdmUtYm91bmNlc0BpZXRmLm9yZzwvZm9udD4NCjxwPjxmb250IHNpemU9MSBm
YWNlPSJzYW5zLXNlcmlmIj4yMDEwLTA2LTEwIDE1OjIwPC9mb250Pg0KPHRkIHdpZHRoPTY1JT4N
Cjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJp
Z2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+PC9kaXY+DQo8
dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPkRhbiBXaW5nICZsdDtkd2luZ0BjaXNj
by5jb20mZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0
Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj6zrcvNPC9mb250PjwvZGl2Pg0KPHRkPjxm
b250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5iZWhhdmVAaWV0Zi5vcmcsIGJlaGF2ZS1jaGFp
cnNAdG9vbHMuaWV0Zi5vcmc8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxp
Z249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPtb3zOI8L2ZvbnQ+PC9kaXY+
DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlJlOiBbQkVIQVZFXSBzdXJ2ZXkg
b24gY2hhcnRlciB1cGRhdGU8L2ZvbnQ+PC90YWJsZT4NCjxicj4NCjx0YWJsZT4NCjx0ciB2YWxp
Z249dG9wPg0KPHRkPg0KPHRkPjwvdGFibGU+DQo8YnI+PC90YWJsZT4NCjxicj4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTI+PHR0PlNsaWdodCBvYmplY3Rpb24uLi48YnI+DQo8YnI+DQpJbiB2aWV3
IG9mIHRoZSBjdXJyZW50IHN0YXRlIG9mIGRpc2N1c3Npb24gYWJvdXQgcmVmZXJyYWxzLDxicj4N
CmNvdWxkIHdlIHNheSAmcXVvdDtHZW5lcmljIElQIGFkZHJlc3MgcmVmZXJyYWwgbWVjaGFuaXNt
JnF1b3Q7IGluc3RlYWQ8YnI+DQpvZiAmcXVvdDtHZW5lcmljIElQIGFkZHJlc3MgcmVmZXJyYWwg
b2JqZWN0JnF1b3Q7Pzxicj4NCjxicj4NClJlZ2FyZHM8YnI+DQogJm5ic3A7IEJyaWFuIENhcnBl
bnRlcjxicj4NCjxicj4NCk9uIDIwMTAtMDYtMTAgMTg6MjcsIERhbiBXaW5nIHdyb3RlOjxicj4N
CiZndDsgQXMgd2UgZGlzY3Vzc2VkIGluIElFVEY3NywgdGhlIGNoYWlycyB3b3VsZCBsaWtlIHRv
IGdhdGhlciBpbnB1dCBmcm9tPGJyPg0KJmd0OyB0aGUgd29ya2luZyBncm91cC4gJm5ic3A7V2Ug
ZGVzaWduZWQgYSBzdXJ2ZXkgd2hpY2ggaXMgYmFzZWQgb24gdGhlPGJyPg0KJmd0OyBwcmVzZW50
YXRpb25zIGdpdmVuIGluIEJFSEFWRSBhdCBJRVRGNzcuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFdl
IHJlY2VpdmVkIGZlZWRiYWNrIGZyb20gQURzIHRoYXQgUG9ydCBDb250cm9sIFByb3RvY29sIGlz
IG1vcmU8YnI+DQomZ3Q7IGFwcHJvcHJpYXRlIGZvciBCRUhBVkUgdGhhbiBTT0ZUV0lSRS4gJm5i
c3A7U28gdGhlIHF1ZXN0aW9ucyBpbmNsdWRlDQpzb21lPGJyPg0KJmd0OyBhZGRpdGlvbnMgKFBv
cnQgQ29udHJvbCBQcm90b2NvbCwgZ2VuZXJpYyByZWZlcnJhbCBvYmplY3QpIGFuZDxicj4NCiZn
dDsgZXhwYW5zaW9uIG9mIGRldGFpbCAobXVsdGljYXN0KS48YnI+DQomZ3Q7IDxicj4NCiZndDsg
UmVzdWx0cyBvZiB0aGlzIHN1cnZleSB3aWxsIGJlIG1hZGUgcHVibGljLCBpbmNsdWRpbmcgbmFt
ZXMgYW5kIGVtYWlsPGJyPg0KJmd0OyBhZGRyZXNzZXMuICZuYnNwO1Jlc3VsdHMgb2YgdGhpcyBz
dXJ2ZXkgd2lsbCBiZSAqcGFydCogb2YgdGhlIGRlY2lzaW9uDQpmb3I8YnI+DQomZ3Q7IEJFSEFW
RSdzIG5ldyBjaGFydGVyIGFuZCBtaWxlc3RvbmUgZGF0ZXM7IHRoZSBzdXJ2ZXkgd2lsbCBub3Qg
YmUgdGhlPGJyPg0KJmd0OyBvbmx5IGlucHV0IGludG8gdGhhdCBkZWNpc2lvbi4gJm5ic3A7UGxl
YXNlIGFuc3dlciBhbGwgdGhlIHF1ZXN0aW9ucw0KaW4gdGhlPGJyPg0KJmd0OyBzdXJ2ZXkgLS0g
dGhlcmUgYXJlIGNoZWNrIGJveGVzIGZvciAmcXVvdDtkb24ndCBrbm93JnF1b3Q7IHdoaWNoIEkN
CnVzZWQgd2hlbjxicj4NCiZndDsgZmlsbGluZyBvdXQgdGhlIHN1cnZleS48YnI+DQomZ3Q7IDxi
cj4NCiZndDsgU3VydmV5IGlzIGxvY2F0ZWQgYXQ6PGJyPg0KJmd0OyBodHRwOi8vd3d3LnN1cnZl
eW1vbmtleS5jb20vcy9RSllOSkNCPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IC1kPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
PGJyPg0KJmd0OyBCZWhhdmUgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyBCZWhhdmVAaWV0Zi5vcmc8
YnI+DQomZ3Q7IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYmVoYXZlPGJy
Pg0KJmd0OyA8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXzxicj4NCkJlaGF2ZSBtYWlsaW5nIGxpc3Q8YnI+DQpCZWhhdmVAaWV0Zi5vcmc8YnI+DQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZTxicj4NCjxicj4NCjwv
dHQ+PC9mb250Pg0KPGJyPg0K
--=_alternative 002A16C74825773E_=--


From dwing@cisco.com  Thu Jun 10 07:02:27 2010
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE9B428C0F5 for <behave@core3.amsl.com>; Thu, 10 Jun 2010 07:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.763
X-Spam-Level: 
X-Spam-Status: No, score=-9.763 tagged_above=-999 required=5 tests=[AWL=0.836,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayheCPHvfGYG for <behave@core3.amsl.com>; Thu, 10 Jun 2010 07:02:26 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id D684B28C0EC for <behave@ietf.org>; Thu, 10 Jun 2010 07:02:26 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwLAPqMEEyrR7Hu/2dsb2JhbACHZIEUiVmMC3GkE5omhRgEg0s
X-IronPort-AV: E=Sophos;i="4.53,398,1272844800"; d="scan'208";a="142414194"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 10 Jun 2010 14:02:29 +0000
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5AE2Se6011926; Thu, 10 Jun 2010 14:02:28 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
References: 
Date: Thu, 10 Jun 2010 07:02:28 -0700
Message-ID: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Acr3lJRfY+LSK0zsSAmayAsFLDea/AQ2iqGAAA2QjsA=
In-Reply-To: 
Cc: draft-ietf-behave-ftp64@tools.ietf.org, 'Behave Chairs' <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Jun 2010 14:02:27 -0000

Correction (thanks, Dave Thaler):  We need to get 5 reviews before 
advancing the document to IESG.  We currently have 1, and Dave's 
review will bring the count to two.

One of the recent changes to the document has included a new FTP verb
to enable/disable the FTP64 ALG.  This verb is intended to support
IPv6 FTP clients who want to disable the FTP64 ALG because the IPv6
FTP client is implementing its own support for traversal of its NAT64.
I know this new verb has received little comment from the working
group and comments on that idea, and the specific suggestions in the
text, would be valuable.

Please review draft-ietf-behave-ftp64-03.

-d


> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Thursday, June 10, 2010 12:32 AM
> To: 'behave@ietf.org'; 
> 'draft-ietf-behave-ftp64@tools.ietf.org'; 'Iljitsch van Beijnum'
> Cc: 'Behave Chairs'
> Subject: RE: WGLC, draft-ietf-behave-ftp64-03
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com] 
> > Sent: Wednesday, May 19, 2010 1:48 PM
> > To: 'behave@ietf.org'
> > Cc: 'Behave Chairs'; 'draft-ietf-behave-ftp64@tools.ietf.org'
> > Subject: WGLC, draft-ietf-behave-ftp64-03
> > 
> > This email announces WGLC for draft-ietf-behave-ftp64-03,
> > 
> >   http://tools.ietf.org/html/draft-ietf-behave-ftp64-03
> > 
> > Please send comments to the author and the mailing list.
> > 
> > WGLC ends in two weeks on Wednesday, June 2.
> 
> The only comments received were from me.
> 
> Iljitsch, please update ftp64 with the comments received and
> I will advance the document to our AD.
> 
> -d
> 


From ajs@shinkuro.com  Fri Jun 11 09:47:14 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 121723A697F for <behave@core3.amsl.com>; Fri, 11 Jun 2010 09:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.874
X-Spam-Level: *
X-Spam-Status: No, score=1.874 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_50=0.001, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ur1TMj4pfLMj for <behave@core3.amsl.com>; Fri, 11 Jun 2010 09:47:12 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 2EF673A697A for <behave@ietf.org>; Fri, 11 Jun 2010 09:47:12 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 00EC61ECB408 for <behave@ietf.org>; Fri, 11 Jun 2010 16:47:12 +0000 (UTC)
Date: Fri, 11 Jun 2010 12:47:10 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100611164710.GR1471@shinkuro.com>
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Jun 2010 16:47:14 -0000

On Thu, Jun 10, 2010 at 07:02:28AM -0700, Dan Wing wrote:
> Please review draft-ietf-behave-ftp64-03.

Dear colleagues,

I have read the draft.  I have some comments.

First, I confess that I am personally uninterested in continued
support for FTP, so the reasons anyone would go to the work here to
solve the problems it solves are somewhat mysterious to me.  (I say
this not to disparage the work, but so that the Chairs can evaluate
the worth of my review.)  Nevertheless, I think the draft does a
pretty good job of laying out what the issues are and suggesting what
to do.  I find it clear, detailed when it needs to be without being
needlessly verbose, and easy to follow.  I support its publication.

Most of the specific comments below are just nits.  None of them
really need to be addressed for me to support the document, but if
there were changes being made it might be a good idea to address them.

Specific comments:

Multiple places, (nit): "The FTP protocol â€¦" Since the "P" in "FTP"
stands for "protocol", I think that's redundant.

Section 4:    

   Many within the IETF community argue that an IP version mismatch
   between FTP clients and FTP servers is better solved by changing
   clients and servers rather than using a translator.  As such, it is
   recommended to update FTP clients and servers as required for IPv6-
   to-IPv4 translation support where possible, to allow proper operation
   of the FTP protocol without the need for ALGs.

Surely this advice isn't good just because of the bizarre prejudices
of a bunch of IETF geeks?  The reason not to use ALGs and such like is
because things _work better_ the less sludge you have in the way.  I
would restate that this way:

    The best way to solve IP version mismatches between FTP clients
    and FTP servers is to change the clients or servers (or both) in
    order to allow them to communicate natively.  That strategy allows
    the protocol to work as designed and reduces complexity.

Or something like that.  As written, that's a little redundant with
the subsequent text in the draft (which I think is fine as it is).

Section 4.3.2:

   If the address in the EPRT command is not the client's IPv6 address,
   the ALG's response is undefined.

Shouldn't this be an error or something, and not just undefined?

Section 4.5: 

   As such, the behavior of an ALG is undefined when a client issues
   both PASV and PORT.

I assume this is because it's really effectively undefined in RFC 959?
That's how I read the text, anyway: the argument immediately before
makes that argument.

Section 5:

   The suggested time for removal of a server from this case is 7
   days, 1 day when the server indicates EPSV support in its FEAT
   response where it previously did not.

Is there any special reason for those numbers, or do they just seem
like nice round numbers?  I think it might be helpful to have some
justification in the text.

   The main rationale for ignoring the IPv4 address in the 227
   response, even if the client has IPv4 connectivity, most servers
   will only allow a data connection from the same client address as
   seen in the control channel connection, see [Bernstein].

Nit: I think that this needs an "is that" between "connectivity,
most".  Also, the comma before "see" at the end looks wrong.  Use
parentheses around the reference instead, I suggest.

Appendix A, (nit): I guess this should say that the appendix should be
removed prior to publication?

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From dthaler@microsoft.com  Mon Jun 14 16:33:58 2010
Return-Path: <dthaler@microsoft.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E648328C0F0 for <behave@core3.amsl.com>; Mon, 14 Jun 2010 16:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.693
X-Spam-Level: 
X-Spam-Status: No, score=-109.693 tagged_above=-999 required=5 tests=[AWL=-0.583, BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wO2sM3UG00Cj for <behave@core3.amsl.com>; Mon, 14 Jun 2010 16:33:57 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id CD89428C0DC for <behave@ietf.org>; Mon, 14 Jun 2010 16:33:57 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 14 Jun 2010 16:34:01 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.1.160.7; Mon, 14 Jun 2010 16:34:01 -0700
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.101]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 14 Jun 2010 16:33:59 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "draft-ietf-behave-ftp64@tools.ietf.org" <draft-ietf-behave-ftp64@tools.ietf.org>
Thread-Topic: WGLC, draft-ietf-behave-ftp64-03
Thread-Index: Acr3lJRfY+LSK0zsSAmayAsFLDea/AQ2iqGAAA2QjsAA3O4X8A==
Date: Mon, 14 Jun 2010 23:33:58 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF652C060BB7@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
In-Reply-To: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Jun 2010 23:33:59 -0000

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Thursday, June 10, 2010 7:02 AM
> To: behave@ietf.org
> Cc: 'Behave Chairs'; draft-ietf-behave-ftp64@tools.ietf.org
> Subject: RE: WGLC, draft-ietf-behave-ftp64-03
>=20
> Correction (thanks, Dave Thaler):  We need to get 5 reviews before advanc=
ing
> the document to IESG.  We currently have 1, and Dave's review will bring =
the
> count to two.
>=20
> One of the recent changes to the document has included a new FTP verb to
> enable/disable the FTP64 ALG.  This verb is intended to support
> IPv6 FTP clients who want to disable the FTP64 ALG because the IPv6 FTP c=
lient
> is implementing its own support for traversal of its NAT64.
> I know this new verb has received little comment from the working group a=
nd
> comments on that idea, and the specific suggestions in the text, would be
> valuable.
>=20
> Please review draft-ietf-behave-ftp64-03.
>=20
> -d

My review is now at=20
http://research.microsoft.com/en-us/um/people/dthaler/draft-ietf-behave-ftp=
64-03.pdf

Besides editorial nits, my technical feedback is summarized below:

1) It leaves a number of things "undefined".  Since that's what got us into=
 the mess
we have with NAT's today, this doesn't seem like a good idea to me.  I'd ra=
ther=20
at least recommend some default (like what is already in 4.6) rather than s=
aying
they're "undefined".  Perhaps that was the intent, but the word "undefined"=
 in
various places is what I'm pushing back against.

2) The doc specifies that servers SHOULD return a 202 response to an ALGS c=
ommand.
However, I just tried it with a server and got "500 Unknown command." =20
>From RFC 959, 500 seems like a reasonable response and I don't see why exis=
ting servers
would be suddenly declared to be non-compliant to this RFC.

3) The doc contains behavioral statements about clients and servers, not ju=
st ALGs.
For example, Section 5 in particular recommends specific behavior for clien=
ts. =20
Is this behavior already allowed/suggested by any existing RFC or is this s=
pecifying=20
new normative client behavior? If the latter, I believe it would be more ap=
propriate
to either:
a) Move them to a separate doc (my personal preference), or
b) Make this doc be a joint Behave/Ftpext document (which would certainly s=
low it
    down and hence I would argue against this), or
c) Make this doc be a joint Behave/AD-sponsored doc (which seems unlikely i=
f the=20
    AD charters FTPEXT), or
d) Replace this section with a set of requirements for a separate client be=
havior=20
    document to meet (my second preference).

(The common characteristic of all of the above options, and perhaps others =
I didn't
think of, is that Behave is not specifying new FTP client or server behavio=
r, only=20
new ALG behavior.)

-Dave Thaler

From iljitsch@muada.com  Tue Jun 15 03:41:45 2010
Return-Path: <iljitsch@muada.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6272A3A6A1A for <behave@core3.amsl.com>; Tue, 15 Jun 2010 03:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.485
X-Spam-Level: 
X-Spam-Status: No, score=-0.485 tagged_above=-999 required=5 tests=[AWL=-2.115, BAYES_50=0.001, NO_RELAYS=-0.001, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvJwDwdootbi for <behave@core3.amsl.com>; Tue, 15 Jun 2010 03:41:44 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 65B853A6A5A for <behave@ietf.org>; Tue, 15 Jun 2010 03:41:44 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o5FAfbqd043377 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Jun 2010 12:41:38 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF652C060BB7@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 15 Jun 2010 12:41:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CAE64FC-33C1-4CA5-AA08-082DE7AA7965@muada.com>
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF652C060BB7@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>
X-Mailer: Apple Mail (2.1078)
Cc: "draft-ietf-behave-ftp64@tools.ietf.org" <draft-ietf-behave-ftp64@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 15 Jun 2010 10:41:45 -0000

On 15 jun 2010, at 1:33, Dave Thaler wrote:

> 1) It leaves a number of things "undefined".  Since that's what got us =
into the mess
> we have with NAT's today, this doesn't seem like a good idea to me.  =
I'd rather=20
> at least recommend some default (like what is already in 4.6) rather =
than saying
> they're "undefined".  Perhaps that was the intent, but the word =
"undefined" in
> various places is what I'm pushing back against.

This is mostly about the situation where the EPRT arguments are such =
that simple translation in the ALG is impossible. I suppose mandating =
that in these cases the EPRT command is simply left untranslated would =
be a good alternative here.

However, there's also the case where a client issues both PASV and PORT. =
RFC 959 allows this, but I really don't see how this could work. I guess =
we could say to just ignore the PORT command and just handle PASV as =
defined previously...?

> 2) The doc specifies that servers SHOULD return a 202 response to an =
ALGS command.
> However, I just tried it with a server and got "500 Unknown command." =20=

>> =46rom RFC 959, 500 seems like a reasonable response and I don't see =
why existing servers
> would be suddenly declared to be non-compliant to this RFC.

Right. 202 (success despite the fact that the command isn't implemented) =
would probably be the most appropriate response, but any 50x would also =
be ok.

> 3) The doc contains behavioral statements about clients and servers, =
not just ALGs.
> For example, Section 5 in particular recommends specific behavior for =
clients. =20
> Is this behavior already allowed/suggested by any existing RFC

No.

> or is this specifying=20
> new normative client behavior?

Also no.

> (The common characteristic of all of the above options, and perhaps =
others I didn't
> think of, is that Behave is not specifying new FTP client or server =
behavior, only=20
> new ALG behavior.)

We've had that discussion before. Removing this stuff from the document =
upsets the balance between "we hate ALGs" and "we have to be pragmatic" =
and may lead to more objections elsewhere. These are specifically =
recommendations, and where they disagree with the established standard =
this is both supported by solid reasoning (see the Bernstein reference) =
and common practice in the wild.

I suggest we ask the ADs for guidance on this.

Thanks,

Iljitsch=

From iljitsch@muada.com  Tue Jun 15 04:01:48 2010
Return-Path: <iljitsch@muada.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE58A28C0DC for <behave@core3.amsl.com>; Tue, 15 Jun 2010 04:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.573
X-Spam-Level: 
X-Spam-Status: No, score=0.573 tagged_above=-999 required=5 tests=[AWL=-1.057,  BAYES_50=0.001, NO_RELAYS=-0.001, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v++scVCL-wFi for <behave@core3.amsl.com>; Tue, 15 Jun 2010 04:01:45 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 9B8B63A6849 for <behave@ietf.org>; Tue, 15 Jun 2010 04:01:44 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o5FB1c1P043524 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Jun 2010 13:01:39 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=windows-1252
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20100611164710.GR1471@shinkuro.com>
Date: Tue, 15 Jun 2010 13:01:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <324F0AC2-A889-4095-ABE0-4B65239C5963@muada.com>
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com> <20100611164710.GR1471@shinkuro.com>
To: Andrew Sullivan <ajs@shinkuro.com>
X-Mailer: Apple Mail (2.1078)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 15 Jun 2010 11:01:49 -0000

On 11 jun 2010, at 18:47, Andrew Sullivan wrote:

> I find it clear, detailed when it needs to be without being
> needlessly verbose, and easy to follow.  I support its publication.

Thanks!  :-)

> Multiple places, (nit): "The FTP protocol =85" Since the "P" in "FTP"
> stands for "protocol", I think that's redundant.

Well, sometimes it's necessary to draw attention to the protocolness of =
FTP, and saying "the FT protocol" or "the file transfer protocol" would =
be somewhat awkward. In the case of "PIN number" I'd agree with you to a =
larger degree, because there are no other aspects to a PIN than the =
number. But there are FTP servers, FTP clients, FTP sessions... and the =
FTP protocol.

> Section 4:   =20

>   Many within the IETF community argue that an IP version mismatch
>   between FTP clients and FTP servers is better solved by changing
>   clients and servers rather than using a translator.  As such, it is
>   recommended to update FTP clients and servers as required for IPv6-
>   to-IPv4 translation support where possible, to allow proper =
operation
>   of the FTP protocol without the need for ALGs.

> Surely this advice isn't good just because of the bizarre prejudices
> of a bunch of IETF geeks?  The reason not to use ALGs and such like is
> because things _work better_ the less sludge you have in the way.  I
> would restate that this way:

>    The best way to solve IP version mismatches between FTP clients
>    and FTP servers is to change the clients or servers (or both) in
>    order to allow them to communicate natively.  That strategy allows
>    the protocol to work as designed and reduces complexity.

Ok.

> Section 4.3.2:

>   If the address in the EPRT command is not the client's IPv6 address,
>   the ALG's response is undefined.

> Shouldn't this be an error or something, and not just undefined?

See my message to Dave. I think IF we want to define something, it needs =
to be passing the command along unmodified. Of course this won't lead to =
a succesful transfer in 98% of all cases.

> Section 5:

>   The suggested time for removal of a server from this case is 7
>   days, 1 day when the server indicates EPSV support in its FEAT
>   response where it previously did not.

> Is there any special reason for those numbers, or do they just seem
> like nice round numbers?

I'm afraid so. The logic is that this may lead to a timeout so the user =
shouldn't be inconvenienced too often.

> I think it might be helpful to have some
> justification in the text.

I'll add something in the vein of the above.


>   The main rationale for ignoring the IPv4 address in the 227
>   response, even if the client has IPv4 connectivity, most servers
>   will only allow a data connection from the same client address as
>   seen in the control channel connection, see [Bernstein].

> Nit: I think that this needs an "is that" between "connectivity,
> most".  Also, the comma before "see" at the end looks wrong.  Use
> parentheses around the reference instead, I suggest.

Ok.

> Appendix A, (nit): I guess this should say that the appendix should be
> removed prior to publication?

I'll remove it myself in the next update.

Iljitsch=

From ajs@shinkuro.com  Tue Jun 15 06:28:17 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A543A3A6A63 for <behave@core3.amsl.com>; Tue, 15 Jun 2010 06:28:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.44
X-Spam-Level: *
X-Spam-Status: No, score=1.44 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_20=-0.74, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j7YNwLJdC73T for <behave@core3.amsl.com>; Tue, 15 Jun 2010 06:28:17 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id E95A53A687D for <behave@ietf.org>; Tue, 15 Jun 2010 06:28:16 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id C28511ECB41F for <behave@ietf.org>; Tue, 15 Jun 2010 13:28:20 +0000 (UTC)
Date: Tue, 15 Jun 2010 09:28:19 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100615132818.GD75154@shinkuro.com>
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF652C060BB7@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <3CAE64FC-33C1-4CA5-AA08-082DE7AA7965@muada.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3CAE64FC-33C1-4CA5-AA08-082DE7AA7965@muada.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 15 Jun 2010 13:28:17 -0000

On Tue, Jun 15, 2010 at 12:41:43PM +0200, Iljitsch van Beijnum wrote:
> > various places is what I'm pushing back against.
> 
> This is mostly about the situation where the EPRT arguments are such
> that simple translation in the ALG is impossible. I suppose
> mandating that in these cases the EPRT command is simply left
> untranslated would be a good alternative here.

I think specifying something is good, no matter what.  That proposal
seems like the best alternative.
 
> However, there's also the case where a client issues both PASV and
> PORT. RFC 959 allows this, but I really don't see how this could
> work. I guess we could say to just ignore the PORT command and just
> handle PASV as defined previously...?

This was a different thing I was worried about.  Maybe the best answer
is to extend the existing prose a little.  You make a subtle argument
that RFC 959 allows this, but that it's effectively undefined
behaviour (because it's internally inconsistent).  What you could do,
then, is just say that it's undefined behaviour "in the same way that
it seems to be undefined under RFC 959".  That'd be enough to satisfy
me, anyway.  (I of course don't speak for Dave).

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From behcetsarikaya@yahoo.com  Tue Jun 15 11:46:02 2010
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D37F3A6977 for <behave@core3.amsl.com>; Tue, 15 Jun 2010 11:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.832
X-Spam-Level: 
X-Spam-Status: No, score=-1.832 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bo5tr3ReHJH9 for <behave@core3.amsl.com>; Tue, 15 Jun 2010 11:45:56 -0700 (PDT)
Received: from web111409.mail.gq1.yahoo.com (web111409.mail.gq1.yahoo.com [67.195.15.180]) by core3.amsl.com (Postfix) with SMTP id 117FC3A6974 for <behave@ietf.org>; Tue, 15 Jun 2010 11:45:53 -0700 (PDT)
Received: (qmail 42769 invoked by uid 60001); 15 Jun 2010 18:45:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1276627554; bh=j6RI2QeFrza+emuTvyvhz5MY0Q4YlFiPmu6Vyi8A5WE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Y3czd0U2P22vv4h+dK6W0vLGmdfNlgbWfZ0uLem3hVojn2kjZ0iRNjpAZrpQKD/hYg77PQVhwU1hEl1OTds4riAjex/zlzr7A6pQvhigqemzy/j69ROZNnp3IdUAt+CytewfHjS9Ut/aKExfOPtkk+8fZzY+int9SlKROMLdYMk=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xb/rWWZfNvPdVbKjOWnD/5sOTmsnR28xQOrjYJnx+lOWNWFUQ06eKn9YGkc8nxnOr+AG57oSemmxaxdqhwuoxpypAPfBEiXpLkqhkIlaUvmGICP+6A/8NE3KCYVlpD1QkM4xE79Bltm4KHSHhX0pNiGdTUmz7bYeVvQ/5ACROyY=;
Message-ID: <840390.41794.qm@web111409.mail.gq1.yahoo.com>
X-YMail-OSG: fvXRaqgVM1mshN9eJvLBjjqUMvrTHuTSDXfNUsBVRdPBx7T uq2hXrmrmGaN6PxlgkaBOQsxFZN9Oig5_AiJpKPgsSNirJic59jZap03vrNU 9RpzLTLzOKTayEDJUjZinvqqnqWNw_NilMYtokNutTQLobT0z5127kRbjkRO oCOQRDXUg8YSEOF1zKjgI.EVEeYall1njQq.9abMQZJdnefDd0o75pBJE_b1 qVYNACmNjhmi.6bbhVoOa9HX_Muk7prNcGqTpl.zCFfg0slcooaO_zbfVD.M oq3.iSwCWwF3Mbe8.wzKk03bsD.3HptQRcJEl3UjQxHzvuIvVD.ikp9xDvqz 55s9RSGoDGwgIfoQp0vOwi_3R
Received: from [206.16.17.212] by web111409.mail.gq1.yahoo.com via HTTP; Tue, 15 Jun 2010 11:45:54 PDT
X-Mailer: YahooMailRC/397.8 YahooMailWebService/0.8.103.269680
Date: Tue, 15 Jun 2010 11:45:54 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: behave@ietf.org, netext@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [BEHAVE] NAT64 for PMIP
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 15 Jun 2010 18:46:02 -0000

Hello Folks,=0A=A0 There is a new draft on =0ANAT64 for Proxy Mobile IPv6=
=0Aat=0Ahttp://tools.ietf.org/id/draft-sarikaya-behave-netext-nat64-pmip-00=
.txt=0APlease post your comments on the lists.=0A=0ARegards,=0A=0ABehcet=0A=
=0A=0A      

From dwing@cisco.com  Fri Jun 18 10:35:14 2010
Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C47A3A68C7 for <behave@core3.amsl.com>; Fri, 18 Jun 2010 10:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.414
X-Spam-Level: 
X-Spam-Status: No, score=-8.414 tagged_above=-999 required=5 tests=[AWL=-0.415, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FWyo3FZEKHES for <behave@core3.amsl.com>; Fri, 18 Jun 2010 10:35:11 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 235D63A68E9 for <behave@ietf.org>; Fri, 18 Jun 2010 10:35:11 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiQIALhKG0xAZnwM/2dsb2JhbACHY4EUiXiMI3GoDJpThRsEg1I
X-IronPort-AV: E=Sophos;i="4.53,440,1272844800"; d="scan'208";a="123063731"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 18 Jun 2010 17:35:16 +0000
Received: from dwingwxp01 (sjc-vpn7-399.cisco.com [10.21.145.143]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5IHZ9FA010385; Fri, 18 Jun 2010 17:35:15 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
References: <066f01cb0865$f57fbea0$c6f0200a@cisco.com>
Date: Fri, 18 Jun 2010 10:35:08 -0700
Message-ID: <16a801cb0f0c$9cf44730$7844150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsIZfUnt0WVfr30Sp2Ue6ikysGNTgGmg3nQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <066f01cb0865$f57fbea0$c6f0200a@cisco.com>
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] survey on charter update
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 18 Jun 2010 17:35:14 -0000

We have received only 6 responses which is insufficient to help prioritizing
BEHAVE's charter and milestones.

If you have an opinion on what BEHAVE should be working on next -- and I know
everyone has an opinion -- please visit http://www.surveymonkey.com/s/QJYNJCB

-d
 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> Sent: Wednesday, June 09, 2010 11:27 PM
> To: behave@ietf.org
> Cc: behave-chairs@tools.ietf.org
> Subject: [BEHAVE] survey on charter update
> 
> As we discussed in IETF77, the chairs would like to gather input from
> the working group.  We designed a survey which is based on the
> presentations given in BEHAVE at IETF77.
> 
> We received feedback from ADs that Port Control Protocol is more
> appropriate for BEHAVE than SOFTWIRE.  So the questions include some
> additions (Port Control Protocol, generic referral object) and
> expansion of detail (multicast).
> 
> Results of this survey will be made public, including names and email
> addresses.  Results of this survey will be *part* of the decision for
> BEHAVE's new charter and milestone dates; the survey will not be the
> only input into that decision.  Please answer all the questions in the
> survey -- there are check boxes for "don't know" which I used when
> filling out the survey.
> 
> Survey is located at:
> http://www.surveymonkey.com/s/QJYNJCB
> 
> -d
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From rbarnes@bbn.com  Fri Jun 25 11:49:07 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3B103A6897; Fri, 25 Jun 2010 11:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.533
X-Spam-Level: 
X-Spam-Status: No, score=-0.533 tagged_above=-999 required=5 tests=[AWL=-0.534, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id coYONAXV-LL1; Fri, 25 Jun 2010 11:49:02 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id DF15A3A683D; Fri, 25 Jun 2010 11:49:01 -0700 (PDT)
Received: from ros-dhcp192-1-51-71.bbn.com ([192.1.51.71]:50812) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OSDxd-000NrT-7O; Fri, 25 Jun 2010 14:49:10 -0400
Message-Id: <47C35048-FF47-4E92-821B-6EB21343B9B1@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
In-Reply-To: <4BBBD185.7090606@viagenie.ca>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 25 Jun 2010 14:49:07 -0400
References: <188D3671-05E9-40A2-9498-24BAE91B269E@bbn.com> <4BBBD185.7090606@viagenie.ca>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Sat, 26 Jun 2010 11:49:32 -0700
Cc: draft-ietf-behave-turn-ipv6@tools.ietf.org, "behave@ietf.org" <behave@ietf.org>, iesg@ietf.org, secdir@ietf.org
Subject: Re: [BEHAVE] secdir review of draft-ietf-behave-turn-ipv6-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 25 Jun 2010 18:49:07 -0000

Hi Simon,

Just following up, since this draft is up for telechat next week.   
Still waiting to see a revision with the agreed comments.

>> Section 9,
>> Might some of the Teredo / 6to4 loop attacks apply as well?  If  
>> not, why
>> not?
>> -- Spoof 4-to-6 allocate request from relay's v4 address
>> -- Spoof authorization relay's v6 address
>> -- Spoof packet from either of relay's addresses
>
> Sure, these are ways of spoofing IPv6 packets that are enabled by  
> Teredo
> and 6to4. There are many others. Is there a reference we can cite?  
> Would
> citing the Usenix paper be OK?

I think it makes sense to describe the attack here, because it's not  
the same as the Usenix attack.  Here's how it works.  Consider the  
following setup:

               +--------------------------------+
               |                                |
               | 2001:DB8::1        2001:DB8::2 |
+-----------------+                        +------------+
| Tunnel Endpoint |                        | TURN Relay |
+-----------------+                        +------------+
               | 192.0.2.1            192.0.2.2 |
               |                                |
               +--------------------------------+

Suppose an attacker knows that a tunnel endpoint will forward  
encapsulated packets from a given IPv6 address (this doesn't  
necessarily need to be the tunnel endpoint's address).  Suppose he  
then spoofs two packets from this address:
1. An allocate request asking for a v4 address, and
2. A ChannelBind request establishing a channel to the IPv4 address of  
the tunnel endpoint

Then he has set up an amplification attack:
-- The TURN relay will re-encapsulate IPv6 UDP data in v4 and send it  
to the tunnel endpoint
-- The tunnel endpoint will decapsulate packets from the v4 interface  
and send them to v6
So if the attacker sends a packet of the following form...

IPv6: src=2001:DB9::1 dst=2001:DB8::2
UDP:  <ports>
TURN: <channel id>
IPv6: src=2001:DB9::1 dst=2001:DB8::2
UDP:  <ports>
TURN: <channel id>
IPv6: src=2001:DB9::1 dst=2001:DB8::2
UDP:  <ports>
TURN: <channel id>
...

Then the TURN relay and the tunnel endpoint will send it back and  
forth until the last TURN header is consumed, at which point the TURN  
relay will send an empty packet, which the tunnel endpoint will drop.

The amplification potential here is limited by the MTU, so it's not  
huge: IPv6+UDP+TURN takes 334 bytes, so you could get a four-to-one  
amplification out of a 1500-byte packet.  But the attacker could still  
increase traffic volume by sending multiple packets or by establishing  
multiple channels spoofed from different addresses behind the same  
tunnel endpoint.

This attack is kind of like the TURN loop attack in RFC 5766 (which  
definitely still applies here!), but nicer for the attacker, since the  
attacker never needs to see the response to a spoofed packet, since he  
doesn't care about the relayed-transport address.

I think the moral here is that TURN relays shouldn't be involved in  
tunnels -- no need for two v4/v6 compatibility measures at once.  So I  
would suggest the document say something like:
"
It is RECOMMENDED that TURN relays not accept allocation or channel  
binding requests from addresses known to be tunneled, and that they  
not forward data to such addresses.  In particular, a TURN relay MUST  
NOT accept Teredo or 6to4 addresses in these requests.
"


































From zheng.linfeng@zte.com.cn  Sun Jun 27 18:17:58 2010
Return-Path: <zheng.linfeng@zte.com.cn>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 379303A6867 for <behave@core3.amsl.com>; Sun, 27 Jun 2010 18:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.714
X-Spam-Level: 
X-Spam-Status: No, score=-94.714 tagged_above=-999 required=5 tests=[AWL=4.524, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9IyuwV3O9Bi for <behave@core3.amsl.com>; Sun, 27 Jun 2010 18:17:57 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 189B63A68B6 for <behave@ietf.org>; Sun, 27 Jun 2010 18:17:56 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 552341419759111; Mon, 28 Jun 2010 09:17:37 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 53682.1419759111; Mon, 28 Jun 2010 09:11:09 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o5S1EuCK028722 for <behave@ietf.org>; Mon, 28 Jun 2010 09:14:56 +0800 (CST) (envelope-from zheng.linfeng@zte.com.cn)
To: "behave@ietf.org" <behave@ietf.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF9DA4AB30.4972CBCE-ON48257750.0005F680-48257750.00074B7C@zte.com.cn>
From: zheng.linfeng@zte.com.cn
Date: Mon, 28 Jun 2010 09:11:28 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-06-28 09:14:54, Serialize complete at 2010-06-28 09:14:54
Content-Type: multipart/alternative; boundary="=_alternative 00074B7A48257750_="
X-MAIL: mse2.zte.com.cn o5S1EuCK028722
Subject: [BEHAVE] I-D notification and request for comments
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 28 Jun 2010 01:17:58 -0000

This is a multipart message in MIME format.
--=_alternative 00074B7A48257750_=
Content-Type: text/plain; charset="US-ASCII"

Dear behave colleagues, 

Any feedbacks welcomed!

http://datatracker.ietf.org/doc/draft-zheng-pnat-dual-v6addr/

Bests, Linfeng 
ZTE 
--=_alternative 00074B7A48257750_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Dear behave colleagues, </font>
<br>
<br><font size=2 face="sans-serif">Any feedbacks welcomed!</font>
<br>
<br><font size=2 face="sans-serif">http://datatracker.ietf.org/doc/draft-zheng-pnat-dual-v6addr/</font>
<br>
<br><font size=2 face="sans-serif">Bests, Linfeng </font>
<br><font size=2 face="sans-serif">ZTE </font>
--=_alternative 00074B7A48257750_=--


From root@core3.amsl.com  Tue Jun 29 12:15:17 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 566F13A6C24; Tue, 29 Jun 2010 12:15:03 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100629191506.566F13A6C24@core3.amsl.com>
Date: Tue, 29 Jun 2010 12:15:03 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-sctpnat-03.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 29 Jun 2010 19:15:24 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Stream Control Transmission Protocol (SCTP) Network Address Translation
	Author(s)       : R. Stewart, et al.
	Filename        : draft-ietf-behave-sctpnat-03.txt
	Pages           : 26
	Date            : 2010-06-29

Stream Control Transmission Protocol [RFC4960] provides a reliable
communications channel between two end-hosts in many ways similar to
TCP [RFC0793].  With the widespread deployment of Network Address
Translators (NAT), specialized code has been added to NAT for TCP
that allows multiple hosts to reside behind a NAT and yet use only a
single globally unique IPv4 address, even when two hosts (behind a
NAT) choose the same port numbers for their connection.  This
additional code is sometimes classified as Network Address and Port
Translation or NAPT.  To date, specialized code for SCTP has NOT yet
been added to most NATs so that only pure NAT is available.  The end
result of this is that only one SCTP capable host can be behind a
NAT.

This document describes an SCTP specific variant of NAT which
provides similar features of NAPT in the single point and multi-point
traversal scenario.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-sctpnat-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-behave-sctpnat-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-06-29121445.I-D@ietf.org>


--NextPart--

From edward.jankiewicz@sri.com  Tue Jun 29 14:00:49 2010
Return-Path: <edward.jankiewicz@sri.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E62D03A6978 for <behave@core3.amsl.com>; Tue, 29 Jun 2010 14:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level: 
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Iddcq0lyjlJ for <behave@core3.amsl.com>; Tue, 29 Jun 2010 14:00:49 -0700 (PDT)
Received: from mail1.sri.com (mail1.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id 433DB3A69C2 for <behave@ietf.org>; Tue, 29 Jun 2010 14:00:47 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [192.168.1.2] ([unknown] [71.0.228.149]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L4S00KVINP8VFO0@mail.sri.com> for behave@ietf.org; Tue, 29 Jun 2010 14:00:50 -0700 (PDT)
Message-id: <4C2A5EF8.2010803@sri.com>
Date: Tue, 29 Jun 2010 17:00:40 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
To: behave@ietf.org
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
In-reply-to: <07a301cb08a5$8ffab770$c6f0200a@cisco.com>
Cc: draft-ietf-behave-ftp64@tools.ietf.org, 'Behave Chairs' <behave-chairs@tools.ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 29 Jun 2010 21:00:50 -0000

I have reviewed the doc and comments submitted by Dave Thaler and Andrew 
Sullivan, and would support advancing the draft assuming those issues 
are addressed first.  I don't have anything to add at this time.

On 6/10/2010 10:02 AM, Dan Wing wrote:
> Correction (thanks, Dave Thaler):  We need to get 5 reviews before 
> advancing the document to IESG.  We currently have 1, and Dave's 
> review will bring the count to two.
>
> One of the recent changes to the document has included a new FTP verb
> to enable/disable the FTP64 ALG.  This verb is intended to support
> IPv6 FTP clients who want to disable the FTP64 ALG because the IPv6
> FTP client is implementing its own support for traversal of its NAT64.
> I know this new verb has received little comment from the working
> group and comments on that idea, and the specific suggestions in the
> text, would be valuable.
>
> Please review draft-ietf-behave-ftp64-03.
>
> -d
>
>
>   
>> -----Original Message-----
>> From: Dan Wing [mailto:dwing@cisco.com] 
>> Sent: Thursday, June 10, 2010 12:32 AM
>> To: 'behave@ietf.org'; 
>> 'draft-ietf-behave-ftp64@tools.ietf.org'; 'Iljitsch van Beijnum'
>> Cc: 'Behave Chairs'
>> Subject: RE: WGLC, draft-ietf-behave-ftp64-03
>>
>>     
>>> -----Original Message-----
>>> From: Dan Wing [mailto:dwing@cisco.com] 
>>> Sent: Wednesday, May 19, 2010 1:48 PM
>>> To: 'behave@ietf.org'
>>> Cc: 'Behave Chairs'; 'draft-ietf-behave-ftp64@tools.ietf.org'
>>> Subject: WGLC, draft-ietf-behave-ftp64-03
>>>
>>> This email announces WGLC for draft-ietf-behave-ftp64-03,
>>>
>>>   http://tools.ietf.org/html/draft-ietf-behave-ftp64-03
>>>
>>> Please send comments to the author and the mailing list.
>>>
>>> WGLC ends in two weeks on Wednesday, June 2.
>>>       
>> The only comments received were from me.
>>
>> Iljitsch, please update ftp64 with the comments received and
>> I will advance the document to our AD.
>>
>> -d
>>
>>     
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 


From denghui02@gmail.com  Tue Jun 29 19:25:29 2010
Return-Path: <denghui02@gmail.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2628D3A68B7 for <behave@core3.amsl.com>; Tue, 29 Jun 2010 19:25:29 -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=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrQoHJJrzFcS for <behave@core3.amsl.com>; Tue, 29 Jun 2010 19:25:28 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 319D33A6867 for <behave@ietf.org>; Tue, 29 Jun 2010 19:25:28 -0700 (PDT)
Received: by vws10 with SMTP id 10so400298vws.31 for <behave@ietf.org>; Tue, 29 Jun 2010 19:25:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Ox7zrC3ZOssPHXEyjW98kUMJoew7eEAw5mFWzL8avx4=; b=J+Er9K0oHbBqnDUCxv6dc9uOSp9uvgLZ8XFq1qVcw47YVecv0F8fNn7IFBDgqcKADQ cPIW6TzXu6/ddDFfQFFMeE8FH0rGjFS8ymcoPCBYz+/4fZKrObnOIgAmFBb+lOvaXSwQ yrK5ZvvtPqAqz525+KdA9JgK66ZagVa3GB3nk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=AzPCtzjkiwT16xMtNi/xckwTmgXoNnWdJ7AJcagtgeFURIoXeAlkFDcrQF51ucdKco 1Pum4DHyVpxofLYgkDEY2Mc9KQ8LEYAyEnMIqqu9iRff6TF6zNzbxEtQeqYIOqzqJ4D2 BrEhaiKzQyL7XWI5Z2m2VxIHPdgxhSGu1X8KA=
MIME-Version: 1.0
Received: by 10.220.123.9 with SMTP id n9mr4353754vcr.129.1277864735328; Tue,  29 Jun 2010 19:25:35 -0700 (PDT)
Received: by 10.220.199.138 with HTTP; Tue, 29 Jun 2010 19:25:35 -0700 (PDT)
In-Reply-To: <20100629120001.B391A3A6ACE@core3.amsl.com>
References: <20100629120001.B391A3A6ACE@core3.amsl.com>
Date: Wed, 30 Jun 2010 10:25:35 +0800
Message-ID: <AANLkTinM5hYlfEyWneljZ-oo38JH_w9ejkZPf0QUAr5t@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: behave@ietf.org
Content-Type: multipart/alternative; boundary=001636e1ecb39edfe4048a36118b
Subject: [BEHAVE] Fwd: I-D Action:draft-huang-behave-bih-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Jun 2010 02:25:29 -0000

--001636e1ecb39edfe4048a36118b
Content-Type: text/plain; charset=ISO-8859-1

Hello all

We have posted a new draft based on last ietf meeting discussion.
Thanks for your comments.

-Hui

---------- Forwarded message ----------
From: <Internet-Drafts@ietf.org>
Date: 2010/6/29
Subject: I-D Action:draft-huang-behave-bih-00.txt
To: i-d-announce@ietf.org


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

       Title           : Dual Stack Hosts Using "Bump-in-the-Host" (BIH)
       Author(s)       : B. Huang, et al.
       Filename        : draft-huang-behave-bih-00.txt
       Pages           : 24
       Date            : 2010-06-29


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-huang-behave-bih-00.txt

--001636e1ecb39edfe4048a36118b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello all</div>
<div>=A0</div>
<div>We have posted a new draft based on last ietf meeting discussion.</div=
>
<div>Thanks for your comments.</div>
<div>=A0</div>
<div>-Hui<br><br></div>
<div class=3D"gmail_quote">---------- Forwarded message ----------<br>From:=
 <b class=3D"gmail_sendername"></b><span dir=3D"ltr">&lt;<a href=3D"mailto:=
Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a>&gt;</span><br>Date: =
2010/6/29<br>
Subject: I-D Action:draft-huang-behave-bih-00.txt<br>To: <a href=3D"mailto:=
i-d-announce@ietf.org">i-d-announce@ietf.org</a><br><br><br>A New Internet-=
Draft is available from the on-line Internet-Drafts directories.<br><br>=A0=
 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Dual Stack Hosts Using &quot;Bump-i=
n-the-Host&quot; (BIH)<br>
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : B. Huang, et al.<br>=A0 =A0 =A0 =A0F=
ilename =A0 =A0 =A0 =A0: draft-huang-behave-bih-00.txt<br>=A0 =A0 =A0 =A0Pa=
ges =A0 =A0 =A0 =A0 =A0 : 24<br>=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0=
: 2010-06-29<br><br><br>A URL for this Internet-Draft is:<br><a href=3D"htt=
p://www.ietf.org/internet-drafts/draft-huang-behave-bih-00.txt" target=3D"_=
blank">http://www.ietf.org/internet-drafts/draft-huang-behave-bih-00.txt</a=
><br>
<br></div>

--001636e1ecb39edfe4048a36118b--

From iljitsch@muada.com  Wed Jun 30 01:30:27 2010
Return-Path: <iljitsch@muada.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA43B3A6916 for <behave@core3.amsl.com>; Wed, 30 Jun 2010 01:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6YpD7dtD0-V for <behave@core3.amsl.com>; Wed, 30 Jun 2010 01:30:23 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 9D2D63A68B5 for <behave@ietf.org>; Wed, 30 Jun 2010 01:30:21 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o5U8U4EW033675 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jun 2010 10:30:05 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4C2A5EF8.2010803@sri.com>
Date: Wed, 30 Jun 2010 10:30:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <80E2A41A-C39E-4621-8AE7-9E9BC6659FBA@muada.com>
References: <07a301cb08a5$8ffab770$c6f0200a@cisco.com> <4C2A5EF8.2010803@sri.com>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
X-Mailer: Apple Mail (2.1081)
Cc: draft-ietf-behave-ftp64@tools.ietf.org, behave@ietf.org, 'Behave Chairs' <behave-chairs@tools.ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] WGLC, draft-ietf-behave-ftp64-03
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Jun 2010 08:30:28 -0000

On 29 jun 2010, at 23:00, Ed Jankiewicz wrote:

> I have reviewed the doc and comments submitted by Dave Thaler and =
Andrew Sullivan, and would support advancing the draft assuming those =
issues are addressed first.  I don't have anything to add at this time.

Which issues specifically do you mean?

Iljitsch=

From simon.perreault@viagenie.ca  Wed Jun 30 14:33:33 2010
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EAE13A696B; Wed, 30 Jun 2010 14:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNCBXMhXIgz5; Wed, 30 Jun 2010 14:33:31 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by core3.amsl.com (Postfix) with ESMTP id 281433A6873; Wed, 30 Jun 2010 14:33:31 -0700 (PDT)
Received: from balaise.nomis80.org (modemcable245.152-21-96.mc.videotron.ca [96.21.152.245]) by jazz.viagenie.ca (Postfix) with ESMTPSA id D428920D1B; Wed, 30 Jun 2010 17:33:41 -0400 (EDT)
Message-ID: <4C2BB835.5070601@viagenie.ca>
Date: Wed, 30 Jun 2010 17:33:41 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
References: <188D3671-05E9-40A2-9498-24BAE91B269E@bbn.com> <4BBBD185.7090606@viagenie.ca> <47C35048-FF47-4E92-821B-6EB21343B9B1@bbn.com>
In-Reply-To: <47C35048-FF47-4E92-821B-6EB21343B9B1@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-behave-turn-ipv6@tools.ietf.org, "behave@ietf.org" <behave@ietf.org>, iesg@ietf.org, secdir@ietf.org
Subject: Re: [BEHAVE] secdir review of draft-ietf-behave-turn-ipv6-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 30 Jun 2010 21:33:33 -0000

On 06/25/2010 02:49 PM, Richard L. Barnes wrote:
> I think it makes sense to describe the attack here, because it's not the
> same as the Usenix attack.  Here's how it works.  Consider the following
> setup:
> 
>               +--------------------------------+
>               |                                |
>               | 2001:DB8::1        2001:DB8::2 |
> +-----------------+                        +------------+
> | Tunnel Endpoint |                        | TURN Relay |
> +-----------------+                        +------------+
>               | 192.0.2.1            192.0.2.2 |
>               |                                |
>               +--------------------------------+
> 
> Suppose an attacker knows that a tunnel endpoint will forward
> encapsulated packets from a given IPv6 address (this doesn't necessarily
> need to be the tunnel endpoint's address).  Suppose he then spoofs two
> packets from this address:
> 1. An allocate request asking for a v4 address, and
> 2. A ChannelBind request establishing a channel to the IPv4 address of
> the tunnel endpoint
> 
> Then he has set up an amplification attack:
> -- The TURN relay will re-encapsulate IPv6 UDP data in v4 and send it to
> the tunnel endpoint
> -- The tunnel endpoint will decapsulate packets from the v4 interface
> and send them to v6
> So if the attacker sends a packet of the following form...
> 
> IPv6: src=2001:DB9::1 dst=2001:DB8::2
> UDP:  <ports>
> TURN: <channel id>
> IPv6: src=2001:DB9::1 dst=2001:DB8::2
> UDP:  <ports>
> TURN: <channel id>
> IPv6: src=2001:DB9::1 dst=2001:DB8::2
> UDP:  <ports>
> TURN: <channel id>
> ...
> 
> Then the TURN relay and the tunnel endpoint will send it back and forth
> until the last TURN header is consumed, at which point the TURN relay
> will send an empty packet, which the tunnel endpoint will drop.
> 
> The amplification potential here is limited by the MTU, so it's not
> huge: IPv6+UDP+TURN takes 334 bytes, so you could get a four-to-one
> amplification out of a 1500-byte packet.  But the attacker could still
> increase traffic volume by sending multiple packets or by establishing
> multiple channels spoofed from different addresses behind the same
> tunnel endpoint.
> 
> This attack is kind of like the TURN loop attack in RFC 5766 (which
> definitely still applies here!), but nicer for the attacker, since the
> attacker never needs to see the response to a spoofed packet, since he
> doesn't care about the relayed-transport address.

Thanks, I understand now. I'll include a summary of the attack in the text.

> I think the moral here is that TURN relays shouldn't be involved in
> tunnels -- no need for two v4/v6 compatibility measures at once.  So I
> would suggest the document say something like:
> "
> It is RECOMMENDED that TURN relays not accept allocation or channel
> binding requests from addresses known to be tunneled, and that they not
> forward data to such addresses.  In particular, a TURN relay MUST NOT
> accept Teredo or 6to4 addresses in these requests.
> "

Agreed.

Thanks,
Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org
