
From r.niederberger@fz-juelich.de  Mon Feb  1 04:08:40 2010
Return-Path: <r.niederberger@fz-juelich.de>
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 6F9813A6836; Mon,  1 Feb 2010 04:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.63
X-Spam-Level: 
X-Spam-Status: No, score=-0.63 tagged_above=-999 required=5 tests=[AWL=1.019,  BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_62=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 cRCIvRRgVS5d; Mon,  1 Feb 2010 04:08:39 -0800 (PST)
Received: from mailgw-k01.its.kfa-juelich.de (mailgw-k01.its.kfa-juelich.de [134.94.4.24]) by core3.amsl.com (Postfix) with SMTP id 2451E3A67A3; Mon,  1 Feb 2010 04:08:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailgw-k01.its.kfa-juelich.de (Postfix) with ESMTP id 703BE6668B7; Mon,  1 Feb 2010 13:09:10 +0100 (CET)
X-Virus-Scanned: amavisd-new at fz-juelich.de
Received: from mailgw-k01.its.kfa-juelich.de ([127.0.0.1]) by localhost (mailgw-k01.its.kfa-juelich.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ayhpYEtrN20; Mon,  1 Feb 2010 13:09:05 +0100 (CET)
Received: from edge-e01.its.kfa-juelich.de (edge-e01.its.kfa-juelich.de [134.94.4.18]) by mailgw-k01.its.kfa-juelich.de (Postfix) with ESMTP id 022356668B2; Mon,  1 Feb 2010 13:09:05 +0100 (CET)
Received: from hub-k01.ad.fz-juelich.de (134.94.4.36) by edge-e01.its.kfa-juelich.de (134.94.4.18) with Microsoft SMTP Server (TLS) id 8.1.393.1; Mon, 1 Feb 2010 13:09:08 +0100
Received: from mbx-cluster01.ad.fz-juelich.de ([169.254.1.78]) by hub-k01.ad.fz-juelich.de ([134.94.4.36]) with mapi; Mon, 1 Feb 2010 13:09:04 +0100
From: "Niederberger, Ralph" <r.niederberger@fz-juelich.de>
To: 'David Harrington' <ietfdbh@comcast.net>, "'softwires@ietf.org'" <softwires@ietf.org>, "'nsis@ietf.org'" <nsis@ietf.org>, "'Behave@ietf.org'" <Behave@ietf.org>
Date: Mon, 1 Feb 2010 13:09:01 +0100
Thread-Topic: [BEHAVE] [Softwires] Feedback requested for a draft OGF Firewall traversalproposal
Thread-Index: AcqguW76EqjTflIyRM2gV7uaXSMpiAARGVqgAIdr5ZA=
Message-ID: <C10613002E572449980A8A90DEE7624A7C8848492A@MBX-CLUSTER01.ad.fz-juelich.de>
References: <C10613002E572449980A8A90DEE7624A7C8848490E@MBX-CLUSTER01.ad.fz-juelich.de> <075801caa100$cc66edd0$0600a8c0@china.huawei.com>
In-Reply-To: <075801caa100$cc66edd0$0600a8c0@china.huawei.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BEHAVE] [Softwires] Feedback requested for a draft OGF	Firewall traversalproposal
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, 01 Feb 2010 12:08:40 -0000

Dear David,

I have scanned through the RFCs you proposed in your last email.

As far as I see those RFCs use different mechanisms than the protocol I pro=
pose.
Feel free to correct me, if I am wrong.

The MIDCOM workgroup developed a protocol, where an application can connect=
 to a midcom agent to request firewall openings.
So the intelligence is swapped out from the midbox, because it could be to =
complicated to be processed within the midbox.

The experimental RFC 4540 specifies a protocol where the application direct=
ly communicates with the midbox.

The draft protocol proposed now uses inband signaling only. That is:

- you need not know about firewalls on the way
- you need not know about Midbox agents to communicate to
- the firewall reads the control stream, which is structured very simple an=
d generally usable.
  So the code to be used on the midboxes should be rather small.
- in principle it acts very similar to the control session of an FTP commun=
ication, but should be much more secure.
- as already said: it currently is based on ssh for authentication and auth=
orization and uses the "ssh none cipher" mechanism for the signaling part,
  but it could make also sense to use TLS instead.

Best regards

Ralph


-----Urspr=FCngliche Nachricht-----
Von: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] Im Auftrag vo=
n David Harrington
Gesendet: Freitag, 29. Januar 2010 17:34
An: Niederberger, Ralph; softwires@ietf.org; nsis@ietf.org; Behave@ietf.org
Betreff: Re: [BEHAVE] [Softwires] Feedback requested for a draft OGF Firewa=
ll traversalproposal

Hi,

The MIDCOM WG http://tools.ietf.org/wg/midcom/ studied this issue in
depth.

They develop a Framework (RFC3303), a requirements document (RFC
3304), a protocol evaluation (RFC 4097), a MIB module for configuring
middleboxes such as firewalls and network address translators
(RFC5190), a discussion of protocol semantics (RFC 5189), and Session
Traversal Utilities for NAT (STUN) (RFC 5389).

You might also look at NEC's Simple Middlebox Configuration Protocol,
documented in the Experimental RFC 4540.

David Harrington
dbharrington@comcast.net
ietfdbh@comcast.net
dharrington@huawei.com


> -----Original Message-----
> From: softwires-bounces@ietf.org
> [mailto:softwires-bounces@ietf.org] On Behalf Of Niederberger, Ralph
> Sent: Friday, January 29, 2010 3:03 AM
> To: 'softwires@ietf.org'; 'nsis@ietf.org'; 'Behave@ietf.org'
> Subject: [Softwires] Feedback requested for a draft OGF
> Firewall traversalproposal
>
> Dear all,
>
> my name is Ralph Niederberger from Research Center J=FClich, Germany.
>
> I was pointed to your mailing lists by Andrew G.Malis, whio
> is the active
> liasson person between IETF and OGF (Open Grid Forum).
>
> > Ralph and Cees,
> > I've polled the IETF leadership, and there really isn't a
> working group
> that is chartered
> > to discuss a protocol for firewall traversal management or related
> matters.
> > ... there may be individuals in the IETF that are qualified
> to review your
> specification.
> > Your best bet to find them may be to send an email to the
> nsis, softwire,
> and/or
> > behave working group email lists to see if any individuals
> on those lists
> may be interested.
> > ...
>
> I am one of the chairs of the OGF FVGA-WG (Open Grid
> Forum - Firewall virtualization for Grid Applications - Work Group)
> (https://forge.gridforum.org/sf/projects/fvga-wg) which is a
successor
> group of FI-RG (Firewall Issues - Research Group).
>
> We have published two documents in our FI-RG group:
>
>    "Firewall issues overview", GFD-083,
> http://www.ogf.org/documents/GFD.83.pdf
>
> and
>
>    "Requirements on operating Grids in Firewalled
> Environments", GFD-142,
> http://www.ogf.org/documents/GFD.142.pdf
>
> Since we have analyzed in this documents that there are no
> real solutions
> available which can be used seemlessly by grid applications,
> we started with
> our new group
> to design a new one.
>
> So we are currently investigating in designing a new protocol
> for dynamic
> opening of ports within firewalls by authorized user applications.
>
> The draft description I have appended to this email.
> Alternatively you can
> access the document via:
>
>    https://forge.gridforum.org/sf/go/doc15527?nav=3D1
>
> We know that there are many other developments, which already
> have tried to
> solve this issue, but have not seen any solution, which is
> widely used
> and/or provides a similar easy to use interface and broad range of
> usability.
>
> Our intention is to get as much as possible feedback, so that
> we can decide
> as soon as possible, if the direction we are going is the
> right one or if
> we have missed anything  important.
>
> Attached you will find my proposal for a new protocol
> (Firewall Traversal
> Protocol - FiTP) allowing to dynamically open ports on
> firewalls, after the
> client
> application (i.e. the user) has been authorized by a remote server.
>
> The data connection (or connections) for which a port opening
> is requested
> is out of scope to this document. This can be any kind of TCP or UDP
> application.
> The protocol describes the exchange of control connection
> commands, its
> possible control connection stati and the format of control
> commands and
> replies only.
> It is assumed to be a wrapper program surrounding one or more client
> applications for which port openings are requested.
>
> The proposal is currently weak in one point:
>
> 1.) it does not support NAT. If one our both of the sides
> communicating are
> beeing "natted", a hack can be done by the client, if he knows how
> translation will be performed. I.e. if he know which address
> gets translated
> into which address, he can use the natted adresses (client
> and/or server
> addresses) in his opening request. Maybe developments of the
> IETF Behave
> working group could help here.
>
> It could be made smarter in two points (but which would not
> change the idea
> behind).
>
> a.) The FiTP protocol as proposed currently uses ssh NONE
> cipher (developed
> by Pittsburh Supercomputing center, PSC) to allow an encrypted
> authentication and authorization and after this an
> unencrypted phase, where
> control information is exchanged. In principle this is no
> problem, but I
> would be happy, if your IETF groups, looking into this
> protocol draft, could
> think about alternate solutions (one could think about e.g.
> TLS instead).
> The control connection itself would not be effected by this, but the
> proposed protocol could benefit from a smarter solution by not being
> dependent on ssh.
>
> b.) I was asked to change the control connection to use XML
> code. This would
> make control connection strings better human readable, but
> would not change
> internals of the proposed protocol itself. Since the control
> streams are
> defined in a fixed way (fixed length of  session number, protocol,
ip
> address and port strings) the control pakets can be easily
> read by hardware.
> Having a fixed XML format this advantage would not be
> effected (control
> messages would only become a little bit longer). So I am
> neutral concerning
> this design change.
>
> It would be very helpful if you could read this draft
> protocol proposal,
> provide some comments and forward it to the relevant area
> directors and
> group chairs working
> on this topic within IETF, if there are any.
>
> If the protocol itself does not fit into your work area and
> there will be no
> other group currently working on this within IETF, could you
> please advice
> me how to start a new group which could work on this topic or
> alternatively
> how OGF could work on this issue and afterwards could try to
> standardize
> this within IETF.
>
> Hope to here from you soon.
>
> Ralph
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

---------------------------------------------------------------------------=
---------------------
---------------------------------------------------------------------------=
---------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
---------------------------------------------------------------------------=
---------------------
---------------------------------------------------------------------------=
---------------------

From xing@cernet.edu.cn  Mon Feb  1 14:46:09 2010
Return-Path: <xing@cernet.edu.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 583E428C1C3 for <behave@core3.amsl.com>; Mon,  1 Feb 2010 14:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 9zloTOVreZDM for <behave@core3.amsl.com>; Mon,  1 Feb 2010 14:46:08 -0800 (PST)
Received: from s-utl01-sjpop.stsn.net (s-utl01-sjpop.stsn.net [72.254.0.201]) by core3.amsl.com (Postfix) with SMTP id 2089528C1C6 for <behave@ietf.org>; Mon,  1 Feb 2010 14:46:07 -0800 (PST)
Received: from s-utl01-sjpop.stsn.net ([127.0.0.1]) by s-utl01-sjpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2010020114464208098 ; Mon, 01 Feb 2010 14:46:42 -0800
Received: from [10.57.35.194] ([10.57.35.194]) by s-utl01-sjpop.stsn.net; Mon, 1 Feb 2010 14:46:42 -0800
Message-ID: <4B6759CC.5000301@cernet.edu.cn>
Date: Tue, 02 Feb 2010 06:46:36 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
References: <20100125101503.20B5F3A68A3@core3.amsl.com> <4B5D7167.4050801@cernet.edu.cn> <85B2F271FDF6B949B3672BA5A7BB62FB0940CA28@xmb-sjc-236.amer.cisco.com> <4B6039D3.7000200@cernet.edu.cn> <85B2F271FDF6B949B3672BA5A7BB62FB0948600B@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB0948600B@xmb-sjc-236.amer.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Mon, 01 Feb 2010 22:46:09 -0000

Senthil Sivakumar (ssenthil) $B<LF;(B:
> Also noticed this is still present.
> Section 3.1 If the DF flag is not set and the IPv4 packet will result in an IPv6
>    packet larger than 1280 bytes, the IPv4 packet MUST be fragmented
>    prior to translating it.  Since IPv4 packets with DF not set will
>
> The "must" above. I was of the impression that you were change the must. Kentaro provided some text that keeps the must but
> still conveys the idea.
>
> "If the DF flag is not set and the IPv4 packet will result in an IPv6
>    packet larger than 1280 bytes, the packet MUST be fragmented so the
>    resulting IPv6 packet (with Fragment header added to each fragment)
>    will be less than or equal to 1280 bytes. For example, if the packet
>    is fragmented prior to the translation, the IPv4 packets must be
>    fragmented so that their length, excluding the IPv4 header, is at
>    most 1232 bytes (1280 minus 40 for the IPv6 header and 8 for the
>    Fragment header).  The resulting fragments are then translated
>    independently using the logic described below. "
>   

OK, we will use this in the next uploaded version.

regards,

xing

> Thanks
> Senthil
>
> -----Original Message-----
> From: Xing Li [mailto:xing@cernet.edu.cn] 
> Sent: Wednesday, January 27, 2010 8:04 AM
> To: Senthil Sivakumar (ssenthil)
> Cc: behave@ietf.org; Behave Chairs
> Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.txt
>
> Hi$B!$(B Senthil,
>
> Thanks for your reply.
>
> Comparing version 05 and version 06
> (http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-v6v4-xlate-06.txt).
> In version 05 section 1.3 we have cited
>
> "An implementation example of the stateless translation is summarized in [I-D.xli-behave-ivi]. "
>
> However, according to the comments we received from the reviewers, we deleted this sentence. If you think this helps the explanation, we can add it back.
>
> For a complete example flow, we think xlate may not be the right place to do so, since the example flow will mainly present the address translation between IPv4 and IPv6 and the address translation is defined in address-format document, not xlate.
>
> What should we do?
>
> Regards,
>
> xing
>
>
> Senthil Sivakumar (ssenthil) $B<LF;(B:
>   
>> Hi Xing,
>> In one of my previous comment on the earlier draft was to add an example flow and I thought you said you would add it in the future version.
>> I still don$B!G(Bt see it in the latest version.
>>
>> Thanks
>> Senthil
>>
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On 
>> Behalf Of Xing Li
>> Sent: Monday, January 25, 2010 5:25 AM
>> To: behave@ietf.org
>> Cc: Behave Chairs
>> Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.txt
>>
>> Hi, All,
>>
>> For draft-ietf-behave-v6v4-xlate-05 during WGLC, we have 4 reviews, many active discussions on the mailing list and mails to the authors. Thanks for the reviews and comments. Here is a summary of the main issues discussed during WGLC.
>>
>> (1) Discussion if translator is a router (for TTL/Hop-limit handling)
>> Conclusion: Translator is a router. We made the wording consistent in 
>> different places of the document (in sections 1.4, 2.1, 2.7, 3.1 and 
>> 3.6. of the xlate-05)
>>
>> (2) Discussion if the translator handles TTL/Hop limit before or after the translation.
>> Conclusion: Leave it for the implementation.
>>
>> (3) Handling of nested ICMP error messages.
>> Conclusion: This process SHOULD stop at first embedded header and drop the packet if it contains more.
>>
>> (4) Translating pointer in Parameter Problem
>> Conclusion: Move Appendix 1 to sections 2.3 and 3.2 of the xlate-05.
>> Remove ambiguous by setting the pointer value to the first octet of the specific field if that field contains multiple octets.
>>
>> (5) What MUST/SHOULD a translator do if the derivation fails for a source address?
>> Conclusion: Translator drops the packet which contains illegal source address.
>>
>> (6) How to deal with ICMP packets coming from IPv6 addresses that aren't IPv4-translatable?
>> Conclusion: In this case, the translator can ether do stateful translation or map them to an IPv4 address block as a holder for all non IPv4-translatable IPv6 addresses.
>>
>> (7) Other technical and editorial comments We have updated the document based on the suggestions.
>>
>> We also combined sections 2.2 and 2.6 of the xlate-05, since IPv4 UDP with checksum zero is a special case of Transport-layer Header Translation.
>>
>> A general question: Should we add the terminology section in each document (for example in xlate)? Or list all terminologies in the framework document (as the current framework does)?
>>
>> Do we have rough consensus for the above issues? Are there any other issues?
>>
>> Regards,
>>
>> X. Li, C. Bao, F. Baker
>>
>>
>>
>> Internet-Drafts@ietf.org $B<LF;(B:
>>   
>>     
>>> 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           : IP/ICMP Translation Algorithm
>>> 	Author(s)       : X. Li, et al.
>>> 	Filename        : draft-ietf-behave-v6v4-xlate-06.txt
>>> 	Pages           : 28
>>> 	Date            : 2010-01-25
>>>
>>> This document specifies an update to the Stateless IP/ICMP 
>>> Translation Algorithm (SIIT) described in RFC 2765.  The algorithm 
>>> translates between IPv4 and IPv6 packet headers (including ICMP
>>> headers) for both stateless and stateful modes.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-06.t
>>> x
>>> t
>>>
>>> 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.
>>>   
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>>
>>> _______________________________________________
>>> 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 xing@cernet.edu.cn  Mon Feb  1 14:48:05 2010
Return-Path: <xing@cernet.edu.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 31CE228C1E5 for <behave@core3.amsl.com>; Mon,  1 Feb 2010 14:48:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 taIHi8FE1Lzj for <behave@core3.amsl.com>; Mon,  1 Feb 2010 14:48:04 -0800 (PST)
Received: from s-utl01-sjpop.stsn.net (s-utl01-sjpop.stsn.net [72.254.0.201]) by core3.amsl.com (Postfix) with SMTP id 812DD28C1E2 for <behave@ietf.org>; Mon,  1 Feb 2010 14:48:04 -0800 (PST)
Received: from s-utl01-sjpop.stsn.net ([127.0.0.1]) by s-utl01-sjpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2010020114483808108 ; Mon, 01 Feb 2010 14:48:38 -0800
Received: from [10.57.35.194] ([10.57.35.194]) by s-utl01-sjpop.stsn.net; Mon, 1 Feb 2010 14:48:37 -0800
Message-ID: <4B675A3F.1000002@cernet.edu.cn>
Date: Tue, 02 Feb 2010 06:48:31 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Kentaro Ebisawa <ebisawa@sablenetworks.net>
References: <20100125101503.20B5F3A68A3@core3.amsl.com> <4B5D7167.4050801@cernet.edu.cn> <20100131213454.9CC6.B01659E3@sablenetworks.net>
In-Reply-To: <20100131213454.9CC6.B01659E3@sablenetworks.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Mon, 01 Feb 2010 22:48:05 -0000

Kentaro Ebisawa $B<LF;(B:
> Hi Xing,
>
> Thanks for the updated doc.
>   
> The chages seems good to me except for the wording in
>  "3.1. Translating IPv4 Headers into IPv6 Headers"
> which Senthil has pointed out in another e-mail.
>
> I would wait for your response to Senthil and add comment to that thread
> if anything.
>
>   

OK, we will use your suggested words in the next uploaded version.

regards,

xing

> Regards,
>   



From magnus.westerlund@ericsson.com  Wed Feb  3 04:53:05 2010
Return-Path: <magnus.westerlund@ericsson.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 4AAFC3A684E for <behave@core3.amsl.com>; Wed,  3 Feb 2010 04:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.819
X-Spam-Level: 
X-Spam-Status: No, score=-3.819 tagged_above=-999 required=5 tests=[AWL=-1.220, 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 HpZqPjdKI5x7 for <behave@core3.amsl.com>; Wed,  3 Feb 2010 04:53:04 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 0272D3A683A for <behave@ietf.org>; Wed,  3 Feb 2010 04:53:03 -0800 (PST)
X-AuditID: c1b4fb3d-b7b85ae00000097d-25-4b6971c9a5f5
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id E0.5F.02429.9C1796B4; Wed,  3 Feb 2010 13:53:29 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Feb 2010 13:52:12 +0100
Received: from [147.214.183.147] ([147.214.183.147]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Feb 2010 13:52:11 +0100
Message-ID: <4B69717B.1040001@ericsson.com>
Date: Wed, 03 Feb 2010 13:52:11 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <4B59CC9C.9030508@ericsson.com> <4B5D1146.1040302@viagenie.ca>
In-Reply-To: <4B5D1146.1040302@viagenie.ca>
X-Enigmail-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 03 Feb 2010 12:52:11.0954 (UTC) FILETIME=[B40EE120:01CAA4CF]
X-Brightmail-Tracker: AAAAAA==
Cc: draft-ietf-behave-turn-tcp@tools.ietf.org, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] AD comments on draft-ietf-behave-turn-tcp-05
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, 03 Feb 2010 12:53:05 -0000

Hi Simon,

Sorry for being tardy in the response. I will be on vacation next week,
so a quick turn around on this is appreciated.


Simon Perreault skrev 2010-01-25 04:34:
> Magnus Westerlund wrote, on 23/01/10 01:04 AM:
>> 1. Section 3.4 and 5.2, if the Turn server takes time to complete the
>> Connect request, can additional connect or other TURN requests be issued
>> with one connect request outstanding?
> 
> Yes. As with any other STUN/TURN request, processing multiple requests in
> parallel is allowed. The Connect request is special in that its processing
> involves reaching across the Internet, but this is orthogonal.
> 
> Do you think it need to be mentioned explicitly?

Maybe, I think there is some point to say yes, but attempting to limit
the number of simultanous ones. That might be easiest accomplished by
pointing to some existing text around this issue. I can't remember if
that is in STUN, TURN or ICE.

> 
>> 2. Section 5.2: Any consideration for timeout for the TCP connection
>> attempt from the server? Is that purely a server implementation choice?
>> Some minimal value the client can expect? Maybe a option to specify a
>> timeout for the client would be appropriate here?
> 
> Good thinking, thanks.
> 
> However, there are many other timeouts involved in the TCP state machine. I
> don't expect the client to have control over all of them. Is the connection
> timeout important enough to give control over it to the client?
> 
> I don't think client control over TCP timeouts is important given the expected
> use cases for TURN.
> 
> The upper limit of the connection timeout can already be controlled by clients.
> They can just close their connection to the server when it starts taking too
> long. (Does this need to be mentioned explicitly?)
> 
> For the lower limit, how about mentioning that servers MUST ensure at least 10
> seconds before connection timeout?

No, I don't think client control of the timeout is important either.
However, I think there is a point in specifying a minimal timeout the
server may use. And I think that should be larger than 10 seconds, more
like 30s. I know that is an eternity for some real-time applications.
However 10s is not that long if there is need for some end-point
synchronization or other. The expectation here is that the client will
kill the connection attempt if it is no longer needed. Until that the
server should continue to try. But not for ever due to the possibility
to use the TURN server as attack tool in that case.

> 
>> 3. Section 5.2: Why is the initial data buffered? Isn't it better to not
>> read from the socket until its peer TCP connection is available. That
>> way the stream will not advance until the data can be forwarded.
> 
> Whether data is buffered in kernel or user space is irrelevant from the point of
> view of the protocol. It's an implementation detail.

My point is the question on what assumptions the client can make ones
the data has been acked. Especially in cases where the application
adapts the content based on what it manage to send through. Thus having
the document indicate that the server shall buffer, especially the
initial data seems wrong to me.

> 
>> 4. Section 5.3, shouldn't the connection attempt be checked against the
>> permissions before being accepted?
> 
> Yes and no.
> 
> The server needs to check permissions. This is an omission in section 5.3. It is
> a big error that needs to be fixed. Thanks for noticing it.
> 
> However, the permission check needs to happen after the connection is accepted
> but before the ConnectionAttempt indication is sent to the client. This is so
> because a user-space implementation cannot know the identity of the peer before
> calling accept(). So we accept the connection, then drop it if it fails the
> permission check.
> 
> (I recall explaining this on behave@ietf.org, so I wonder why this text isn't
> already in the draft...)

Ok, please get some text in there.

Cheers

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From edward.jankiewicz@sri.com  Wed Feb  3 09:23:13 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 EC9B628C19C; Wed,  3 Feb 2010 09:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level: 
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 HAx8aPyMztL9; Wed,  3 Feb 2010 09:23:13 -0800 (PST)
Received: from mail1.sri.com (mail1.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id 1DCBD28C19B; Wed,  3 Feb 2010 09:23:13 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [192.168.1.4] ([unknown] [71.0.228.150]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0KXA0021A06L3YB0@mail.sri.com>; Wed, 03 Feb 2010 09:20:46 -0800 (PST)
Message-id: <4B69B06D.7080606@sri.com>
Date: Wed, 03 Feb 2010 12:20:45 -0500
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
To: Behave WG <behave@ietf.org>, softwires@ietf.org
Subject: [BEHAVE] PMTU Discovery and ICMPv6 filtering
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, 03 Feb 2010 17:23:14 -0000

One of my colleagues received a long comment on Path MTU Discovery recommendations his organization published and is seeking advice.  I recall this has been discussed several times at IETF meetings, not sure which WG, so this may be redundant.  I've tried to summarize the salient points below, and have two broad questions on this:  Are these points already covered in RFCs (other than 4459, 4890) or current Internet-Drafts? If so, I would appreciate pointers.  If not already covered by current publications, is there interest in documenting the problem and comparing the solutions/drawbacks?

The commenter basically wrote:

IPv4 and IPv6 treat packets exceeding MTU differently - IPv4 will fragment packets that are "too big" but IPv6 will drop the packet and respond with ICMPv6 "too-big" error message. [The subject publication] recommends using the Path MTU Discovery Protocol to discover the end-to-end PMTU, which relies on ICMPv6 error messages. These may be blocked by various "filters" and IPsec gateways, which is the case in many operational networks.

However, even when ICMPv6 is not blocked, IPsec gateways (in tunnel mode) add extra headers, and there can be more than one tunnel header involved (routers also create tunnels). When a "too-big" message is sent the router will return put in its ICMPv6 message the value of the MTU on the next link at layer 2. The host receiving this MTU value in an ICMP message at part of the Path MTU Discovery Protocol has no way of knowing how many extra tunnel headers are added along the path, and so if it just takes the reported MTU value without allowing for these extra headers the process will keep on failing and will not recover. We have seen this behavior in our experiments. 

This can be prevented by ensuring that the maximum packet size sent by the host is smaller than the layer 2 limit: smaller by an amount estimated to be sufficient to allow room for extra headers to be added along the path. Several ways of achieving this are possible: 

(1) Set this reduced MTU value on the on the IPSec gateway LAN interface; the host then discovers this MTU through the PMTUD. 

(2) Statically configure this reduced MTU value into the host and switch off PMTUD. 

(3) Set a reduced MTU at the IPSec gateway WAN interface; The IPSec gateway acts as a host on this interface and so can do packet fragmentation.

(4) Provide the capability in the IPSec gateway to discover the MTU on its WAN interface, subtract the maximum header size that this gateway will add to packets presented on its LAN interface, which the host can then discover through the PMTUD.

Method (4) would be the best solution, but is not currently available in the IPSec gateway products. 
The next best solution is (1), which has been used [in commenter experiments]. This is not as good as (4) because it requires manual intervention, and an understanding of how to calculate the appropriate (reduced) MTU value.  
The next best solution is (2), the only disadvantage of this approach is that only one value can be set for all paths and so the worst case (lowest) value has to be used. In a complex network it may not always be obvious what the worst case path is, and so a conservative estimate may be necessary. Even so this could be preferable in some deployment scenarios since the path-MTU discovery protocol relies on the passage of ICMP messages which are sometimes blocked by firewalls and other security devices.  
Approach (3) is the worst solution since it will cause many IP packets to be fragmented which is inefficient (both because, unlike IPv4, the IPv6 header has to be extended to include the fragmentation offset field, and because it will result the second fragment being very small, i.e. the ratio of user-data to IP header size will be poor). 

It is likely that for immediate use option (1) should be used although (4) would be better if it were supported in the relevant products. 

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


From mcr@sandelman.ca  Thu Feb  4 08:37:34 2010
Return-Path: <mcr@sandelman.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 6B97B3A689B; Thu,  4 Feb 2010 08:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, 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 f2r4vOk8xgC8; Thu,  4 Feb 2010 08:37:33 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by core3.amsl.com (Postfix) with ESMTP id 598403A6B0F; Thu,  4 Feb 2010 08:37:33 -0800 (PST)
Received: from sandelman.ottawa.on.ca (unknown [207.236.207.2]) by relay.sandelman.ca (Postfix) with ESMTPS id BA65634352; Thu,  4 Feb 2010 11:31:52 -0500 (EST)
Received: from marajade.sandelman.ca (unknown [127.0.0.1]) by sandelman.ottawa.on.ca (Postfix) with ESMTP id 906F64E798; Thu,  4 Feb 2010 11:09:59 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-Reply-To: <4B69B06D.7080606@sri.com> 
References: <4B69B06D.7080606@sri.com> 
X-Mailer: MH-E 8.1; nmh 1.1; XEmacs 21.4 (patch 21)
Date: Thu, 04 Feb 2010 11:09:59 -0500
Message-ID: <29721.1265299799@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: softwires@ietf.org, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] PMTU Discovery and ICMPv6 filtering
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, 04 Feb 2010 16:37:34 -0000

{resend with my subscribed email}

Ed, there are a number of things to say.
First, behaviour 4 is mostly described by RFC4301, I believe.
Yes, section 8.2.1.
If you find it is not available, then you need to talk to your vendors.

Behaviour 3 (which, in IPv4 speak, is essentially not copying the DF
bit), is often necessary, but it can mess up the plpmtu mechanism.

Second, PLPMTUD was publiched by the pmtud WG as RFC4821.
This is the best suggestion.

I wrote about what Freeswan/Openswan KLIPS tried to do, which was a
variation of #3, because we wanted the network to work...   it is at:
    http://www.sandelman.ca/SSW/ietf/ipsec/fragment/draft-richardson-ipsec-fragment.txt

Most of these ideas were incorporated into RFC4821.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 



From Washam.Fan@huaweisymantec.com  Thu Feb  4 22:49:13 2010
Return-Path: <Washam.Fan@huaweisymantec.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 D899C28C0E7 for <behave@core3.amsl.com>; Thu,  4 Feb 2010 22:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.582
X-Spam-Level: *
X-Spam-Status: No, score=1.582 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, SUBJ_ALL_CAPS=2.077]
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 vv3HYaR0y8cQ for <behave@core3.amsl.com>; Thu,  4 Feb 2010 22:49:12 -0800 (PST)
Received: from mta1.huaweisymantec.com (unknown [218.17.155.14]) by core3.amsl.com (Postfix) with ESMTP id 5B9253A6DB0 for <behave@ietf.org>; Thu,  4 Feb 2010 22:49:12 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; charset=us-ascii
Received: from hstml01-in.huaweisymantec.com ([172.26.3.41]) by hstga01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KXC00ARMWB25C70@hstga01-in.huaweisymantec.com> for behave@ietf.org; Fri, 05 Feb 2010 14:49:51 +0800 (CST)
Received: from huaweisymantec.com ([127.0.0.1]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KXC00E2VWB2TU20@hstml01-in.huaweisymantec.com> for behave@ietf.org; Fri, 05 Feb 2010 14:49:50 +0800 (CST)
Received: from [10.27.154.141] by hstml01-in.huaweisymantec.com (mshttpd); Fri, 05 Feb 2010 14:49:50 +0800
From: WashamFan <Washam.Fan@huaweisymantec.com>
To: behave@ietf.org
Message-id: <fc9ed4e7196b.4b6c300e@huaweisymantec.com>
Date: Fri, 05 Feb 2010 14:49:50 +0800
X-Mailer: Sun Java(tm) System Messenger Express 6.3-8.03 (built Apr 24 2009; 32bit)
Content-language: en
X-Accept-Language: en
Priority: normal
Subject: [BEHAVE] REQ-5, RFC5508
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, 05 Feb 2010 06:49:14 -0000

Hi,

THe text says

   REQ-5: If a NAT device receives an ICMP Error packet from the private
          realm, and the NAT does not have an active mapping for the
          embedded payload, the NAT SHOULD silently drop the ICMP Error
          packet.  If the NAT has active mapping for the embedded
          payload, then the NAT MUST do the following prior to
          forwarding the packet, unless explicitly overridden by local
          policy:

          a) Revert the IP and transport headers of the embedded IP
             packet to their original form, using the matching mapping;
             and

          b) Leave the ICMP Error type and code unchanged; and

          c) If the NAT enforces Basic NAT function ([NAT-TRAD]), and
             the NAT has active mapping for the IP address that sent the
             ICMP Error, translate the source IP address of the ICMP
             Error packet with the public IP address in the mapping.  In   | 
             all other cases, translate the source IP address of the         |
             ICMP Error packet with its own public IP address.                |

I have a comment on the last sentence. 

Please note that NAPT can have a address pool either. If the ICMP
Error message generated by an intermediate node in the interal realm,
and NAPT has no corresponding active mapping for this node. The
last sentence applies in this case, but which one should be picked up
for mapping if the NAPT has multiple external addresses.

Thanks,
washam



From ssenthil@cisco.com  Fri Feb  5 05:09:55 2010
Return-Path: <ssenthil@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 E07713A6902 for <behave@core3.amsl.com>; Fri,  5 Feb 2010 05:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.561
X-Spam-Level: 
X-Spam-Status: No, score=-9.561 tagged_above=-999 required=5 tests=[AWL=-1.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SUBJ_ALL_CAPS=2.077]
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 C5XmbQnsVLwD for <behave@core3.amsl.com>; Fri,  5 Feb 2010 05:09:55 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 39DCC3A6905 for <behave@ietf.org>; Fri,  5 Feb 2010 05:09:52 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAO+na0urR7Ht/2dsb2JhbACcJ6JQmACEUgQ
X-IronPort-AV: E=Sophos;i="4.49,413,1262563200"; d="scan'208";a="296247998"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 05 Feb 2010 13:10:42 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o15DAgko007673; Fri, 5 Feb 2010 13:10:42 GMT
Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Feb 2010 05:10:42 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 5 Feb 2010 05:10:38 -0800
Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB095995E8@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <fc9ed4e7196b.4b6c300e@huaweisymantec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] REQ-5, RFC5508
Thread-Index: AcqmL3XNq8/Q6Tw7SDi6uY5j9EzqtAAMRIBA
References: <fc9ed4e7196b.4b6c300e@huaweisymantec.com>
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: "WashamFan" <Washam.Fan@huaweisymantec.com>, <behave@ietf.org>
X-OriginalArrivalTime: 05 Feb 2010 13:10:42.0124 (UTC) FILETIME=[9E98E0C0:01CAA664]
Subject: Re: [BEHAVE] REQ-5, RFC5508
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, 05 Feb 2010 13:09:56 -0000

The NAT box itself has a public IP address assigned to its outgoing
interface/port which can be used instead of allocating one from the
address pool but it is upto the implementation.=20

Senthil

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of WashamFan
Sent: Friday, February 05, 2010 1:50 AM
To: behave@ietf.org
Subject: [BEHAVE] REQ-5, RFC5508

Hi,

THe text says

   REQ-5: If a NAT device receives an ICMP Error packet from the private
          realm, and the NAT does not have an active mapping for the
          embedded payload, the NAT SHOULD silently drop the ICMP Error
          packet.  If the NAT has active mapping for the embedded
          payload, then the NAT MUST do the following prior to
          forwarding the packet, unless explicitly overridden by local
          policy:

          a) Revert the IP and transport headers of the embedded IP
             packet to their original form, using the matching mapping;
             and

          b) Leave the ICMP Error type and code unchanged; and

          c) If the NAT enforces Basic NAT function ([NAT-TRAD]), and
             the NAT has active mapping for the IP address that sent the
             ICMP Error, translate the source IP address of the ICMP
             Error packet with the public IP address in the mapping.  In
|=20
             all other cases, translate the source IP address of the
|
             ICMP Error packet with its own public IP address.
|

I have a comment on the last sentence.=20

Please note that NAPT can have a address pool either. If the ICMP Error
message generated by an intermediate node in the interal realm, and NAPT
has no corresponding active mapping for this node. The last sentence
applies in this case, but which one should be picked up for mapping if
the NAPT has multiple external addresses.

Thanks,
washam


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

From jouni.nospam@gmail.com  Fri Feb  5 05:41:46 2010
Return-Path: <jouni.nospam@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 ABE4F28C12E for <behave@core3.amsl.com>; Fri,  5 Feb 2010 05:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.639
X-Spam-Level: 
X-Spam-Status: No, score=-0.639 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 BsKZmMuza-ux for <behave@core3.amsl.com>; Fri,  5 Feb 2010 05:41:46 -0800 (PST)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id B308028C130 for <behave@ietf.org>; Fri,  5 Feb 2010 05:41:45 -0800 (PST)
Received: by ewy28 with SMTP id 28so4290263ewy.28 for <behave@ietf.org>; Fri, 05 Feb 2010 05:42:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=wXitHDFk3m1wzcE7sK5tuX3xcDHcHyxXOOQD+fBkPLU=; b=ljzaWExRu5L8Zx6fLL0GTnYphM3Tk2gtvVg3fFQvT1LZYTD8BywNOOGJ0eutJGRjff hLtsGnHr36etEEMFLaJDV0SZZzBnPfbnzwvuClpFn55DhEabSZkoBk5iAxGYjbU0raw9 KldZYW2dxfLxcwnmQ3XGsNiRF3NG2xa6SW8ts=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=NIQRi+qQvBDSah53OjpB59ZNik4hMrxdH/NkE2j/CBTKHp0SkQ6cBqFlJaA1Gbi5OC /yiIdl0T5E+BYRjYfIwkG4q8GxMst56i5lJ7I5n5tHsS5R+HgZk5af+oDZh1PH1/NVId 39M10RfOHSzmlr/XDQtEJDs32OR5Ymm2qw6bk=
Received: by 10.213.44.18 with SMTP id y18mr571255ebe.69.1265377352515; Fri, 05 Feb 2010 05:42:32 -0800 (PST)
Received: from ?10.254.1.96? ([192.100.123.77]) by mx.google.com with ESMTPS id 15sm943225ewy.8.2010.02.05.05.42.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 05 Feb 2010 05:42:30 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <4B5D7167.4050801@cernet.edu.cn>
Date: Fri, 5 Feb 2010 15:41:35 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <E1C59E7D-207F-452A-BDBD-725BBCEEA02C@gmail.com>
References: <20100125101503.20B5F3A68A3@core3.amsl.com> <4B5D7167.4050801@cernet.edu.cn>
To: Xing Li <xing@cernet.edu.cn>
X-Mailer: Apple Mail (2.1077)
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Fri, 05 Feb 2010 13:41:46 -0000

Hi,

On Jan 25, 2010, at 12:24 PM, Xing Li wrote:

> Hi, All,
> 
> For draft-ietf-behave-v6v4-xlate-05 during WGLC, we have 4 reviews, many
> active discussions on the mailing list and mails to the authors. Thanks
> for the reviews and comments. Here is a summary of the main issues
> discussed during WGLC.
> 
> (1) Discussion if translator is a router (for TTL/Hop-limit handling)
> Conclusion: Translator is a router. We made the wording consistent in
> different places of the document (in sections 1.4, 2.1, 2.7, 3.1 and
> 3.6. of the xlate-05)
> 

In Section 3.1 it says:

   ...
   If the DF bit is set and the MTU of the next-hop interface is less
   than or equal to the total length value of the IPv4 packet minus 20,
   the translator MUST send an ICMPv4 "Fragmentation Needed" error
   message to the IPv4 source address.
   ...
  

Am I just reading/understanding this wrong but shouldn't the text say?

   ...
   If the DF bit is set and the MTU of the next-hop interface is less
   than to the total length value of the IPv4 packet plus 20,
   the translator MUST send an ICMPv4 "Fragmentation Needed" error
   message to the IPv4 source address.
   ...

-Jouni

From Fred.L.Templin@boeing.com  Fri Feb  5 14:16:13 2010
Return-Path: <Fred.L.Templin@boeing.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 526003A67ED; Fri,  5 Feb 2010 14:16:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.076,  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 ai0ArnDhQcxz; Fri,  5 Feb 2010 14:16:11 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 8DE853A6B4A; Fri,  5 Feb 2010 14:16:11 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o15MGxVZ003366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 5 Feb 2010 14:17:00 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o15MGxGZ019974; Fri, 5 Feb 2010 14:16:59 -0800 (PST)
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o15MGxRl019969 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 5 Feb 2010 14:16:59 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-09.nw.nos.boeing.com ([130.247.25.115]) with mapi; Fri, 5 Feb 2010 14:16:59 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>, Behave WG <behave@ietf.org>, "softwires@ietf.org" <softwires@ietf.org>
Date: Fri, 5 Feb 2010 14:17:04 -0800
Thread-Topic: [BEHAVE] PMTU Discovery and ICMPv6 filtering
Thread-Index: Acqk9e5k2HVZbYNmRqmDmJiAEKHTMABrvomw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com>
References: <4B69B06D.7080606@sri.com>
In-Reply-To: <4B69B06D.7080606@sri.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BEHAVE] PMTU Discovery and ICMPv6 filtering
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, 05 Feb 2010 22:16:13 -0000

Hi Ed,

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of Ed Jankiewicz
> Sent: Wednesday, February 03, 2010 9:21 AM
> To: Behave WG; softwires@ietf.org
> Subject: [BEHAVE] PMTU Discovery and ICMPv6 filtering
>=20
> One of my colleagues received a long comment on Path MTU Discovery recomm=
endations his organization
> published and is seeking advice.  I recall this has been discussed severa=
l times at IETF meetings,
> not sure which WG, so this may be redundant.  I've tried to summarize the=
 salient points below, and
> have two broad questions on this:  Are these points already covered in RF=
Cs (other than 4459, 4890)
> or current Internet-Drafts? If so, I would appreciate pointers.  If not a=
lready covered by current
> publications, is there interest in documenting the problem and comparing =
the solutions/drawbacks?
>=20
> The commenter basically wrote:
>=20
> IPv4 and IPv6 treat packets exceeding MTU differently - IPv4 will fragmen=
t packets that are "too big"
> but IPv6 will drop the packet and respond with ICMPv6 "too-big" error mes=
sage. [The subject
> publication] recommends using the Path MTU Discovery Protocol to discover=
 the end-to-end PMTU, which
> relies on ICMPv6 error messages. These may be blocked by various "filters=
" and IPsec gateways, which
> is the case in many operational networks.
>=20
> However, even when ICMPv6 is not blocked, IPsec gateways (in tunnel mode)=
 add extra headers, and
> there can be more than one tunnel header involved (routers also create tu=
nnels). When a "too-big"
> message is sent the router will return put in its ICMPv6 message the valu=
e of the MTU on the next
> link at layer 2. The host receiving this MTU value in an ICMP message at =
part of the Path MTU
> Discovery Protocol has no way of knowing how many extra tunnel headers ar=
e added along the path, and
> so if it just takes the reported MTU value without allowing for these ext=
ra headers the process will
> keep on failing and will not recover. We have seen this behavior in our e=
xperiments.
>=20
> This can be prevented by ensuring that the maximum packet size sent by th=
e host is smaller than the
> layer 2 limit: smaller by an amount estimated to be sufficient to allow r=
oom for extra headers to be
> added along the path. Several ways of achieving this are possible:
>=20
> (1) Set this reduced MTU value on the on the IPSec gateway LAN interface;=
 the host then discovers
> this MTU through the PMTUD.
>=20
> (2) Statically configure this reduced MTU value into the host and switch =
off PMTUD.
>=20
> (3) Set a reduced MTU at the IPSec gateway WAN interface; The IPSec gatew=
ay acts as a host on this
> interface and so can do packet fragmentation.
>=20
> (4) Provide the capability in the IPSec gateway to discover the MTU on it=
s WAN interface, subtract
> the maximum header size that this gateway will add to packets presented o=
n its LAN interface, which
> the host can then discover through the PMTUD.
>=20
> Method (4) would be the best solution, but is not currently available in =
the IPSec gateway products.
> The next best solution is (1), which has been used [in commenter experime=
nts]. This is not as good as
> (4) because it requires manual intervention, and an understanding of how =
to calculate the appropriate
> (reduced) MTU value.
> The next best solution is (2), the only disadvantage of this approach is =
that only one value can be
> set for all paths and so the worst case (lowest) value has to be used. In=
 a complex network it may
> not always be obvious what the worst case path is, and so a conservative =
estimate may be necessary.
> Even so this could be preferable in some deployment scenarios since the p=
ath-MTU discovery protocol
> relies on the passage of ICMP messages which are sometimes blocked by fir=
ewalls and other security
> devices.
> Approach (3) is the worst solution since it will cause many IP packets to=
 be fragmented which is
> inefficient (both because, unlike IPv4, the IPv6 header has to be extende=
d to include the
> fragmentation offset field, and because it will result the second fragmen=
t being very small, i.e. the
> ratio of user-data to IP header size will be poor).
>=20
> It is likely that for immediate use option (1) should be used although (4=
) would be better if it were
> supported in the relevant products.

(1) seems like a safe option at face value, but can lead
to undesirable inefficiencies. Consider for example the
diagram below:

            L1    L2               L3
            |     |                |
        W --|--R--|--GW1<=3D=3D=3D=3D>GW2--|--Z
            |     |   (Internet)   |
               X--|     L4, L5,
               Y--|     L6, etc.

Here, we have a tunnel beteen 'GW1' and 'GW2' over the
Internet to connect two networks. 'GW1' sets a reduced
MTU 'M' on its LAN interface connected to link 'L2', and
also advertises 'M' in the Router Advertisements it sends
on 'L2'. Hosts 'X' and 'Y' pick up the reduced MTU from
the RA and limit the size of the packets they send to at
most 'M' bytes. But, host 'W' connected to link 'L1' does
not see the MTU reduction, and hence will routinely send
packets larger than 'M' to any hosts beyond router 'R'
such as 'X', 'Y' and 'Z'. These packets will be dropped
with an ICMPv6 PTB returned, then 'W' will be forced to
reduce its packet size and retransmit. The only way to
prevent this is to drive the reduced MTU 'M' deeply into
the entire network stacked up behind 'GW1', which may
contain arbitrarily many additional routers and links.

Now, even if the reduced MTU 'M' were propagated deeply
throughout the 'GW1' network, if most communications
remain localized hosts would only be able to use a packet
size of at most 'M' even if their links natively support
a much larger MTU. Consider for example that link 'L2'
in the diagram has a native MTU of 9kb, but the effective
MTU across the 'GW1'<=3D=3D=3D=3D>'GW2' tunnel is only 1400. 'GW1'
will advertise 1400 on link 'L1', and communications
betweenhosts 'X' and 'Y' will be restricted to using at
most 1400 byte packets when they could have used 9kb.

There are a couple of factors to consider in terms of
what might be a better solution. First, what are the
expected data rates over the 'GW1'<=3D=3D=3D=3D>'GW2' tunnel,
and second what are the performance characteristics of
those gateways? If the data rates are such that GW1 and
GW2 are already operating at their peak performance even
without taking on any additional processing overhead,
then the best solution would be to make sure that all
links over which the tunnel might travel (e.g., 'L4',
'L5', 'L6', etc.) are large enough to "hide" the tunnel
encapsulation artifact. For example, if all links 'L4'
'L5', 'L6', etc. configure a native MTU of no smaller
than 1600 and the encapsulation overhead for the tunnel
is 100 bytes, then all routers and hosts on the LAN side
of 'GW1' would be able to happily use a 1500 MTU. If the
MTUs of 'L4', etc. cannot be controlled, however, then
there is no recourse but to use option (1) and cope with
the inefficiencies.

On the other hand, if the data rates across the tunnel
are nominal and/or 'GW1' and 'GW2' have more than
sufficient processing capability to take on a modest
amount of additional overhead, the GWs can use tunnel
fragmentation so that 'GW1' can present a solid MTU on
its LAN side interface that does not reflect the size
of the tunnel encapsulation headers. If the tunnel
fragmentation could accommodate an MTU of at least 1500
in this way, then 'GW1' would be able to observe the
"de facto Internet cell size" of 1500. If we further
assume that the vast majority of hosts in the world
today either limit their packet sizes to no more than
1500 bytes or are willing to assume the risk of silent
loss of packets larger than 1500 due to MTU restrictions,
then there is no need to place artificial restrictions
on the size of packets that can be used within the 'GW1'
network. This latter class of hosts (those that send
packets larger than 1500) would be best served to use
their own host-based MTU probing mechanisms for sending=20
packets larger than 1500 in case the network is somehow
silently dropping PMTUD messages. RFC4821 was specifically
designed for this purpose.

End result - whenever it is practically possible, tunnel
routers should use tunnel fragmentation and hosts should
use RFC4821.

Fred
fred.l.templin@boeing.com
    =20
> --
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research
> Supporting DISA Standards Engineering Branch
> 732-389-1003 or  ed.jankiewicz@sri.com
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From xing@cernet.edu.cn  Sat Feb  6 04:16:08 2010
Return-Path: <xing@cernet.edu.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 DE1853A6880 for <behave@core3.amsl.com>; Sat,  6 Feb 2010 04:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.001
X-Spam-Level: *
X-Spam-Status: No, score=1.001 tagged_above=-999 required=5 tests=[AWL=-0.088,  BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, FH_HAS_XAIMC=2.696]
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 vaaGnYUrSHw0 for <behave@core3.amsl.com>; Sat,  6 Feb 2010 04:16:07 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 2E9D23A6C04 for <behave@ietf.org>; Sat,  6 Feb 2010 04:16:06 -0800 (PST)
Received: from [192.168.1.101]([125.34.50.47]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b6db469; Sat, 06 Feb 2010 20:16:27 +0800
Message-ID: <4B6CAA1D.9080402@cernet.edu.cn>
Date: Sat, 06 Feb 2010 07:30:37 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
References: <20100125101503.20B5F3A68A3@core3.amsl.com> <4B5D7167.4050801@cernet.edu.cn> <85B2F271FDF6B949B3672BA5A7BB62FB0940CA28@xmb-sjc-236.amer.cisco.com> <4B6039D3.7000200@cernet.edu.cn> <85B2F271FDF6B949B3672BA5A7BB62FB09485ADB@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB09485ADB@xmb-sjc-236.amer.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 0mXajdXB
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Sat, 06 Feb 2010 12:16:09 -0000

Senthil Sivakumar (ssenthil) $B<LF;(B:
> Hi Xing,
> My preference is to have an example flow in this document. It helps to visualize and understand. I really don$B!G(Bt understand why it does not belong  
> in this draft. 
>   

OK. we will add an appendix containing the work-flow example of
stateless translation. The example of stateful translation is already in
the xlate-stateful document.

regards,

xing
> Thanks
> Senthil
>
> -----Original Message-----
> From: Xing Li [mailto:xing@cernet.edu.cn] 
> Sent: Wednesday, January 27, 2010 8:04 AM
> To: Senthil Sivakumar (ssenthil)
> Cc: behave@ietf.org; Behave Chairs
> Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.txt
>
> Hi$B!$(B Senthil,
>
> Thanks for your reply.
>
> Comparing version 05 and version 06
> (http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-v6v4-xlate-06.txt).
> In version 05 section 1.3 we have cited
>
> "An implementation example of the stateless translation is summarized in [I-D.xli-behave-ivi]. "
>
> However, according to the comments we received from the reviewers, we deleted this sentence. If you think this helps the explanation, we can add it back.
>
> For a complete example flow, we think xlate may not be the right place to do so, since the example flow will mainly present the address translation between IPv4 and IPv6 and the address translation is defined in address-format document, not xlate.
>
> What should we do?
>
> Regards,
>
> xing
>
>
> Senthil Sivakumar (ssenthil) $B<LF;(B:
>   
>> Hi Xing,
>> In one of my previous comment on the earlier draft was to add an example flow and I thought you said you would add it in the future version.
>> I still don$B!G(Bt see it in the latest version.
>>
>> Thanks
>> Senthil
>>
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On 
>> Behalf Of Xing Li
>> Sent: Monday, January 25, 2010 5:25 AM
>> To: behave@ietf.org
>> Cc: Behave Chairs
>> Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.txt
>>
>> Hi, All,
>>
>> For draft-ietf-behave-v6v4-xlate-05 during WGLC, we have 4 reviews, many active discussions on the mailing list and mails to the authors. Thanks for the reviews and comments. Here is a summary of the main issues discussed during WGLC.
>>
>> (1) Discussion if translator is a router (for TTL/Hop-limit handling)
>> Conclusion: Translator is a router. We made the wording consistent in 
>> different places of the document (in sections 1.4, 2.1, 2.7, 3.1 and 
>> 3.6. of the xlate-05)
>>
>> (2) Discussion if the translator handles TTL/Hop limit before or after the translation.
>> Conclusion: Leave it for the implementation.
>>
>> (3) Handling of nested ICMP error messages.
>> Conclusion: This process SHOULD stop at first embedded header and drop the packet if it contains more.
>>
>> (4) Translating pointer in Parameter Problem
>> Conclusion: Move Appendix 1 to sections 2.3 and 3.2 of the xlate-05.
>> Remove ambiguous by setting the pointer value to the first octet of the specific field if that field contains multiple octets.
>>
>> (5) What MUST/SHOULD a translator do if the derivation fails for a source address?
>> Conclusion: Translator drops the packet which contains illegal source address.
>>
>> (6) How to deal with ICMP packets coming from IPv6 addresses that aren't IPv4-translatable?
>> Conclusion: In this case, the translator can ether do stateful translation or map them to an IPv4 address block as a holder for all non IPv4-translatable IPv6 addresses.
>>
>> (7) Other technical and editorial comments We have updated the document based on the suggestions.
>>
>> We also combined sections 2.2 and 2.6 of the xlate-05, since IPv4 UDP with checksum zero is a special case of Transport-layer Header Translation.
>>
>> A general question: Should we add the terminology section in each document (for example in xlate)? Or list all terminologies in the framework document (as the current framework does)?
>>
>> Do we have rough consensus for the above issues? Are there any other issues?
>>
>> Regards,
>>
>> X. Li, C. Bao, F. Baker
>>
>>
>>
>> Internet-Drafts@ietf.org $B<LF;(B:
>>   
>>     
>>> 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           : IP/ICMP Translation Algorithm
>>> 	Author(s)       : X. Li, et al.
>>> 	Filename        : draft-ietf-behave-v6v4-xlate-06.txt
>>> 	Pages           : 28
>>> 	Date            : 2010-01-25
>>>
>>> This document specifies an update to the Stateless IP/ICMP 
>>> Translation Algorithm (SIIT) described in RFC 2765.  The algorithm 
>>> translates between IPv4 and IPv6 packet headers (including ICMP
>>> headers) for both stateless and stateful modes.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-06.t
>>> x
>>> t
>>>
>>> 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.
>>>   
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>>
>>> _______________________________________________
>>> 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 root@core3.amsl.com  Sat Feb  6 20:30:02 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 342793A6F4C; Sat,  6 Feb 2010 20:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100207043002.342793A6F4C@core3.amsl.com>
Date: Sat,  6 Feb 2010 20:30:02 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-framework-06.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: Sun, 07 Feb 2010 04:30:02 -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           : Framework for IPv4/IPv6 Translation
	Author(s)       : F. Baker, et al.
	Filename        : draft-ietf-behave-v6v4-framework-06.txt
	Pages           : 30
	Date            : 2010-02-06

This note describes a framework for IPv4/IPv6 translation.  This is
in the context of replacing NAT-PT, which was deprecated by RFC 4966,
and to enable networks to have IPv4 and IPv6 coexist in a somewhat
rational manner while transitioning to an IPv6 network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-framework-06.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-v6v4-framework-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xing@cernet.edu.cn  Sat Feb  6 21:46:16 2010
Return-Path: <xing@cernet.edu.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 21E5B28C0D9 for <behave@core3.amsl.com>; Sat,  6 Feb 2010 21:46:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.061
X-Spam-Level: **
X-Spam-Status: No, score=2.061 tagged_above=-999 required=5 tests=[AWL=0.475,  BAYES_05=-1.11, FH_HAS_XAIMC=2.696]
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 7Ad4yY27fDIW for <behave@core3.amsl.com>; Sat,  6 Feb 2010 21:46:15 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id BFDA628C0D7 for <behave@ietf.org>; Sat,  6 Feb 2010 21:46:14 -0800 (PST)
Received: from [59.66.24.89]([59.66.24.89]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm104b6e63b3; Sun, 07 Feb 2010 13:46:58 +0800
Message-ID: <4B6E53CE.3090805@cernet.edu.cn>
Date: Sun, 07 Feb 2010 13:46:54 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: jouni korhonen <jouni.nospam@gmail.com>
References: <20100125101503.20B5F3A68A3@core3.amsl.com>	<4B5D7167.4050801@cernet.edu.cn> <E1C59E7D-207F-452A-BDBD-725BBCEEA02C@gmail.com>
In-Reply-To: <E1C59E7D-207F-452A-BDBD-725BBCEEA02C@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 9qAzzdXB
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Sun, 07 Feb 2010 05:46:16 -0000

jouni korhonen 写道:

You are correct. Thanks. We will make corrections in the next version.

Regards,

xing

> Hi,
>
> On Jan 25, 2010, at 12:24 PM, Xing Li wrote:
>
>   
>> Hi, All,
>>
>> For draft-ietf-behave-v6v4-xlate-05 during WGLC, we have 4 reviews, many
>> active discussions on the mailing list and mails to the authors. Thanks
>> for the reviews and comments. Here is a summary of the main issues
>> discussed during WGLC.
>>
>> (1) Discussion if translator is a router (for TTL/Hop-limit handling)
>> Conclusion: Translator is a router. We made the wording consistent in
>> different places of the document (in sections 1.4, 2.1, 2.7, 3.1 and
>> 3.6. of the xlate-05)
>>
>>     
>
> In Section 3.1 it says:
>
>    ...
>    If the DF bit is set and the MTU of the next-hop interface is less
>    than or equal to the total length value of the IPv4 packet minus 20,
>    the translator MUST send an ICMPv4 "Fragmentation Needed" error
>    message to the IPv4 source address.
>    ...
>   
>
> Am I just reading/understanding this wrong but shouldn't the text say?
>
>    ...
>    If the DF bit is set and the MTU of the next-hop interface is less
>    than to the total length value of the IPv4 packet plus 20,
>    the translator MUST send an ICMPv4 "Fragmentation Needed" error
>    message to the IPv4 source address.
>    ...
>
> -Jouni
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>
>   


From root@core3.amsl.com  Sat Feb  6 22:45:18 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 E97D23A7004; Sat,  6 Feb 2010 22:45:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100207064512.E97D23A7004@core3.amsl.com>
Date: Sat,  6 Feb 2010 22:45:03 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-07.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: Sun, 07 Feb 2010 06:45:19 -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           : IP/ICMP Translation Algorithm
	Author(s)       : X. Li, et al.
	Filename        : draft-ietf-behave-v6v4-xlate-07.txt
	Pages           : 31
	Date            : 2010-02-06

This document specifies an update to the Stateless IP/ICMP
Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
translates between IPv4 and IPv6 packet headers (including ICMP
headers) for both stateless and stateful modes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-07.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-v6v4-xlate-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xing@cernet.edu.cn  Sat Feb  6 23:17:52 2010
Return-Path: <xing@cernet.edu.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 036D03A6FB5 for <behave@core3.amsl.com>; Sat,  6 Feb 2010 23:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.068
X-Spam-Level: ***
X-Spam-Status: No, score=3.068 tagged_above=-999 required=5 tests=[AWL=-0.771,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696, MIME_CHARSET_FARAWAY=2.45,  MISSING_HEADERS=1.292]
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 IwLdIM66almz for <behave@core3.amsl.com>; Sat,  6 Feb 2010 23:17:51 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 9C8863A68FE for <behave@ietf.org>; Sat,  6 Feb 2010 23:17:50 -0800 (PST)
Received: from [59.66.24.89]([59.66.24.89]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b6e7937; Sun, 07 Feb 2010 15:18:46 +0800
Message-ID: <4B6E6953.2080901@cernet.edu.cn>
Date: Sun, 07 Feb 2010 15:18:43 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
CC: behave@ietf.org
References: <20100207043002.342793A6F4C@core3.amsl.com>
In-Reply-To: <20100207043002.342793A6F4C@core3.amsl.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 96qZBeXB
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-framework-06.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: Sun, 07 Feb 2010 07:17:52 -0000

We have uploaded a new version of the framework document based on the
comments received. The diff is at
http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-v6v4-framework-06.txt

Regards,

xing


Internet-Drafts@ietf.org дµÀ:
> 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           : Framework for IPv4/IPv6 Translation
> 	Author(s)       : F. Baker, et al.
> 	Filename        : draft-ietf-behave-v6v4-framework-06.txt
> 	Pages           : 30
> 	Date            : 2010-02-06
>
> This note describes a framework for IPv4/IPv6 translation.  This is
> in the context of replacing NAT-PT, which was deprecated by RFC 4966,
> and to enable networks to have IPv4 and IPv6 coexist in a somewhat
> rational manner while transitioning to an IPv6 network.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-framework-06.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.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From xing@cernet.edu.cn  Sat Feb  6 23:24:06 2010
Return-Path: <xing@cernet.edu.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 7CDFC3A68FE for <behave@core3.amsl.com>; Sat,  6 Feb 2010 23:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.223
X-Spam-Level: ***
X-Spam-Status: No, score=3.223 tagged_above=-999 required=5 tests=[AWL=-0.617,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696, MIME_CHARSET_FARAWAY=2.45,  MISSING_HEADERS=1.292]
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 HKXEdjdCqLod for <behave@core3.amsl.com>; Sat,  6 Feb 2010 23:24:05 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 2E46E3A6834 for <behave@ietf.org>; Sat,  6 Feb 2010 23:24:04 -0800 (PST)
Received: from [59.66.24.89]([59.66.24.89]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm1d4b6e7aad; Sun, 07 Feb 2010 15:25:00 +0800
Message-ID: <4B6E6AD1.8040600@cernet.edu.cn>
Date: Sun, 07 Feb 2010 15:25:05 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
CC: behave@ietf.org
References: <20100207064512.E97D23A7004@core3.amsl.com>
In-Reply-To: <20100207064512.E97D23A7004@core3.amsl.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 9es5BeXB
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-07.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: Sun, 07 Feb 2010 07:24:06 -0000

We have uploaded a new version of the xlate document based on the
comments received after the previous upload. The diff is at
http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-v6v4-xlate-07.txt

The modifications are:

(1) Add a workflow example in appendix.
(2) Add some details for the illegal source address handling.
(3) Provide more freedom for the implementation.
(4) Typo corrections.

Thanks.

xing



Internet-Drafts@ietf.org дµÀ:
> 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           : IP/ICMP Translation Algorithm
> 	Author(s)       : X. Li, et al.
> 	Filename        : draft-ietf-behave-v6v4-xlate-07.txt
> 	Pages           : 31
> 	Date            : 2010-02-06
>
> This document specifies an update to the Stateless IP/ICMP
> Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
> translates between IPv4 and IPv6 packet headers (including ICMP
> headers) for both stateless and stateful modes.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-07.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.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From ajs@shinkuro.com  Sun Feb  7 02:11: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 68F703A6D06 for <behave@core3.amsl.com>; Sun,  7 Feb 2010 02:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 xmDoEZAwrZas for <behave@core3.amsl.com>; Sun,  7 Feb 2010 02:11:15 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 0040A3A6898 for <behave@ietf.org>; Sun,  7 Feb 2010 02:11:14 -0800 (PST)
Received: from crankycanuck.ca (unknown [213.144.149.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4DE5C1ECB4E8; Sun,  7 Feb 2010 10:12:11 +0000 (UTC)
Date: Sun, 7 Feb 2010 05:12:05 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: Dave Thaler <dthaler@microsoft.com>
Message-ID: <20100207101204.GA1174@shinkuro.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B29B9976F@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B29B9976F@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on draft-ietf-behave-dns64-05
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: Sun, 07 Feb 2010 10:11:17 -0000

On Tue, Jan 05, 2010 at 03:01:10AM +0000, Dave Thaler wrote:
> My comments and suggested wording changes on this document 
> are marked up in the PDF at 
> http://research.microsoft.com/~dthaler/draft-ietf-behave-dns64-05.pdf

A question about wording changes: in several places, you suggested
changing the English description of RCODE values from their names in
RFC 1035 to their usual representation from implementations.  For
instance, you suggest changing "RCODE=3 (Name Error)" to "RCODE=3
(NXDOMAIN)" and "RCODE=2 (Server failure)" to "RCODE=2 (SERVFAIL)".
Any special reason why?  If we're going to include NXDOMAIN, we have
another normative reference, because NXDOMAIN isn't defined at all in
RFC 1035 (neither is SERVFAIL, but it's at least an obvious abbrev).
That's why I prefer to stick with the definitions in 1035.  Ok?

A

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


From jouni.nospam@gmail.com  Sun Feb  7 05:33:26 2010
Return-Path: <jouni.nospam@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 845DF3A67F4 for <behave@core3.amsl.com>; Sun,  7 Feb 2010 05:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 YbWH+zLJOXPu for <behave@core3.amsl.com>; Sun,  7 Feb 2010 05:33:25 -0800 (PST)
Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by core3.amsl.com (Postfix) with ESMTP id 69C3D3A681D for <behave@ietf.org>; Sun,  7 Feb 2010 05:33:25 -0800 (PST)
Received: from a88-114-169-200.elisa-laajakaista.fi (a88-114-169-200.elisa-laajakaista.fi [88.114.169.200]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 17639139729; Sun,  7 Feb 2010 15:34:17 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=utf-8
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <4B6E53CE.3090805@cernet.edu.cn>
Date: Sun, 7 Feb 2010 15:34:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <84FE75B1-DA45-4B37-A777-F49E66414172@gmail.com>
References: <20100125101503.20B5F3A68A3@core3.amsl.com>	<4B5D7167.4050801@cernet.edu.cn> <E1C59E7D-207F-452A-BDBD-725BBCEEA02C@gmail.com> <4B6E53CE.3090805@cernet.edu.cn>
To: Xing Li <xing@cernet.edu.cn>
X-Mailer: Apple Mail (2.1077)
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Sun, 07 Feb 2010 13:33:26 -0000

Hi Xing,

Thanks! I still think the text in Section 3.1 of -07 needs a bit fixing. =
The ICMPv4 error message needs to be sent only when the next hop =
interface MTU is *less* that IPv4 packet size plus 20 bytes. Equal size =
is ok. So change "less than or equal to the total" -> "less than the =
total".

-Jouni

On Feb 7, 2010, at 7:46 AM, Xing Li wrote:

> jouni korhonen =E5=86=99=E9=81=93:
>=20
> You are correct. Thanks. We will make corrections in the next version.
>=20
> Regards,
>=20
> xing
>=20
>> Hi,
>>=20
>> On Jan 25, 2010, at 12:24 PM, Xing Li wrote:
>>=20
>> =20
>>> Hi, All,
>>>=20
>>> For draft-ietf-behave-v6v4-xlate-05 during WGLC, we have 4 reviews, =
many
>>> active discussions on the mailing list and mails to the authors. =
Thanks
>>> for the reviews and comments. Here is a summary of the main issues
>>> discussed during WGLC.
>>>=20
>>> (1) Discussion if translator is a router (for TTL/Hop-limit =
handling)
>>> Conclusion: Translator is a router. We made the wording consistent =
in
>>> different places of the document (in sections 1.4, 2.1, 2.7, 3.1 and
>>> 3.6. of the xlate-05)
>>>=20
>>>   =20
>>=20
>> In Section 3.1 it says:
>>=20
>>   ...
>>   If the DF bit is set and the MTU of the next-hop interface is less
>>   than or equal to the total length value of the IPv4 packet minus =
20,
>>   the translator MUST send an ICMPv4 "Fragmentation Needed" error
>>   message to the IPv4 source address.
>>   ...
>> =20
>> Am I just reading/understanding this wrong but shouldn't the text =
say?
>>=20
>>   ...
>>   If the DF bit is set and the MTU of the next-hop interface is less
>>   than to the total length value of the IPv4 packet plus 20,
>>   the translator MUST send an ICMPv4 "Fragmentation Needed" error
>>   message to the IPv4 source address.
>>   ...
>>=20
>> -Jouni
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>=20
>>=20
>> =20
>=20


From iljitsch@muada.com  Sun Feb  7 11:39:20 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 822A13A6EE8 for <behave@core3.amsl.com>; Sun,  7 Feb 2010 11:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 pETXvgCesxxm for <behave@core3.amsl.com>; Sun,  7 Feb 2010 11:39:19 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 932C63A692C for <behave@ietf.org>; Sun,  7 Feb 2010 11:39:19 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o17Jcv0O023078 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <behave@ietf.org>; Sun, 7 Feb 2010 20:39:02 +0100 (CET) (envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sun, 7 Feb 2010 20:40:06 +0100
References: <4B6F08CC.2070900@wand.net.nz>
To: "behave@ietf.org WG" <behave@ietf.org>
Message-Id: <063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com>
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
Subject: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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: Sun, 07 Feb 2010 19:39:20 -0000

Ben Stasiewics has done some testing to see if hosts actually respond =
with a fragment header after a < 1280 too big message, and the results =
are surprising.

Looks like we can't depend on hosts implementing this correctly.

Begin forwarded message:

> From: Ben Stasiewicz <ben@wand.net.nz>
> Date: 7 februari 2010 19:39:08 GMT+01:00
> To: mtu@psc.edu
> Cc: Matthew Luckie <mjl@wand.net.nz>
> Subject: Re: IPv6 hosts sending <1280 byte packets [was RE: RRG =
discussion of SEAL, IPTM - and my critique of RFC4821]

> On 29/01/10 08:40, Dan Wing wrote:
>> Ben, would it be possible to conduct a test to see how hosts react to =
PTB
>> smaller than 1280?

> I conducted such a test and found that 299 (43.46%) of the 688
> IPv6-capable web servers that I tested did include an IPv6 =
fragmentation
> header in their response packets after they were sent an ICMPv6 PTB
> message specifying an MTU < 1280 bytes. The other 389 (56.54%) did =
not.

> I am happy to answer any questions about the test.


From xing@cernet.edu.cn  Sun Feb  7 18:11:39 2010
Return-Path: <xing@cernet.edu.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 D462D3A6F91 for <behave@core3.amsl.com>; Sun,  7 Feb 2010 18:11:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.527
X-Spam-Level: 
X-Spam-Status: No, score=0.527 tagged_above=-999 required=5 tests=[AWL=0.430,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 r0MBM37Se6ON for <behave@core3.amsl.com>; Sun,  7 Feb 2010 18:11:38 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 4D4CC3A6916 for <behave@ietf.org>; Sun,  7 Feb 2010 18:11:36 -0800 (PST)
Received: from [192.168.1.101]([125.34.54.71]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b6fcf6a; Mon, 08 Feb 2010 10:12:22 +0800
Message-ID: <4B6F7302.2030503@cernet.edu.cn>
Date: Mon, 08 Feb 2010 10:12:18 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Jouni <jouni.nospam@gmail.com>
References: <20100125101503.20B5F3A68A3@core3.amsl.com>	<4B5D7167.4050801@cernet.edu.cn> <E1C59E7D-207F-452A-BDBD-725BBCEEA02C@gmail.com> <4B6E53CE.3090805@cernet.edu.cn> <84FE75B1-DA45-4B37-A777-F49E66414172@gmail.com>
In-Reply-To: <84FE75B1-DA45-4B37-A777-F49E66414172@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 43sGTeXB
Cc: behave@ietf.org, Behave Chairs <behave-chairs@tools.ietf.org>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-06.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: Mon, 08 Feb 2010 02:11:40 -0000

Jouni 写道:
> Hi Xing,
>
> Thanks! I still think the text in Section 3.1 of -07 needs a bit fixing. The ICMPv4 error message needs to be sent only when the next hop interface MTU is *less* that IPv4 packet size plus 20 bytes. Equal size is ok. So change "less than or equal to the total" -> "less than the total".
>   

thanks. although this is marginal, we will update to "less than" in the 
next upload. xing
> -Jouni
>
> On Feb 7, 2010, at 7:46 AM, Xing Li wrote:
>
>   
>> jouni korhonen 写道:
>>
>> You are correct. Thanks. We will make corrections in the next version.
>>
>> Regards,
>>
>> xing
>>
>>     
>>> Hi,
>>>
>>> On Jan 25, 2010, at 12:24 PM, Xing Li wrote:
>>>
>>>  
>>>       
>>>> Hi, All,
>>>>
>>>> For draft-ietf-behave-v6v4-xlate-05 during WGLC, we have 4 reviews, many
>>>> active discussions on the mailing list and mails to the authors. Thanks
>>>> for the reviews and comments. Here is a summary of the main issues
>>>> discussed during WGLC.
>>>>
>>>> (1) Discussion if translator is a router (for TTL/Hop-limit handling)
>>>> Conclusion: Translator is a router. We made the wording consistent in
>>>> different places of the document (in sections 1.4, 2.1, 2.7, 3.1 and
>>>> 3.6. of the xlate-05)
>>>>
>>>>    
>>>>         
>>> In Section 3.1 it says:
>>>
>>>   ...
>>>   If the DF bit is set and the MTU of the next-hop interface is less
>>>   than or equal to the total length value of the IPv4 packet minus 20,
>>>   the translator MUST send an ICMPv4 "Fragmentation Needed" error
>>>   message to the IPv4 source address.
>>>   ...
>>>  
>>> Am I just reading/understanding this wrong but shouldn't the text say?
>>>
>>>   ...
>>>   If the DF bit is set and the MTU of the next-hop interface is less
>>>   than to the total length value of the IPv4 packet plus 20,
>>>   the translator MUST send an ICMPv4 "Fragmentation Needed" error
>>>   message to the IPv4 source address.
>>>   ...
>>>
>>> -Jouni
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>>>
>>>  
>>>       
>
>
>   


From root@core3.amsl.com  Sun Feb  7 20:45:02 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 2A1D53A716E; Sun,  7 Feb 2010 20:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100208044502.2A1D53A716E@core3.amsl.com>
Date: Sun,  7 Feb 2010 20:45:02 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-08.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: Mon, 08 Feb 2010 04:45:02 -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           : IP/ICMP Translation Algorithm
	Author(s)       : X. Li, et al.
	Filename        : draft-ietf-behave-v6v4-xlate-08.txt
	Pages           : 32
	Date            : 2010-02-07

This document specifies an update to the Stateless IP/ICMP
Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
translates between IPv4 and IPv6 packet headers (including ICMP
headers) for both stateless and stateful modes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-08.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-v6v4-xlate-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From dwing@cisco.com  Mon Feb  8 08:20: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 0A4C43A7448 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 08:20:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 8ZFWXSp3ARQR for <behave@core3.amsl.com>; Mon,  8 Feb 2010 08:20:03 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 79EB13A742C for <behave@ietf.org>; Mon,  8 Feb 2010 08:20:03 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsgFALrIb0urRN+K/2dsb2JhbACHeoESt1CXCYRUBA
X-IronPort-AV: E=Sophos;i="4.49,431,1262563200"; d="scan'208";a="147553600"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 08 Feb 2010 16:21:06 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o18GL6pi011025; Mon, 8 Feb 2010 16:21:06 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>, <behave@ietf.org>
References: <4B6F08CC.2070900@wand.net.nz> <063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com>
Date: Mon, 8 Feb 2010 08:21:06 -0800
Message-ID: <00f201caa8da$b78e3e90$c4f0200a@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
In-Reply-To: <063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com>
Thread-Index: AcqoLXaVuCJlYDjOSS+ytT5o3LcRLwAqlLFA
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 16:20:07 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Iljitsch van Beijnum
> Sent: Sunday, February 07, 2010 11:40 AM
> To: behave@ietf.org WG
> Subject: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> Ben Stasiewics has done some testing to see if hosts actually 
> respond with a fragment header after a < 1280 too big 
> message, and the results are surprising.
> 
> Looks like we can't depend on hosts implementing this correctly.

To be clear, Ben Stasiewicz's test does not determine if the problem is hosts
failing to implement the last paragraph of Section 5 of RFC2460 correctly, or
if host-/network-based firewalls are blocking ICMPv6 packet-too-big messages
or blocking IPv6 packets with the fragment header.

I recently received email from TAHI (http://www.tahi.org), which does IPv6
conformance testing.  Their test is listed at
http://www.ipv6ready.org/docs/Core_Conformance_Latest.pdf and its test
v6LC.4.1.6 ("Receiving MTU Below IPv6 Minimum Link MTU") which appears to have
been tested since 2005.  So any recipient of the IPv6 Ready certification will
implement things correctly.  And there may well be sysctl settings to tweak
this specific behavior.


But no matter the reason, I agree that a greater than 50% failure on the
Internet means the function is effectively broken.  In my view, Ben's testing
invalidates the consensus reached in the meeting at IETF76 (Hiroshima), and I
have asked authors of xlate and xlate-stateful to revise the documents
accordingly.

If anyone thinks we should keep the IETF76 consensus, please speak up now!

-d


> Begin forwarded message:
> 
> > From: Ben Stasiewicz <ben@wand.net.nz>
> > Date: 7 februari 2010 19:39:08 GMT+01:00
> > To: mtu@psc.edu
> > Cc: Matthew Luckie <mjl@wand.net.nz>
> > Subject: Re: IPv6 hosts sending <1280 byte packets [was RE: 
> RRG discussion of SEAL, IPTM - and my critique of RFC4821]
> 
> > On 29/01/10 08:40, Dan Wing wrote:
> >> Ben, would it be possible to conduct a test to see how 
> hosts react to PTB
> >> smaller than 1280?
> 
> > I conducted such a test and found that 299 (43.46%) of the 688
> > IPv6-capable web servers that I tested did include an IPv6 
> fragmentation
> > header in their response packets after they were sent an ICMPv6 PTB
> > message specifying an MTU < 1280 bytes. The other 389 
> (56.54%) did not.
> 
> > I am happy to answer any questions about the test.
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From ddolson@sandvine.com  Mon Feb  8 07:12:36 2010
Return-Path: <ddolson@sandvine.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 71C1D28C121; Mon,  8 Feb 2010 07:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 bOWdDM-hRlmh; Mon,  8 Feb 2010 07:12:34 -0800 (PST)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by core3.amsl.com (Postfix) with ESMTP id 0130628C124; Mon,  8 Feb 2010 07:12:33 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Feb 2010 10:13:34 -0500
Message-ID: <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
Thread-Index: Acqk9e5k2HVZbYNmRqmDmJiAEKHTMABrvomwAIlmcyA=
References: <4B69B06D.7080606@sri.com> <E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com>
From: "Dave Dolson" <ddolson@sandvine.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Ed Jankiewicz" <edward.jankiewicz@sri.com>, "Behave WG" <behave@ietf.org>, <softwires@ietf.org>
X-Mailman-Approved-At: Mon, 08 Feb 2010 08:39:01 -0800
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 08 Feb 2010 15:12:36 -0000

Fred,

Quoted from below (by Ed Jankiewicz):
> > (4) Provide the capability in the IPSec gateway to discover the MTU
> on its WAN interface, subtract
> > the maximum header size that this gateway will add to packets
> presented on its LAN interface, which
> > the host can then discover through the PMTUD.
> >
> > Method (4) would be the best solution, but is not currently
available
> in the IPSec gateway products.

I believe this is referring to mapping of ICMP "too big" messages. When
a tunnel end-point receives a "too big" message, it would have to map
the message to an ICMP message for the original host. I believe this
could be done in a stateless manner using the packet quoted in the
message. (RFC2463 says the "too big" message will include "As much of
invoking packet as will fit without the ICMPv6 packet exceeding the
minimum IPv6 MTU")

In my opinion, this suggestion is indeed the best solution, and should
have MAY or perhaps RECOMMENDED status despite lack of current
availability.

The network will operate most efficiently without fragmentation. When
1500-byte packets are *always* fragmented, there are twice as many of
these packets, and the probability of packet loss is doubled, especially
problematic when the tunnel passes over a network that can experience
congestion. (Only one fragment has to be lost for the entire packet to
be lost.) This will impact the throughput of bulk traffic the most. This
is why TCP went to "don't fragment" mode many years ago.

Therefore I respectfully disagree with your assertion that "whenever it
is practically possible, tunnel routers should use tunnel
fragmentation."

I suggest that tunnel gateways SHOULD send the ICMP "too big", but MAY
instead fragment. A vendor could provide fragmentation or ICMP
configuration options, either of which could be useful depending on the
reliability of the network that carries the tunnel. (Of course the
network carrying the tunnel could simply have a larger MTU.) The
receiving end of the tunnel would have to support reassembly of tunnel
fragments for multi-vendor interop.


As for ICMP black-holes, is this likely to be standard practice with
ICMP6 as well (vs. being done to protect old IPv4 routers from attacks
on their expensive control-path processing) ?


David Dolson
Software Architect, Sandvine Incorporated.
http://www.sandvine.com



> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org]
On
> Behalf Of Templin, Fred L
> Sent: Friday, February 05, 2010 5:17 PM
> To: Ed Jankiewicz; Behave WG; softwires@ietf.org
> Subject: Re: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
>=20
> Hi Ed,
>=20
> > -----Original Message-----
> > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Ed Jankiewicz
> > Sent: Wednesday, February 03, 2010 9:21 AM
> > To: Behave WG; softwires@ietf.org
> > Subject: [BEHAVE] PMTU Discovery and ICMPv6 filtering
> >
> > One of my colleagues received a long comment on Path MTU Discovery
> recommendations his organization
> > published and is seeking advice.  I recall this has been discussed
> several times at IETF meetings,
> > not sure which WG, so this may be redundant.  I've tried to
summarize
> the salient points below, and
> > have two broad questions on this:  Are these points already covered
> in RFCs (other than 4459, 4890)
> > or current Internet-Drafts? If so, I would appreciate pointers.  If
> not already covered by current
> > publications, is there interest in documenting the problem and
> comparing the solutions/drawbacks?
> >
> > The commenter basically wrote:
> >
> > IPv4 and IPv6 treat packets exceeding MTU differently - IPv4 will
> fragment packets that are "too big"
> > but IPv6 will drop the packet and respond with ICMPv6 "too-big"
error
> message. [The subject
> > publication] recommends using the Path MTU Discovery Protocol to
> discover the end-to-end PMTU, which
> > relies on ICMPv6 error messages. These may be blocked by various
> "filters" and IPsec gateways, which
> > is the case in many operational networks.
> >
> > However, even when ICMPv6 is not blocked, IPsec gateways (in tunnel
> mode) add extra headers, and
> > there can be more than one tunnel header involved (routers also
> create tunnels). When a "too-big"
> > message is sent the router will return put in its ICMPv6 message the
> value of the MTU on the next
> > link at layer 2. The host receiving this MTU value in an ICMP
message
> at part of the Path MTU
> > Discovery Protocol has no way of knowing how many extra tunnel
> headers are added along the path, and
> > so if it just takes the reported MTU value without allowing for
these
> extra headers the process will
> > keep on failing and will not recover. We have seen this behavior in
> our experiments.
> >
> > This can be prevented by ensuring that the maximum packet size sent
> by the host is smaller than the
> > layer 2 limit: smaller by an amount estimated to be sufficient to
> allow room for extra headers to be
> > added along the path. Several ways of achieving this are possible:
> >
> > (1) Set this reduced MTU value on the on the IPSec gateway LAN
> interface; the host then discovers
> > this MTU through the PMTUD.
> >
> > (2) Statically configure this reduced MTU value into the host and
> switch off PMTUD.
> >
> > (3) Set a reduced MTU at the IPSec gateway WAN interface; The IPSec
> gateway acts as a host on this
> > interface and so can do packet fragmentation.
> >
> > (4) Provide the capability in the IPSec gateway to discover the MTU
> on its WAN interface, subtract
> > the maximum header size that this gateway will add to packets
> presented on its LAN interface, which
> > the host can then discover through the PMTUD.
> >
> > Method (4) would be the best solution, but is not currently
available
> in the IPSec gateway products.
> > The next best solution is (1), which has been used [in commenter
> experiments]. This is not as good as
> > (4) because it requires manual intervention, and an understanding of
> how to calculate the appropriate
> > (reduced) MTU value.
> > The next best solution is (2), the only disadvantage of this
approach
> is that only one value can be
> > set for all paths and so the worst case (lowest) value has to be
> used. In a complex network it may
> > not always be obvious what the worst case path is, and so a
> conservative estimate may be necessary.
> > Even so this could be preferable in some deployment scenarios since
> the path-MTU discovery protocol
> > relies on the passage of ICMP messages which are sometimes blocked
by
> firewalls and other security
> > devices.
> > Approach (3) is the worst solution since it will cause many IP
> packets to be fragmented which is
> > inefficient (both because, unlike IPv4, the IPv6 header has to be
> extended to include the
> > fragmentation offset field, and because it will result the second
> fragment being very small, i.e. the
> > ratio of user-data to IP header size will be poor).
> >
> > It is likely that for immediate use option (1) should be used
> although (4) would be better if it were
> > supported in the relevant products.
>=20
> (1) seems like a safe option at face value, but can lead
> to undesirable inefficiencies. Consider for example the
> diagram below:
>=20
>             L1    L2               L3
>             |     |                |
>         W --|--R--|--GW1<=3D=3D=3D=3D>GW2--|--Z
>             |     |   (Internet)   |
>                X--|     L4, L5,
>                Y--|     L6, etc.
>=20
> Here, we have a tunnel beteen 'GW1' and 'GW2' over the
> Internet to connect two networks. 'GW1' sets a reduced
> MTU 'M' on its LAN interface connected to link 'L2', and
> also advertises 'M' in the Router Advertisements it sends
> on 'L2'. Hosts 'X' and 'Y' pick up the reduced MTU from
> the RA and limit the size of the packets they send to at
> most 'M' bytes. But, host 'W' connected to link 'L1' does
> not see the MTU reduction, and hence will routinely send
> packets larger than 'M' to any hosts beyond router 'R'
> such as 'X', 'Y' and 'Z'. These packets will be dropped
> with an ICMPv6 PTB returned, then 'W' will be forced to
> reduce its packet size and retransmit. The only way to
> prevent this is to drive the reduced MTU 'M' deeply into
> the entire network stacked up behind 'GW1', which may
> contain arbitrarily many additional routers and links.
>=20
> Now, even if the reduced MTU 'M' were propagated deeply
> throughout the 'GW1' network, if most communications
> remain localized hosts would only be able to use a packet
> size of at most 'M' even if their links natively support
> a much larger MTU. Consider for example that link 'L2'
> in the diagram has a native MTU of 9kb, but the effective
> MTU across the 'GW1'<=3D=3D=3D=3D>'GW2' tunnel is only 1400. 'GW1'
> will advertise 1400 on link 'L1', and communications
> betweenhosts 'X' and 'Y' will be restricted to using at
> most 1400 byte packets when they could have used 9kb.
>=20
> There are a couple of factors to consider in terms of
> what might be a better solution. First, what are the
> expected data rates over the 'GW1'<=3D=3D=3D=3D>'GW2' tunnel,
> and second what are the performance characteristics of
> those gateways? If the data rates are such that GW1 and
> GW2 are already operating at their peak performance even
> without taking on any additional processing overhead,
> then the best solution would be to make sure that all
> links over which the tunnel might travel (e.g., 'L4',
> 'L5', 'L6', etc.) are large enough to "hide" the tunnel
> encapsulation artifact. For example, if all links 'L4'
> 'L5', 'L6', etc. configure a native MTU of no smaller
> than 1600 and the encapsulation overhead for the tunnel
> is 100 bytes, then all routers and hosts on the LAN side
> of 'GW1' would be able to happily use a 1500 MTU. If the
> MTUs of 'L4', etc. cannot be controlled, however, then
> there is no recourse but to use option (1) and cope with
> the inefficiencies.
>=20
> On the other hand, if the data rates across the tunnel
> are nominal and/or 'GW1' and 'GW2' have more than
> sufficient processing capability to take on a modest
> amount of additional overhead, the GWs can use tunnel
> fragmentation so that 'GW1' can present a solid MTU on
> its LAN side interface that does not reflect the size
> of the tunnel encapsulation headers. If the tunnel
> fragmentation could accommodate an MTU of at least 1500
> in this way, then 'GW1' would be able to observe the
> "de facto Internet cell size" of 1500. If we further
> assume that the vast majority of hosts in the world
> today either limit their packet sizes to no more than
> 1500 bytes or are willing to assume the risk of silent
> loss of packets larger than 1500 due to MTU restrictions,
> then there is no need to place artificial restrictions
> on the size of packets that can be used within the 'GW1'
> network. This latter class of hosts (those that send
> packets larger than 1500) would be best served to use
> their own host-based MTU probing mechanisms for sending
> packets larger than 1500 in case the network is somehow
> silently dropping PMTUD messages. RFC4821 was specifically
> designed for this purpose.
>=20
> End result - whenever it is practically possible, tunnel
> routers should use tunnel fragmentation and hosts should
> use RFC4821.
>=20
> Fred
> fred.l.templin@boeing.com
>=20
> > --
> > Ed Jankiewicz - SRI International
> > Fort Monmouth Branch Office - IPv6 Research
> > Supporting DISA Standards Engineering Branch
> > 732-389-1003 or  ed.jankiewicz@sri.com
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From marcelo@it.uc3m.es  Mon Feb  8 08:51:36 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 309C43A7230 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 08:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.459
X-Spam-Level: 
X-Spam-Status: No, score=-106.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, 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 9TW7lqX0XUa4 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 08:51:34 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 72A183A67F6 for <behave@ietf.org>; Mon,  8 Feb 2010 08:51:34 -0800 (PST)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id 2DA197F23D5 for <behave@ietf.org>; Mon,  8 Feb 2010 17:52:35 +0100 (CET)
Message-ID: <4B704153.2020007@it.uc3m.es>
Date: Mon, 08 Feb 2010 17:52:35 +0100
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.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com> <00f201caa8da$b78e3e90$c4f0200a@cisco.com>
In-Reply-To: <00f201caa8da$b78e3e90$c4f0200a@cisco.com>
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-17162.002
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 16:51:36 -0000

El 08/02/10 17:21, Dan Wing escribió:
>
> But no matter the reason, I agree that a greater than 50% failure on the
> Internet means the function is effectively broken.  In my view, Ben's testing
> invalidates the consensus reached in the meeting at IETF76 (Hiroshima),and I
>    
> have asked authors of xlate and xlate-stateful to revise the documents
> accordingly.
>
>    

I am not sure what the translator should do now... what do you have in mind?

Regards, marcelo

> If anyone thinks we should keep the IETF76 consensus, please speak up now!
>
> -d
>
>
>    
>> Begin forwarded message:
>>
>>      
>>> From: Ben Stasiewicz<ben@wand.net.nz>
>>> Date: 7 februari 2010 19:39:08 GMT+01:00
>>> To: mtu@psc.edu
>>> Cc: Matthew Luckie<mjl@wand.net.nz>
>>> Subject: Re: IPv6 hosts sending<1280 byte packets [was RE:
>>>        
>> RRG discussion of SEAL, IPTM - and my critique of RFC4821]
>>
>>      
>>> On 29/01/10 08:40, Dan Wing wrote:
>>>        
>>>> Ben, would it be possible to conduct a test to see how
>>>>          
>> hosts react to PTB
>>      
>>>> smaller than 1280?
>>>>          
>>      
>>> I conducted such a test and found that 299 (43.46%) of the 688
>>> IPv6-capable web servers that I tested did include an IPv6
>>>        
>> fragmentation
>>      
>>> header in their response packets after they were sent an ICMPv6 PTB
>>> message specifying an MTU<  1280 bytes. The other 389
>>>        
>> (56.54%) did not.
>>
>>      
>>> I am happy to answer any questions about the test.
>>>        
>> _______________________________________________
>> 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 dwing@cisco.com  Mon Feb  8 09:45:13 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 1A1CA3A7462 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 09:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 R1tocuKkfkEg for <behave@core3.amsl.com>; Mon,  8 Feb 2010 09:45:12 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id D124628C0DE for <behave@ietf.org>; Mon,  8 Feb 2010 09:45:11 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsgFAKfcb0urRN+K/2dsb2JhbACHeoESuBaXJIRUBA
X-IronPort-AV: E=Sophos;i="4.49,431,1262563200"; d="scan'208";a="84706839"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by rtp-iport-2.cisco.com with ESMTP; 08 Feb 2010 17:46:14 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o18HkDf2021241; Mon, 8 Feb 2010 17:46:13 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'marcelo bagnulo braun'" <marcelo@it.uc3m.es>, <behave@ietf.org>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com> <4B704153.2020007@it.uc3m.es>
Date: Mon, 8 Feb 2010 09:46:13 -0800
Message-ID: <015801caa8e6$9b72fff0$c4f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <4B704153.2020007@it.uc3m.es>
Thread-Index: Acqo3yJLiK4ckIlgSsaKCbr7ug1DHAAAyP2Q
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 17:45:13 -0000

=20

> -----Original Message-----
> From: behave-bounces@ietf.org=20
> [mailto:behave-bounces@ietf.org] On Behalf Of marcelo bagnulo braun
> Sent: Monday, February 08, 2010 8:53 AM
> To: behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
> El 08/02/10 17:21, Dan Wing escribi=F3:
> >
> > But no matter the reason, I agree that a greater than 50%=20
> > failure on the
> > Internet means the function is effectively broken.  In my=20
> > view, Ben's testing
> > invalidates the consensus reached in the meeting at IETF76=20
> > (Hiroshima),and I
> >   =20
> > have asked authors of xlate and xlate-stateful to revise=20
> > the documents accordingly.
> >
> >   =20
>=20
> I am not sure what the translator should do now... what do=20
> you have in mind?

We can't rely on sending ICMPv6 packet-too-big to IPv6 hosts
if the packet-too-big indicates an MTU less than 1280.  Thus,
the text from RFC2765 (SIIT),

   However, [IPv6]
   requires that IPv6 nodes handle such an ICMP "packet too big" message
   by reducing the path MTU to 1280 and including an IPv6 fragment
   header with each packet.  This allows end-to-end path MTU discovery
   across the translator as long as the path MTU is 1280 bytes or
   greater.  When the path MTU drops below the 1280 limit the IPv6
   sender will originate 1280 byte packets that will be fragmented by
   IPv4 routers along the path after being translated to IPv4.

is true, but testing results on the Internet show it fails more than
50% of the time.  Thus, we can't rely on it.  =
draft-ietf-behave-v6v4-xlate-08=20
has incorporated that same text from RFC2765 and the current design=20
relies on that function. =20

For stateless translation, we need to simply translate small packets
(which was smaller than 1280 on the IPv6 side) with IPv4 DF=3D0, and =
allow
it to be fragmented on the IPv4 side.  This is because if the translator
does receive an IPv4 ICMP packet-too-big describing an MTU smaller than=20
1280, and translated it to IPv6, more than 50% of the IPv6 hosts would=20
be unable to successfully process it.  This means we lose end-to-end=20
PMTUD across the translator for links smaller than 1280.  However, we=20
still have end-to-end PMTUD for links greater than 1280, so translators
will allow moving to larger packets in the future.


For stateful translation, it is _possible_ for the translator
to include MTU in its IPv4 and IPv6 tables, and do provide end-to-end
PMTUD even for links below 1280.  To do this, a stateful translator
would maintain the MTU for all IPv4 hosts that currently have a mapping,
and go ahead and translate with DF=3D1.  Then, if an IPv4 ICMP PTB is
received and describes an MTU smaller than 1280, go ahead and translate
that to ICMPv6 (in the hopes of hitting the ~45% of hosts that will
successfully process it), but also modify the MTU in the mapping table
so that subsequent packets are always fragmented by the stateful
translator.  This allows the IPv6 host to realize it isn't getting
end-to-end PMTUD (because it was sent the ICMPv6 PTB message,=20
indicating a smaller-than-1280 MTU), and also allows the stateful
translator to set DF=3D0 only for those IPv4 destinations that need
it.  But, this all seems complicated for stateful translation; I=20
don't know if we need to get into such an optimization, especially at
this late date with our specifications.

Thoughts?

-d


> Regards, marcelo
>=20
> > If anyone thinks we should keep the IETF76 consensus,=20
> please speak up now!
> >
> > -d
> >
> >
> >   =20
> >> Begin forwarded message:
> >>
> >>     =20
> >>> From: Ben Stasiewicz<ben@wand.net.nz>
> >>> Date: 7 februari 2010 19:39:08 GMT+01:00
> >>> To: mtu@psc.edu
> >>> Cc: Matthew Luckie<mjl@wand.net.nz>
> >>> Subject: Re: IPv6 hosts sending<1280 byte packets [was RE:
> >>>       =20
> >> RRG discussion of SEAL, IPTM - and my critique of RFC4821]
> >>
> >>     =20
> >>> On 29/01/10 08:40, Dan Wing wrote:
> >>>       =20
> >>>> Ben, would it be possible to conduct a test to see how
> >>>>         =20
> >> hosts react to PTB
> >>     =20
> >>>> smaller than 1280?
> >>>>         =20
> >>     =20
> >>> I conducted such a test and found that 299 (43.46%) of the 688
> >>> IPv6-capable web servers that I tested did include an IPv6
> >>>       =20
> >> fragmentation
> >>     =20
> >>> header in their response packets after they were sent an=20
> ICMPv6 PTB
> >>> message specifying an MTU<  1280 bytes. The other 389
> >>>       =20
> >> (56.54%) did not.
> >>
> >>     =20
> >>> I am happy to answer any questions about the test.
> >>>       =20
> >> _______________________________________________
> >> Behave mailing list
> >> Behave@ietf.org
> >> https://www.ietf.org/mailman/listinfo/behave
> >>     =20
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> >   =20
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From remi.despres@free.fr  Mon Feb  8 09:48:11 2010
Return-Path: <remi.despres@free.fr>
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 6280D3A7475; Mon,  8 Feb 2010 09:48:11 -0800 (PST)
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.075,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 ilhFmqkdoi2f; Mon,  8 Feb 2010 09:48:10 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id C52423A7461; Mon,  8 Feb 2010 09:48:08 -0800 (PST)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 7D4B7E08092; Mon,  8 Feb 2010 18:49:04 +0100 (CET)
Received: from [192.168.0.13] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 84A5BE081A8; Mon,  8 Feb 2010 18:49:01 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com>
Date: Mon, 8 Feb 2010 18:49:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE97335B-485E-424B-A99B-D1DB8EDE45F1@free.fr>
References: <4B69B06D.7080606@sri.com> <E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com> <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com>
To: Dave Dolson <ddolson@sandvine.com>
X-Mailer: Apple Mail (2.1077)
Cc: softwires@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>, Behave WG <behave@ietf.org>, Ed Jankiewicz <edward.jankiewicz@sri.com>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 08 Feb 2010 17:48:11 -0000

Le 8 f=E9vr. 2010 =E0 16:13, Dave Dolson a =E9crit :

> As for ICMP black-holes, is this likely to be standard practice with
> ICMP6 as well (vs. being done to protect old IPv4 routers from attacks
> on their expensive control-path processing) ?

Does anyone know a reference where a good reason would be documented to =
Discard ICMP error messages, even when they contain valid addresses?
(In the absence of such good reason, forwarding them should IMHO be =
MUST.)

RD



From iljitsch@muada.com  Mon Feb  8 12:26:14 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 8F3CC28C176 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 12:26:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 bwwgv0-3TUbT for <behave@core3.amsl.com>; Mon,  8 Feb 2010 12:26:13 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 8DE6328C181 for <behave@ietf.org>; Mon,  8 Feb 2010 12:26:13 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o18KPoIi032656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 8 Feb 2010 21:25:52 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <015801caa8e6$9b72fff0$c4f0200a@cisco.com>
Date: Mon, 8 Feb 2010 21:27:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com> <4B704153.2020007@it.uc3m.es> <015801caa8e6$9b72fff0$c4f0200a@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 20:26:14 -0000

On 8 feb 2010, at 18:46, Dan Wing wrote:

> For stateful translation, it is _possible_ for the translator
> to include MTU in its IPv4 and IPv6 tables, and do provide end-to-end
> PMTUD even for links below 1280.  To do this, a stateful translator
> would maintain the MTU for all IPv4 hosts that currently have a =
mapping,
> and go ahead and translate with DF=3D1.

So in this case the translator receives IPv6 packets with or without a =
fragment header that are 1280 bytes but the IPv4 destination has a path =
MTU of (say) 576 bytes. This means the translator has to fragment.

So essentially this means doing more work (keeping PMTUD state for the =
IPv4 path) in order to do even more work later (fragment). Not sure how =
that makes sense... If you simply set DF=3D0 for packets < 1280 bytes =
then the people who thought it was a good idea to set an unreasonably =
small MTU are the ones who get to fragment, which to me seems how it =
should be.

(Although in practice few fragments will happen because in IPv4 PMTUD is =
only supported for TCP and TCP has the MSS option.)

> Then, if an IPv4 ICMP PTB is
> received and describes an MTU smaller than 1280, go ahead and =
translate
> that to ICMPv6 (in the hopes of hitting the ~45% of hosts that will
> successfully process it),

You can always do that, yes.


From marc.blanchet@viagenie.ca  Mon Feb  8 12:57:49 2010
Return-Path: <marc.blanchet@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 AB02D3A73A6 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 12:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 fBbK6jfLKP-8 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 12:57:48 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id AED693A7288 for <behave@ietf.org>; Mon,  8 Feb 2010 12:57:48 -0800 (PST)
Received: from mb-en1.lan (modemcable144.164-201-24.mc.videotron.ca [24.201.164.144]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2C48421B89; Mon,  8 Feb 2010 15:58:51 -0500 (EST)
Message-ID: <4B707B0A.5030208@viagenie.ca>
Date: Mon, 08 Feb 2010 15:58:50 -0500
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: behave@ietf.org, v6ops@ietf.org, ipv6-wg <ipv6-wg@ripe.net>,  intarea@ietf.org, dnsext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [BEHAVE] announcing DNS64-NAT64 opensource implementations
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, 08 Feb 2010 20:57:49 -0000

<sorry for cross-posting/>

This is to announce the availability of two NAT64-DNS64 open-source
implementations by Viagenie, as follows:

======
NAT64
======
BSD PF:
  this implementation of NAT64 is made by modifying the PF packet filter
available on BSD systems. A new 'nat64' statement is created in the
pf.conf file to enable the nat64 functionality.

Linux Netfilter:
The implementation of NAT64 for linux is available as a kernel module. 
It uses Netfilter's facilities for packet interception.  The
configuration is done with parameters provided at module insertion.

======
DNS64
======
As announced in july 2009 during IETF Stockholm, the companion DNS64
functionality is also available in two implementations, as follows:

BIND:
  this implementation of DNS64 is made by modifying the BIND DNS server.
A new "dns64-prefix" statement in options is created in the named.conf
file to enable DNS64 functionality.

Unbound:
  this implementation of DNS64 is made by adding a module to the Unbound
DNS server. To enable the DNS64 functionality, the module should be
declared and the dns64-prefix statement should be added in the
unbound.conf file.

The two functionalities (NAT64 and DNS64) make a complete system for
translating IPv6-IPv4 packets. The source code, some pre-compiled
packages and project description are available at:
http://ecdysis.viagenie.ca.

This project was funded by NLNet foundation
and Viagenie.

We are looking for feedback, patches, suggestions from the community.

http://ecdysis.viagenie.ca

Regards,

Marc Blanchet, Simon Perreault, Jean-Philippe Dionne
Viagenie




From Fred.L.Templin@boeing.com  Mon Feb  8 13:07:07 2010
Return-Path: <Fred.L.Templin@boeing.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 BDCCE28C182; Mon,  8 Feb 2010 13:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.615
X-Spam-Level: 
X-Spam-Status: No, score=-6.615 tagged_above=-999 required=5 tests=[AWL=-0.016, 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 rc7to8doujup; Mon,  8 Feb 2010 13:07:05 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id A2DE83A70AF; Mon,  8 Feb 2010 13:07:05 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o18L83CD007645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Feb 2010 13:08:04 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o18L83fo008696; Mon, 8 Feb 2010 13:08:03 -0800 (PST)
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o18L82Jh008675 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 8 Feb 2010 13:08:03 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-04.nw.nos.boeing.com ([130.247.64.250]) with mapi; Mon, 8 Feb 2010 13:08:03 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Dave Dolson <ddolson@sandvine.com>, Ed Jankiewicz <edward.jankiewicz@sri.com>, Behave WG <behave@ietf.org>, "softwires@ietf.org" <softwires@ietf.org>
Date: Mon, 8 Feb 2010 13:08:01 -0800
Thread-Topic: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
Thread-Index: Acqk9e5k2HVZbYNmRqmDmJiAEKHTMABrvomwAIlmcyAADPtXgA==
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com> <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com>
In-Reply-To: <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 08 Feb 2010 21:07:08 -0000

Hi Dave,

> -----Original Message-----
> From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On B=
ehalf Of Dave Dolson
> Sent: Monday, February 08, 2010 7:14 AM
> To: Templin, Fred L; Ed Jankiewicz; Behave WG; softwires@ietf.org
> Subject: Re: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
>
> Fred,
>
> Quoted from below (by Ed Jankiewicz):
> > > (4) Provide the capability in the IPSec gateway to discover the MTU
> > on its WAN interface, subtract
> > > the maximum header size that this gateway will add to packets
> > presented on its LAN interface, which
> > > the host can then discover through the PMTUD.
> > >
> > > Method (4) would be the best solution, but is not currently
> available
> > in the IPSec gateway products.
>
> I believe this is referring to mapping of ICMP "too big" messages. When
> a tunnel end-point receives a "too big" message, it would have to map
> the message to an ICMP message for the original host. I believe this
> could be done in a stateless manner using the packet quoted in the
> message. (RFC2463 says the "too big" message will include "As much of
> invoking packet as will fit without the ICMPv6 packet exceeding the
> minimum IPv6 MTU")

But, if the packet-in-error encapsulated in the ICMP
PTB message is encrypted and not complete (i.e., only
the leading 1200 or so bytes of the encrypted packet
are included), how will the tunnel ingress know how to
decrypt it in order to do the stateless translation?

Also, there seems to be some evidence that ICMPv6 PTB
messages are being dropped in the network. And, there is
ample evidence that ICMPv4 PTB messages are frequently
dropped in the network.

> In my opinion, this suggestion is indeed the best solution, and should
> have MAY or perhaps RECOMMENDED status despite lack of current
> availability.
>
> The network will operate most efficiently without fragmentation. When
> 1500-byte packets are *always* fragmented, there are twice as many of
> these packets, and the probability of packet loss is doubled, especially
> problematic when the tunnel passes over a network that can experience
> congestion. (Only one fragment has to be lost for the entire packet to
> be lost.) This will impact the throughput of bulk traffic the most. This
> is why TCP went to "don't fragment" mode many years ago.

The optimum solution comes when through good fortune
the network happens to have link sizes that are large
enough to hide the tunnel overhead artifact. Some have
suggested that almost all links in the Internet core
configure an MTU of ~4KB or greater. That seems like
a fairly bold statement to me, but I have no way of
confirming or refuting it. In that case, it is a
safe bet that packet of up to 1500 bytes will get
through without the need for fragmentation even after
the tunneling overhead is required.

> Therefore I respectfully disagree with your assertion that "whenever it
> is practically possible, tunnel routers should use tunnel
> fragmentation."

OK, I can see how my statement may have been alarming
without sufficient supporting background (which I
failed to provide). First I am not recommending
steady-state segmentation and reassembly; it is
greatly preferable that segmentation and reassembly
be avoided when it is not absolutely necessary. But,
the key is to be able to sense *when* segmentation
and reassembly is necessary, and then only use it
for those cases. That is what SEAL does - it uses
data packets as implicit probes to tell when the
path MTU is too small to pass original packets of
up to 1500 bytes (i.e., before the tunnel headers
are added). If the path MTU is large enough, SEAL
will pass the original packets in one piece w/o
further fragmentation. If the path MTU is too
small, SEAL uses segmentation to produce a "packet
pair" that gets pasted back together at the tunnel
far end. (SEAL will support longer trains of
segments as well, but that would be a deeper
discussion.)

> I suggest that tunnel gateways SHOULD send the ICMP "too big", but MAY
> instead fragment.

I would amend this to say that for DF=3D1 packets the tunnel
ingress MUST send an ICMP PTB when the packet is larger
than a fixed minimum tunnel MTU and also too large to
traverse the tunnel in a single piece. For packets that
are no larger than the fixed minimum tunnel MTU, the
tunnel ingress SHOULD use tunnel fragmentation (i.e.,
SEAL segmentation and reassembly). Presumably, the tunnel
ingress would choose a fixed minimum tunnel MTU that is
large enough so that source hosts will not see excessive
data loss and retransmissions due to path MTU discovery
interactions.

For many/most deployments, a fixed minimum tunnel MTU of
1500 bytes would seem advisable.

> A vendor could provide fragmentation or ICMP
> configuration options, either of which could be useful depending on the
> reliability of the network that carries the tunnel. (Of course the
> network carrying the tunnel could simply have a larger MTU.) The
> receiving end of the tunnel would have to support reassembly of tunnel
> fragments for multi-vendor interop.
>
>
> As for ICMP black-holes, is this likely to be standard practice with
> ICMP6 as well (vs. being done to protect old IPv4 routers from attacks
> on their expensive control-path processing) ?

Studies have been cited on the RRG list showing
non-negligible losses of ICMPv6 PTB messages as
well as significant losses of ICMPv4 PTB messages.
Trusting an untrustworthy network seems like at
best a tenuous approach.

Thanks - Fred
fred.l.templin@boeing.com

> David Dolson
> Software Architect, Sandvine Incorporated.
> http://www.sandvine.com
>
>
>
> > -----Original Message-----
> > From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org]
> On
> > Behalf Of Templin, Fred L
> > Sent: Friday, February 05, 2010 5:17 PM
> > To: Ed Jankiewicz; Behave WG; softwires@ietf.org
> > Subject: Re: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
> >
> > Hi Ed,
> >
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> > Behalf Of Ed Jankiewicz
> > > Sent: Wednesday, February 03, 2010 9:21 AM
> > > To: Behave WG; softwires@ietf.org
> > > Subject: [BEHAVE] PMTU Discovery and ICMPv6 filtering
> > >
> > > One of my colleagues received a long comment on Path MTU Discovery
> > recommendations his organization
> > > published and is seeking advice.  I recall this has been discussed
> > several times at IETF meetings,
> > > not sure which WG, so this may be redundant.  I've tried to
> summarize
> > the salient points below, and
> > > have two broad questions on this:  Are these points already covered
> > in RFCs (other than 4459, 4890)
> > > or current Internet-Drafts? If so, I would appreciate pointers.  If
> > not already covered by current
> > > publications, is there interest in documenting the problem and
> > comparing the solutions/drawbacks?
> > >
> > > The commenter basically wrote:
> > >
> > > IPv4 and IPv6 treat packets exceeding MTU differently - IPv4 will
> > fragment packets that are "too big"
> > > but IPv6 will drop the packet and respond with ICMPv6 "too-big"
> error
> > message. [The subject
> > > publication] recommends using the Path MTU Discovery Protocol to
> > discover the end-to-end PMTU, which
> > > relies on ICMPv6 error messages. These may be blocked by various
> > "filters" and IPsec gateways, which
> > > is the case in many operational networks.
> > >
> > > However, even when ICMPv6 is not blocked, IPsec gateways (in tunnel
> > mode) add extra headers, and
> > > there can be more than one tunnel header involved (routers also
> > create tunnels). When a "too-big"
> > > message is sent the router will return put in its ICMPv6 message the
> > value of the MTU on the next
> > > link at layer 2. The host receiving this MTU value in an ICMP
> message
> > at part of the Path MTU
> > > Discovery Protocol has no way of knowing how many extra tunnel
> > headers are added along the path, and
> > > so if it just takes the reported MTU value without allowing for
> these
> > extra headers the process will
> > > keep on failing and will not recover. We have seen this behavior in
> > our experiments.
> > >
> > > This can be prevented by ensuring that the maximum packet size sent
> > by the host is smaller than the
> > > layer 2 limit: smaller by an amount estimated to be sufficient to
> > allow room for extra headers to be
> > > added along the path. Several ways of achieving this are possible:
> > >
> > > (1) Set this reduced MTU value on the on the IPSec gateway LAN
> > interface; the host then discovers
> > > this MTU through the PMTUD.
> > >
> > > (2) Statically configure this reduced MTU value into the host and
> > switch off PMTUD.
> > >
> > > (3) Set a reduced MTU at the IPSec gateway WAN interface; The IPSec
> > gateway acts as a host on this
> > > interface and so can do packet fragmentation.
> > >
> > > (4) Provide the capability in the IPSec gateway to discover the MTU
> > on its WAN interface, subtract
> > > the maximum header size that this gateway will add to packets
> > presented on its LAN interface, which
> > > the host can then discover through the PMTUD.
> > >
> > > Method (4) would be the best solution, but is not currently
> available
> > in the IPSec gateway products.
> > > The next best solution is (1), which has been used [in commenter
> > experiments]. This is not as good as
> > > (4) because it requires manual intervention, and an understanding of
> > how to calculate the appropriate
> > > (reduced) MTU value.
> > > The next best solution is (2), the only disadvantage of this
> approach
> > is that only one value can be
> > > set for all paths and so the worst case (lowest) value has to be
> > used. In a complex network it may
> > > not always be obvious what the worst case path is, and so a
> > conservative estimate may be necessary.
> > > Even so this could be preferable in some deployment scenarios since
> > the path-MTU discovery protocol
> > > relies on the passage of ICMP messages which are sometimes blocked
> by
> > firewalls and other security
> > > devices.
> > > Approach (3) is the worst solution since it will cause many IP
> > packets to be fragmented which is
> > > inefficient (both because, unlike IPv4, the IPv6 header has to be
> > extended to include the
> > > fragmentation offset field, and because it will result the second
> > fragment being very small, i.e. the
> > > ratio of user-data to IP header size will be poor).
> > >
> > > It is likely that for immediate use option (1) should be used
> > although (4) would be better if it were
> > > supported in the relevant products.
> >
> > (1) seems like a safe option at face value, but can lead
> > to undesirable inefficiencies. Consider for example the
> > diagram below:
> >
> >             L1    L2               L3
> >             |     |                |
> >         W --|--R--|--GW1<=3D=3D=3D=3D>GW2--|--Z
> >             |     |   (Internet)   |
> >                X--|     L4, L5,
> >                Y--|     L6, etc.
> >
> > Here, we have a tunnel beteen 'GW1' and 'GW2' over the
> > Internet to connect two networks. 'GW1' sets a reduced
> > MTU 'M' on its LAN interface connected to link 'L2', and
> > also advertises 'M' in the Router Advertisements it sends
> > on 'L2'. Hosts 'X' and 'Y' pick up the reduced MTU from
> > the RA and limit the size of the packets they send to at
> > most 'M' bytes. But, host 'W' connected to link 'L1' does
> > not see the MTU reduction, and hence will routinely send
> > packets larger than 'M' to any hosts beyond router 'R'
> > such as 'X', 'Y' and 'Z'. These packets will be dropped
> > with an ICMPv6 PTB returned, then 'W' will be forced to
> > reduce its packet size and retransmit. The only way to
> > prevent this is to drive the reduced MTU 'M' deeply into
> > the entire network stacked up behind 'GW1', which may
> > contain arbitrarily many additional routers and links.
> >
> > Now, even if the reduced MTU 'M' were propagated deeply
> > throughout the 'GW1' network, if most communications
> > remain localized hosts would only be able to use a packet
> > size of at most 'M' even if their links natively support
> > a much larger MTU. Consider for example that link 'L2'
> > in the diagram has a native MTU of 9kb, but the effective
> > MTU across the 'GW1'<=3D=3D=3D=3D>'GW2' tunnel is only 1400. 'GW1'
> > will advertise 1400 on link 'L1', and communications
> > betweenhosts 'X' and 'Y' will be restricted to using at
> > most 1400 byte packets when they could have used 9kb.
> >
> > There are a couple of factors to consider in terms of
> > what might be a better solution. First, what are the
> > expected data rates over the 'GW1'<=3D=3D=3D=3D>'GW2' tunnel,
> > and second what are the performance characteristics of
> > those gateways? If the data rates are such that GW1 and
> > GW2 are already operating at their peak performance even
> > without taking on any additional processing overhead,
> > then the best solution would be to make sure that all
> > links over which the tunnel might travel (e.g., 'L4',
> > 'L5', 'L6', etc.) are large enough to "hide" the tunnel
> > encapsulation artifact. For example, if all links 'L4'
> > 'L5', 'L6', etc. configure a native MTU of no smaller
> > than 1600 and the encapsulation overhead for the tunnel
> > is 100 bytes, then all routers and hosts on the LAN side
> > of 'GW1' would be able to happily use a 1500 MTU. If the
> > MTUs of 'L4', etc. cannot be controlled, however, then
> > there is no recourse but to use option (1) and cope with
> > the inefficiencies.
> >
> > On the other hand, if the data rates across the tunnel
> > are nominal and/or 'GW1' and 'GW2' have more than
> > sufficient processing capability to take on a modest
> > amount of additional overhead, the GWs can use tunnel
> > fragmentation so that 'GW1' can present a solid MTU on
> > its LAN side interface that does not reflect the size
> > of the tunnel encapsulation headers. If the tunnel
> > fragmentation could accommodate an MTU of at least 1500
> > in this way, then 'GW1' would be able to observe the
> > "de facto Internet cell size" of 1500. If we further
> > assume that the vast majority of hosts in the world
> > today either limit their packet sizes to no more than
> > 1500 bytes or are willing to assume the risk of silent
> > loss of packets larger than 1500 due to MTU restrictions,
> > then there is no need to place artificial restrictions
> > on the size of packets that can be used within the 'GW1'
> > network. This latter class of hosts (those that send
> > packets larger than 1500) would be best served to use
> > their own host-based MTU probing mechanisms for sending
> > packets larger than 1500 in case the network is somehow
> > silently dropping PMTUD messages. RFC4821 was specifically
> > designed for this purpose.
> >
> > End result - whenever it is practically possible, tunnel
> > routers should use tunnel fragmentation and hosts should
> > use RFC4821.
> >
> > Fred
> > fred.l.templin@boeing.com
> >
> > > --
> > > Ed Jankiewicz - SRI International
> > > Fort Monmouth Branch Office - IPv6 Research
> > > Supporting DISA Standards Engineering Branch
> > > 732-389-1003 or  ed.jankiewicz@sri.com
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www.ietf.org/mailman/listinfo/behave
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From dwing@cisco.com  Mon Feb  8 14:33:21 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 DCA443A72A0 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 14:33:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 101bpnZIqyvx for <behave@core3.amsl.com>; Mon,  8 Feb 2010 14:33:21 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 1B8583A7253 for <behave@ietf.org>; Mon,  8 Feb 2010 14:33:21 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0GAKQgcEurRN+K/2dsb2JhbACHe4EStkWXTIRUBA
X-IronPort-AV: E=Sophos;i="4.49,431,1262563200"; d="scan'208";a="147754305"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 08 Feb 2010 22:34:25 +0000
Received: from dwingwxp01 (dhcp-128-107-166-142.cisco.com [128.107.166.142]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o18MYPQT004518; Mon, 8 Feb 2010 22:34:25 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com> <4B704153.2020007@it.uc3m.es> <015801caa8e6$9b72fff0$c4f0200a@cisco.com> <75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com>
Date: Mon, 8 Feb 2010 14:34:25 -0800
Message-ID: <02cd01caa90e$dde921c0$c4f0200a@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
In-Reply-To: <75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com>
Thread-Index: Acqo/RoBFmN2MbT7RMOT+S89TkdfZwAELDjg
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 22:33:22 -0000

 

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com] 
> Sent: Monday, February 08, 2010 12:27 PM
> To: Dan Wing
> Cc: 'marcelo bagnulo braun'; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> On 8 feb 2010, at 18:46, Dan Wing wrote:
> 
> > For stateful translation, it is _possible_ for the translator
> > to include MTU in its IPv4 and IPv6 tables, and do provide 
> end-to-end
> > PMTUD even for links below 1280.  To do this, a stateful translator
> > would maintain the MTU for all IPv4 hosts that currently 
> have a mapping,
> > and go ahead and translate with DF=1.
> 
> So in this case the translator receives IPv6 packets with or 
> without a fragment header that are 1280 bytes but the IPv4 
> destination has a path MTU of (say) 576 bytes. This means the 
> translator has to fragment.
> 
> So essentially this means doing more work (keeping PMTUD 
> state for the IPv4 path) in order to do even more work later 
> (fragment). Not sure how that makes sense... If you simply 
> set DF=0 for packets < 1280 bytes then the people who thought 
> it was a good idea to set an unreasonably small MTU are the 
> ones who get to fragment, which to me seems how it should be.

Yes, it means the translator is doing the effort of fragmenting
rather than the router immediately in front of the small-MTU
link.  However, by doing it this way, we can maintain end-to-end
PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
packets with the fragmentation header.  Those hosts now know
their packets are being fragmented.  Certainly there was some
perceived value in the IPv6 knowing its packets are being
fragmented.

> (Although in practice few fragments will happen because in 
> IPv4 PMTUD is only supported for TCP and TCP has the MSS option.)

I agree that nearly 100% of PMTUD on IPv4 is with TCP.

But there isn't anything prohibiting PMTUD for UDP.  
For UDP, draft-petithuguenin-behave-stun-pmtud describes how to do
PMTUD and uses the technique described in RFC4821 (which doesn't 
rely on receiving ICMP messages).

> > Then, if an IPv4 ICMP PTB is
> > received and describes an MTU smaller than 1280, go ahead 
> > and translate
> > that to ICMPv6 (in the hopes of hitting the ~45% of hosts that will
> > successfully process it),
> 
> You can always do that, yes.

I tend to think, though, we don't want to figure this out
for stateful translators at this point in time.  If it is
found useful/necessary, it can be specified later.  It feels
like an optimization to retain PMTUD awareness in the IPv6
network for less-than 1280 payloads for stateful translation.
It does not seem necessary, because we can maintain PMTUD
end-to-end for packets bigger than 1280 bytes.  Thus, 
stateful (or stateful) translation does not harm the hoped-
for transition to larger MTUs in the future.

-d


From iljitsch@muada.com  Mon Feb  8 15:01:33 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 6241828C107 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 15:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 Zyib4XpDasMn for <behave@core3.amsl.com>; Mon,  8 Feb 2010 15:01:32 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 24AE428C0E8 for <behave@ietf.org>; Mon,  8 Feb 2010 15:01:31 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o18N1Fbs033591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 00:01:16 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <02cd01caa90e$dde921c0$c4f0200a@cisco.com>
Date: Tue, 9 Feb 2010 00:02:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com> <4B704153.2020007@it.uc3m.es> <015801caa8e6$9b72fff0$c4f0200a@cisco.com> <75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com> <02cd01caa90e$dde921c0$c4f0200a@cisco.com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 23:01:33 -0000

On 8 feb 2010, at 23:34, Dan Wing wrote:

>> So essentially this means doing more work (keeping PMTUD=20
>> state for the IPv4 path) in order to do even more work later=20
>> (fragment). Not sure how that makes sense...

> Yes, it means the translator is doing the effort of fragmenting
> rather than the router immediately in front of the small-MTU
> link.  However, by doing it this way, we can maintain end-to-end
> PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> packets with the fragmentation header.

No, the two issues are orthogonal.

At some point, an IPv6 host sends a packet that is larger than the IPv4 =
PMTU. A router sends back a too big message. Issue A is how to handle =
this too big message. Issue B is what happens to packets that the IPv6 =
host subsequently sends.

I think there is agreement that A should be handled by simply =
translating the IPv4 too big too IPv6 and adjusting it as per the header =
size differences, but otherwise let it through transparently. (I once =
argued for rewriting it to 1280, though.)

Nothing has changed here.

But now for part B. A stateless translator can't monitor the IPv4 PMTU. =
Not because it's stateful (we're talking per destination state, not per =
session state, it would be doable to track this) but because there may =
be more than one translator so any given translator may not see all =
packets. So for stateless translation when the translator has a < 1280 =
packet with no fragment header we don't know whether this is because =
PMTUD was succesful and the packet size fits in the PMTU, or the IPv6 =
host ignored the < 1280 too big message and is omitting the fragment =
header in violation of the relevant RFCs. In order to be compatible with =
the latter the only thing we can do is set DF to 0.

(I just realize that we don't know what happens when for instance the =
PMTU is 1000 and the IPv6 host wants to send a 1100-byte packet: does it =
include a fragment header or not?)

Note that for part B, if there _is_ a fragment header, that will also =
trigger the translator to set DF to 0. So in the case where the IPv6 =
hosts are well behaved there is no change to either parts A or B.

In the stateful case we know all packets flow through the same =
translator so we get to track the IPv4 PMTU so when there is an IPv6 =
packet that needs to be translated we know whether it's bigger or =
smaller than the PMTU so we can send packets that are bigger with DF=3D1 =
and packets that are smaller with DF=3D0 and if we are to, also =
immediately fragment them. However, there is no advantage to doing this =
extra work because even if we get to set DF=3D1 on some packets that are =
smaller than the PMTU that only lets us discover a reduction in the =
PMTU, but that discovery doesn't buy us anything because the IPv6 host =
isn't going to reduce its packet size. Fragmenting at the translator =
also doesn't buy the translator anything and it may even get the packet =
blocked or create more work if there's a firewall with a > 1280 MTU =
before the path hits the < 1280 MTU which would need to reassemble the =
packet to observe the port numbers. And it could be an attack vector: =
attackers could send too bigs with tiny MTUs to make the translator work =
harder.

> Certainly there was some
> perceived value in the IPv6 knowing its packets are being
> fragmented.

I don't think so. Even if the application somehow learns this =
information, what is it supposed to do then?

> I agree that nearly 100% of PMTUD on IPv4 is with TCP.

> But there isn't anything prohibiting PMTUD for UDP.

With sufficient thrust pigs fly just fine...

Generally, it's not easy for UDP applications to limit their packet =
sizes. So the protocol would have to support changing the packet size on =
the fly and then the application would have to react to too big =
messages. Not impossible, but I've never seen it happen. But if =
BitTorrent goes to UDP it's likely they'll put this in in some way.

> I tend to think, though, we don't want to figure this out
> for stateful translators at this point in time.  If it is
> found useful/necessary, it can be specified later.

Right.=

From dwing@cisco.com  Mon Feb  8 15:27:35 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 AF8B33A74CC for <behave@core3.amsl.com>; Mon,  8 Feb 2010 15:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 1Ij0hSsPyFMC for <behave@core3.amsl.com>; Mon,  8 Feb 2010 15:27:34 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 91EFB3A68C7 for <behave@ietf.org>; Mon,  8 Feb 2010 15:27:34 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0GAIMtcEurRN+J/2dsb2JhbACHe4EStkaXV4I7B4ISBI5H
X-IronPort-AV: E=Sophos;i="4.49,432,1262563200"; d="scan'208";a="147781191"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 08 Feb 2010 23:28:38 +0000
Received: from dwingwxp01 (dhcp-128-107-166-142.cisco.com [128.107.166.142]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o18NScVO012261; Mon, 8 Feb 2010 23:28:38 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com> <4B704153.2020007@it.uc3m.es> <015801caa8e6$9b72fff0$c4f0200a@cisco.com> <75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com> <02cd01caa90e$dde921c0$c4f0200a@cisco.com> <B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com>
Date: Mon, 8 Feb 2010 15:28:38 -0800
Message-ID: <02f101caa916$712d0170$c4f0200a@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
In-Reply-To: <B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com>
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1w
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 08 Feb 2010 23:27:35 -0000

 

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com] 
> Sent: Monday, February 08, 2010 3:02 PM
> To: Dan Wing
> Cc: 'marcelo bagnulo braun'; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> On 8 feb 2010, at 23:34, Dan Wing wrote:
> 
> >> So essentially this means doing more work (keeping PMTUD 
> >> state for the IPv4 path) in order to do even more work later 
> >> (fragment). Not sure how that makes sense...
> 
> > Yes, it means the translator is doing the effort of fragmenting
> > rather than the router immediately in front of the small-MTU
> > link.  However, by doing it this way, we can maintain end-to-end
> > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > packets with the fragmentation header.
> 
> No, the two issues are orthogonal.
> 
> At some point, an IPv6 host sends a packet that is larger 
> than the IPv4 PMTU. A router sends back a too big message. 
> Issue A is how to handle this too big message. Issue B is 
> what happens to packets that the IPv6 host subsequently sends.

A stateless translator cannot identify 'subsequent' packets,
because it doesn't remember previous state.  

> I think there is agreement that A should be handled by simply 
> translating the IPv4 too big too IPv6 and adjusting it as per 
> the header size differences, but otherwise let it through 
> transparently. (I once argued for rewriting it to 1280, though.)
> 
> Nothing has changed here.
> 
> But now for part B. A stateless translator can't monitor the 
> IPv4 PMTU. Not because it's stateful (we're talking per 
> destination state, not per session state, it would be doable 
> to track this) but because there may be more than one 
> translator so any given translator may not see all packets. 
> So for stateless translation when the translator has a < 1280 
> packet with no fragment header we don't know whether this is 
> because PMTUD was succesful and the packet size fits in the 
> PMTU, or the IPv6 host ignored the < 1280 too big message and 
> is omitting the fragment header in violation of the relevant 
> RFCs. In order to be compatible with the latter the only 
> thing we can do is set DF to 0.
> 
> (I just realize that we don't know what happens when for 
> instance the PMTU is 1000 and the IPv6 host wants to send a 
> 1100-byte packet: does it include a fragment header or not?)
> 
> Note that for part B, if there _is_ a fragment header, that 
> will also trigger the translator to set DF to 0. So in the 
> case where the IPv6 hosts are well behaved there is no change 
> to either parts A or B.

So, I believe we are in agreement:  IPv6 packets less than
1280 need to be translated to IPv4 and sent with DF=0.

> In the stateful case we know all packets flow through the 
> same translator so we get to track the IPv4 PMTU so when 
> there is an IPv6 packet that needs to be translated we know 
> whether it's bigger or smaller than the PMTU so we can send 
> packets that are bigger with DF=1 and packets that are 
> smaller with DF=0 and if we are to, also immediately fragment 
> them. However, there is no advantage to doing this extra work 
> because even if we get to set DF=1 on some packets that are 
> smaller than the PMTU that only lets us discover a reduction 
> in the PMTU, but that discovery doesn't buy us anything 
> because the IPv6 host isn't going to reduce its packet size. 

I agree the IPv6 host won't reduce its packet size below
1280.  But the IPv6 host becomes aware that the path MTU
is smaller than 1280.  I don't know if the IPv6 host finds
that useful/valuable to know the path MTU is less than the
IPv6 minimum MTU.

> Fragmenting at the translator also doesn't buy the translator 
> anything and it may even get the packet blocked or create 
> more work if there's a firewall with a > 1280 MTU before the 
> path hits the < 1280 MTU which would need to reassemble the 
> packet to observe the port numbers. And it could be an attack 
> vector: attackers could send too bigs with tiny MTUs to make 
> the translator work harder.
> 
> > Certainly there was some
> > perceived value in the IPv6 knowing its packets are being
> > fragmented.
> 
> I don't think so. Even if the application somehow learns this 
> information, what is it supposed to do then?

Don't know.  It is obviously easier for the 6/4 translator to
simply fragment the packet (or translate and send with DF=0) without 
informing the IPv6 host, but there is long-standing text in both
RFC2460 and its predecessor (RFC1883) that says to send back
ICMPv6 PTB and the IPv6 host is then supposed to send packets
with the fragmentation header.

> > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> 
> > But there isn't anything prohibiting PMTUD for UDP.
> 
> With sufficient thrust pigs fly just fine...
> 
> Generally, it's not easy for UDP applications to limit their 
> packet sizes. So the protocol would have to support changing 
> the packet size on the fly and then the application would 
> have to react to too big messages.

draft-petithuguenin-behave-stun-pmtud does not rely on
ICMP packet too big messages.

> Not impossible, but I've never seen it happen.

Me, neither.  I'm just trying to temper the "only TCP does
PMTUD", because UDP can do PMTUD.  And of course there is value
in sending the largest packets possible.

> But if BitTorrent goes to UDP it's 
> likely they'll put this in in some way.

As of version 2.x, the most popular BitTorrent client on
Windows (uTorrent) has implemented uTP, for whatever that's
worth.  I don't know if they're doing PMTUD, though.  Beta
versions of uTorrent are available for OSX, too, and I expect
they will soon support uTP (if they aren't already).

> > I tend to think, though, we don't want to figure this out
> > for stateful translators at this point in time.  If it is
> > found useful/necessary, it can be specified later.
> 
> Right.=

-d


From Fred.L.Templin@boeing.com  Mon Feb  8 16:01:08 2010
Return-Path: <Fred.L.Templin@boeing.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 5D93828C1C5 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 16:01:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.614
X-Spam-Level: 
X-Spam-Status: No, score=-6.614 tagged_above=-999 required=5 tests=[AWL=-0.015, 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 p9wxrdRAr0J3 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 16:01:07 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 0D04C28C1B2 for <behave@ietf.org>; Mon,  8 Feb 2010 16:01:06 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o1901xvl010404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Feb 2010 18:01:59 -0600 (CST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o1901wYn000871; Mon, 8 Feb 2010 16:01:58 -0800 (PST)
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o1901wN9000858 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 8 Feb 2010 16:01:58 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Mon, 8 Feb 2010 16:01:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Dan Wing <dwing@cisco.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Date: Mon, 8 Feb 2010 16:01:56 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNA=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com> <02f101caa916$712d0170$c4f0200a@cisco.com>
In-Reply-To: <02f101caa916$712d0170$c4f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 00:01:08 -0000

The concern with setting DF=3D0 on the IPv4 side for packets
that are 1280 or smaller on the IPv6 side is the possibility
for RFC4963 data corruption if we let it run at line rate.

There are certainly plenty of websites on the IPv4 Internet
that set DF=3D0 on every packet they send, and many even use
packet sizes larger than 1280. But, how many of them send
large packets at line rate?

Fred
fred.l.templin@boeing.com =20

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of Dan Wing
> Sent: Monday, February 08, 2010 3:29 PM
> To: 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
>=20
>=20
> > -----Original Message-----
> > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > Sent: Monday, February 08, 2010 3:02 PM
> > To: Dan Wing
> > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> >
> > On 8 feb 2010, at 23:34, Dan Wing wrote:
> >
> > >> So essentially this means doing more work (keeping PMTUD
> > >> state for the IPv4 path) in order to do even more work later
> > >> (fragment). Not sure how that makes sense...
> >
> > > Yes, it means the translator is doing the effort of fragmenting
> > > rather than the router immediately in front of the small-MTU
> > > link.  However, by doing it this way, we can maintain end-to-end
> > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > > packets with the fragmentation header.
> >
> > No, the two issues are orthogonal.
> >
> > At some point, an IPv6 host sends a packet that is larger
> > than the IPv4 PMTU. A router sends back a too big message.
> > Issue A is how to handle this too big message. Issue B is
> > what happens to packets that the IPv6 host subsequently sends.
>=20
> A stateless translator cannot identify 'subsequent' packets,
> because it doesn't remember previous state.
>=20
> > I think there is agreement that A should be handled by simply
> > translating the IPv4 too big too IPv6 and adjusting it as per
> > the header size differences, but otherwise let it through
> > transparently. (I once argued for rewriting it to 1280, though.)
> >
> > Nothing has changed here.
> >
> > But now for part B. A stateless translator can't monitor the
> > IPv4 PMTU. Not because it's stateful (we're talking per
> > destination state, not per session state, it would be doable
> > to track this) but because there may be more than one
> > translator so any given translator may not see all packets.
> > So for stateless translation when the translator has a < 1280
> > packet with no fragment header we don't know whether this is
> > because PMTUD was succesful and the packet size fits in the
> > PMTU, or the IPv6 host ignored the < 1280 too big message and
> > is omitting the fragment header in violation of the relevant
> > RFCs. In order to be compatible with the latter the only
> > thing we can do is set DF to 0.
> >
> > (I just realize that we don't know what happens when for
> > instance the PMTU is 1000 and the IPv6 host wants to send a
> > 1100-byte packet: does it include a fragment header or not?)
> >
> > Note that for part B, if there _is_ a fragment header, that
> > will also trigger the translator to set DF to 0. So in the
> > case where the IPv6 hosts are well behaved there is no change
> > to either parts A or B.
>=20
> So, I believe we are in agreement:  IPv6 packets less than
> 1280 need to be translated to IPv4 and sent with DF=3D0.
>=20
> > In the stateful case we know all packets flow through the
> > same translator so we get to track the IPv4 PMTU so when
> > there is an IPv6 packet that needs to be translated we know
> > whether it's bigger or smaller than the PMTU so we can send
> > packets that are bigger with DF=3D1 and packets that are
> > smaller with DF=3D0 and if we are to, also immediately fragment
> > them. However, there is no advantage to doing this extra work
> > because even if we get to set DF=3D1 on some packets that are
> > smaller than the PMTU that only lets us discover a reduction
> > in the PMTU, but that discovery doesn't buy us anything
> > because the IPv6 host isn't going to reduce its packet size.
>=20
> I agree the IPv6 host won't reduce its packet size below
> 1280.  But the IPv6 host becomes aware that the path MTU
> is smaller than 1280.  I don't know if the IPv6 host finds
> that useful/valuable to know the path MTU is less than the
> IPv6 minimum MTU.
>=20
> > Fragmenting at the translator also doesn't buy the translator
> > anything and it may even get the packet blocked or create
> > more work if there's a firewall with a > 1280 MTU before the
> > path hits the < 1280 MTU which would need to reassemble the
> > packet to observe the port numbers. And it could be an attack
> > vector: attackers could send too bigs with tiny MTUs to make
> > the translator work harder.
> >
> > > Certainly there was some
> > > perceived value in the IPv6 knowing its packets are being
> > > fragmented.
> >
> > I don't think so. Even if the application somehow learns this
> > information, what is it supposed to do then?
>=20
> Don't know.  It is obviously easier for the 6/4 translator to
> simply fragment the packet (or translate and send with DF=3D0) without
> informing the IPv6 host, but there is long-standing text in both
> RFC2460 and its predecessor (RFC1883) that says to send back
> ICMPv6 PTB and the IPv6 host is then supposed to send packets
> with the fragmentation header.
>=20
> > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> >
> > > But there isn't anything prohibiting PMTUD for UDP.
> >
> > With sufficient thrust pigs fly just fine...
> >
> > Generally, it's not easy for UDP applications to limit their
> > packet sizes. So the protocol would have to support changing
> > the packet size on the fly and then the application would
> > have to react to too big messages.
>=20
> draft-petithuguenin-behave-stun-pmtud does not rely on
> ICMP packet too big messages.
>=20
> > Not impossible, but I've never seen it happen.
>=20
> Me, neither.  I'm just trying to temper the "only TCP does
> PMTUD", because UDP can do PMTUD.  And of course there is value
> in sending the largest packets possible.
>=20
> > But if BitTorrent goes to UDP it's
> > likely they'll put this in in some way.
>=20
> As of version 2.x, the most popular BitTorrent client on
> Windows (uTorrent) has implemented uTP, for whatever that's
> worth.  I don't know if they're doing PMTUD, though.  Beta
> versions of uTorrent are available for OSX, too, and I expect
> they will soon support uTP (if they aren't already).
>=20
> > > I tend to think, though, we don't want to figure this out
> > > for stateful translators at this point in time.  If it is
> > > found useful/necessary, it can be specified later.
> >
> > Right.=3D
>=20
> -d
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From dwing@cisco.com  Mon Feb  8 16:23:29 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 35A2B3A69A0 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 16:23:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 JI6YYRHfDK8e for <behave@core3.amsl.com>; Mon,  8 Feb 2010 16:23:28 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id A28633A70E1 for <behave@ietf.org>; Mon,  8 Feb 2010 16:23:27 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0GAKM6cEurRN+K/2dsb2JhbACHe4EStnaXW4I7B4ISBI5H
X-IronPort-AV: E=Sophos;i="4.49,432,1262563200"; d="scan'208";a="84765069"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by rtp-iport-2.cisco.com with ESMTP; 09 Feb 2010 00:24:12 +0000
Received: from dwingwxp01 (dhcp-128-107-166-142.cisco.com [128.107.166.142]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o190OCe4008797; Tue, 9 Feb 2010 00:24:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com> <02f101caa916$712d0170$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com>
Date: Mon, 8 Feb 2010 16:24:12 -0800
Message-ID: <032d01caa91e$343c71d0$c4f0200a@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
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com>
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cA==
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 00:23:29 -0000

 

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] 
> Sent: Monday, February 08, 2010 4:02 PM
> To: Dan Wing; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> The concern with setting DF=0 on the IPv4 side for packets
> that are 1280 or smaller on the IPv6 side is the possibility
> for RFC4963 data corruption if we let it run at line rate.

At high speed with the same source/destination addresses, and when
fragmentation on the IPv4 network occurs.  That is, sending lots of packets
with DF=0 does not, by itself, cause a problem even if they are fragmented on
the same link -- so long as they have different source or different
destination addresses.  I agree we should make a note of that.  

Is there another approach that should be considered to avoid that concern?

> There are certainly plenty of websites on the IPv4 Internet
> that set DF=0 on every packet they send, and many even use
> packet sizes larger than 1280. But, how many of them send
> large packets at line rate?

Content delivery networks?

-d


> Fred
> fred.l.templin@boeing.com  
> 
> > -----Original Message-----
> > From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > Sent: Monday, February 08, 2010 3:29 PM
> > To: 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > Sent: Monday, February 08, 2010 3:02 PM
> > > To: Dan Wing
> > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > >
> > > >> So essentially this means doing more work (keeping PMTUD
> > > >> state for the IPv4 path) in order to do even more work later
> > > >> (fragment). Not sure how that makes sense...
> > >
> > > > Yes, it means the translator is doing the effort of fragmenting
> > > > rather than the router immediately in front of the small-MTU
> > > > link.  However, by doing it this way, we can maintain end-to-end
> > > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > > > packets with the fragmentation header.
> > >
> > > No, the two issues are orthogonal.
> > >
> > > At some point, an IPv6 host sends a packet that is larger
> > > than the IPv4 PMTU. A router sends back a too big message.
> > > Issue A is how to handle this too big message. Issue B is
> > > what happens to packets that the IPv6 host subsequently sends.
> > 
> > A stateless translator cannot identify 'subsequent' packets,
> > because it doesn't remember previous state.
> > 
> > > I think there is agreement that A should be handled by simply
> > > translating the IPv4 too big too IPv6 and adjusting it as per
> > > the header size differences, but otherwise let it through
> > > transparently. (I once argued for rewriting it to 1280, though.)
> > >
> > > Nothing has changed here.
> > >
> > > But now for part B. A stateless translator can't monitor the
> > > IPv4 PMTU. Not because it's stateful (we're talking per
> > > destination state, not per session state, it would be doable
> > > to track this) but because there may be more than one
> > > translator so any given translator may not see all packets.
> > > So for stateless translation when the translator has a < 1280
> > > packet with no fragment header we don't know whether this is
> > > because PMTUD was succesful and the packet size fits in the
> > > PMTU, or the IPv6 host ignored the < 1280 too big message and
> > > is omitting the fragment header in violation of the relevant
> > > RFCs. In order to be compatible with the latter the only
> > > thing we can do is set DF to 0.
> > >
> > > (I just realize that we don't know what happens when for
> > > instance the PMTU is 1000 and the IPv6 host wants to send a
> > > 1100-byte packet: does it include a fragment header or not?)
> > >
> > > Note that for part B, if there _is_ a fragment header, that
> > > will also trigger the translator to set DF to 0. So in the
> > > case where the IPv6 hosts are well behaved there is no change
> > > to either parts A or B.
> > 
> > So, I believe we are in agreement:  IPv6 packets less than
> > 1280 need to be translated to IPv4 and sent with DF=0.
> > 
> > > In the stateful case we know all packets flow through the
> > > same translator so we get to track the IPv4 PMTU so when
> > > there is an IPv6 packet that needs to be translated we know
> > > whether it's bigger or smaller than the PMTU so we can send
> > > packets that are bigger with DF=1 and packets that are
> > > smaller with DF=0 and if we are to, also immediately fragment
> > > them. However, there is no advantage to doing this extra work
> > > because even if we get to set DF=1 on some packets that are
> > > smaller than the PMTU that only lets us discover a reduction
> > > in the PMTU, but that discovery doesn't buy us anything
> > > because the IPv6 host isn't going to reduce its packet size.
> > 
> > I agree the IPv6 host won't reduce its packet size below
> > 1280.  But the IPv6 host becomes aware that the path MTU
> > is smaller than 1280.  I don't know if the IPv6 host finds
> > that useful/valuable to know the path MTU is less than the
> > IPv6 minimum MTU.
> > 
> > > Fragmenting at the translator also doesn't buy the translator
> > > anything and it may even get the packet blocked or create
> > > more work if there's a firewall with a > 1280 MTU before the
> > > path hits the < 1280 MTU which would need to reassemble the
> > > packet to observe the port numbers. And it could be an attack
> > > vector: attackers could send too bigs with tiny MTUs to make
> > > the translator work harder.
> > >
> > > > Certainly there was some
> > > > perceived value in the IPv6 knowing its packets are being
> > > > fragmented.
> > >
> > > I don't think so. Even if the application somehow learns this
> > > information, what is it supposed to do then?
> > 
> > Don't know.  It is obviously easier for the 6/4 translator to
> > simply fragment the packet (or translate and send with DF=0) without
> > informing the IPv6 host, but there is long-standing text in both
> > RFC2460 and its predecessor (RFC1883) that says to send back
> > ICMPv6 PTB and the IPv6 host is then supposed to send packets
> > with the fragmentation header.
> > 
> > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > >
> > > > But there isn't anything prohibiting PMTUD for UDP.
> > >
> > > With sufficient thrust pigs fly just fine...
> > >
> > > Generally, it's not easy for UDP applications to limit their
> > > packet sizes. So the protocol would have to support changing
> > > the packet size on the fly and then the application would
> > > have to react to too big messages.
> > 
> > draft-petithuguenin-behave-stun-pmtud does not rely on
> > ICMP packet too big messages.
> > 
> > > Not impossible, but I've never seen it happen.
> > 
> > Me, neither.  I'm just trying to temper the "only TCP does
> > PMTUD", because UDP can do PMTUD.  And of course there is value
> > in sending the largest packets possible.
> > 
> > > But if BitTorrent goes to UDP it's
> > > likely they'll put this in in some way.
> > 
> > As of version 2.x, the most popular BitTorrent client on
> > Windows (uTorrent) has implemented uTP, for whatever that's
> > worth.  I don't know if they're doing PMTUD, though.  Beta
> > versions of uTorrent are available for OSX, too, and I expect
> > they will soon support uTP (if they aren't already).
> > 
> > > > I tend to think, though, we don't want to figure this out
> > > > for stateful translators at this point in time.  If it is
> > > > found useful/necessary, it can be specified later.
> > >
> > > Right.=
> > 
> > -d
> > 
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave


From Fred.L.Templin@boeing.com  Mon Feb  8 17:10:16 2010
Return-Path: <Fred.L.Templin@boeing.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 27F0628C0D8 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 17:10:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.313
X-Spam-Level: 
X-Spam-Status: No, score=-6.313 tagged_above=-999 required=5 tests=[AWL=-0.314, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, 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 CMNmPhxF53kh for <behave@core3.amsl.com>; Mon,  8 Feb 2010 17:10:14 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 5729B3A6E22 for <behave@ietf.org>; Mon,  8 Feb 2010 17:10:14 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o191BAof014280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 8 Feb 2010 17:11:10 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o191B9pd026519; Mon, 8 Feb 2010 19:11:09 -0600 (CST)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o191B9PQ026512 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 8 Feb 2010 19:11:09 -0600 (CST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Mon, 8 Feb 2010 17:11:08 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Dan Wing <dwing@cisco.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Date: Mon, 8 Feb 2010 17:11:06 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cAABmZlw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com> <032d01caa91e$343c71d0$c4f0200a@cisco.com>
In-Reply-To: <032d01caa91e$343c71d0$c4f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 01:10:16 -0000

Dan,

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of Dan Wing
> Sent: Monday, February 08, 2010 4:24 PM
> To: Templin, Fred L; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
>=20
>=20
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > Sent: Monday, February 08, 2010 4:02 PM
> > To: Dan Wing; 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> >
> > The concern with setting DF=3D0 on the IPv4 side for packets
> > that are 1280 or smaller on the IPv6 side is the possibility
> > for RFC4963 data corruption if we let it run at line rate.
>=20
> At high speed with the same source/destination addresses, and when
> fragmentation on the IPv4 network occurs.  That is, sending lots of packe=
ts
> with DF=3D0 does not, by itself, cause a problem even if they are fragmen=
ted on
> the same link -- so long as they have different source or different
> destination addresses.  I agree we should make a note of that.

Yes, the concern is for same src,dst operating at line=20
rate. IPv6 apps assume that there is no possibility for
fragmentation in the network, hence they may not be as
shy as IPv4 apps when it comes to sending large packets
at high data rates. Having the translator set DF=3D0 can
break that assumption.
=20
> Is there another approach that should be considered to avoid that concern=
?

I still believe placement of the translator matters.
Placing the translator closer to the IPv4 host
reduces the portion of the path that is exposed to
IPv4 hops. This is true whether the DF=3D0 or DF=3D1
approach is used.

Fred
fred.l.templin@boeing.com

> > There are certainly plenty of websites on the IPv4 Internet
> > that set DF=3D0 on every packet they send, and many even use
> > packet sizes larger than 1280. But, how many of them send
> > large packets at line rate?
>=20
> Content delivery networks?
>=20
> -d
>=20
>=20
> > Fred
> > fred.l.templin@boeing.com
> >
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > Sent: Monday, February 08, 2010 3:29 PM
> > > To: 'Iljitsch van Beijnum'
> > > Cc: behave@ietf.org
> > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > > Sent: Monday, February 08, 2010 3:02 PM
> > > > To: Dan Wing
> > > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > > >
> > > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > > >
> > > > >> So essentially this means doing more work (keeping PMTUD
> > > > >> state for the IPv4 path) in order to do even more work later
> > > > >> (fragment). Not sure how that makes sense...
> > > >
> > > > > Yes, it means the translator is doing the effort of fragmenting
> > > > > rather than the router immediately in front of the small-MTU
> > > > > link.  However, by doing it this way, we can maintain end-to-end
> > > > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > > > > packets with the fragmentation header.
> > > >
> > > > No, the two issues are orthogonal.
> > > >
> > > > At some point, an IPv6 host sends a packet that is larger
> > > > than the IPv4 PMTU. A router sends back a too big message.
> > > > Issue A is how to handle this too big message. Issue B is
> > > > what happens to packets that the IPv6 host subsequently sends.
> > >
> > > A stateless translator cannot identify 'subsequent' packets,
> > > because it doesn't remember previous state.
> > >
> > > > I think there is agreement that A should be handled by simply
> > > > translating the IPv4 too big too IPv6 and adjusting it as per
> > > > the header size differences, but otherwise let it through
> > > > transparently. (I once argued for rewriting it to 1280, though.)
> > > >
> > > > Nothing has changed here.
> > > >
> > > > But now for part B. A stateless translator can't monitor the
> > > > IPv4 PMTU. Not because it's stateful (we're talking per
> > > > destination state, not per session state, it would be doable
> > > > to track this) but because there may be more than one
> > > > translator so any given translator may not see all packets.
> > > > So for stateless translation when the translator has a < 1280
> > > > packet with no fragment header we don't know whether this is
> > > > because PMTUD was succesful and the packet size fits in the
> > > > PMTU, or the IPv6 host ignored the < 1280 too big message and
> > > > is omitting the fragment header in violation of the relevant
> > > > RFCs. In order to be compatible with the latter the only
> > > > thing we can do is set DF to 0.
> > > >
> > > > (I just realize that we don't know what happens when for
> > > > instance the PMTU is 1000 and the IPv6 host wants to send a
> > > > 1100-byte packet: does it include a fragment header or not?)
> > > >
> > > > Note that for part B, if there _is_ a fragment header, that
> > > > will also trigger the translator to set DF to 0. So in the
> > > > case where the IPv6 hosts are well behaved there is no change
> > > > to either parts A or B.
> > >
> > > So, I believe we are in agreement:  IPv6 packets less than
> > > 1280 need to be translated to IPv4 and sent with DF=3D0.
> > >
> > > > In the stateful case we know all packets flow through the
> > > > same translator so we get to track the IPv4 PMTU so when
> > > > there is an IPv6 packet that needs to be translated we know
> > > > whether it's bigger or smaller than the PMTU so we can send
> > > > packets that are bigger with DF=3D1 and packets that are
> > > > smaller with DF=3D0 and if we are to, also immediately fragment
> > > > them. However, there is no advantage to doing this extra work
> > > > because even if we get to set DF=3D1 on some packets that are
> > > > smaller than the PMTU that only lets us discover a reduction
> > > > in the PMTU, but that discovery doesn't buy us anything
> > > > because the IPv6 host isn't going to reduce its packet size.
> > >
> > > I agree the IPv6 host won't reduce its packet size below
> > > 1280.  But the IPv6 host becomes aware that the path MTU
> > > is smaller than 1280.  I don't know if the IPv6 host finds
> > > that useful/valuable to know the path MTU is less than the
> > > IPv6 minimum MTU.
> > >
> > > > Fragmenting at the translator also doesn't buy the translator
> > > > anything and it may even get the packet blocked or create
> > > > more work if there's a firewall with a > 1280 MTU before the
> > > > path hits the < 1280 MTU which would need to reassemble the
> > > > packet to observe the port numbers. And it could be an attack
> > > > vector: attackers could send too bigs with tiny MTUs to make
> > > > the translator work harder.
> > > >
> > > > > Certainly there was some
> > > > > perceived value in the IPv6 knowing its packets are being
> > > > > fragmented.
> > > >
> > > > I don't think so. Even if the application somehow learns this
> > > > information, what is it supposed to do then?
> > >
> > > Don't know.  It is obviously easier for the 6/4 translator to
> > > simply fragment the packet (or translate and send with DF=3D0) withou=
t
> > > informing the IPv6 host, but there is long-standing text in both
> > > RFC2460 and its predecessor (RFC1883) that says to send back
> > > ICMPv6 PTB and the IPv6 host is then supposed to send packets
> > > with the fragmentation header.
> > >
> > > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > > >
> > > > > But there isn't anything prohibiting PMTUD for UDP.
> > > >
> > > > With sufficient thrust pigs fly just fine...
> > > >
> > > > Generally, it's not easy for UDP applications to limit their
> > > > packet sizes. So the protocol would have to support changing
> > > > the packet size on the fly and then the application would
> > > > have to react to too big messages.
> > >
> > > draft-petithuguenin-behave-stun-pmtud does not rely on
> > > ICMP packet too big messages.
> > >
> > > > Not impossible, but I've never seen it happen.
> > >
> > > Me, neither.  I'm just trying to temper the "only TCP does
> > > PMTUD", because UDP can do PMTUD.  And of course there is value
> > > in sending the largest packets possible.
> > >
> > > > But if BitTorrent goes to UDP it's
> > > > likely they'll put this in in some way.
> > >
> > > As of version 2.x, the most popular BitTorrent client on
> > > Windows (uTorrent) has implemented uTP, for whatever that's
> > > worth.  I don't know if they're doing PMTUD, though.  Beta
> > > versions of uTorrent are available for OSX, too, and I expect
> > > they will soon support uTP (if they aren't already).
> > >
> > > > > I tend to think, though, we don't want to figure this out
> > > > > for stateful translators at this point in time.  If it is
> > > > > found useful/necessary, it can be specified later.
> > > >
> > > > Right.=3D
> > >
> > > -d
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From dwing@cisco.com  Mon Feb  8 17:15:23 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 2839C28C0D8 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 17:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, 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 hL0y6-TyTEpV for <behave@core3.amsl.com>; Mon,  8 Feb 2010 17:15:21 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 9CBC83A6F89 for <behave@ietf.org>; Mon,  8 Feb 2010 17:15:21 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0GALFFcEurRN+J/2dsb2JhbACHeoEStm+XZYI7B4ISBI5H
X-IronPort-AV: E=Sophos;i="4.49,433,1262563200"; d="scan'208";a="238683579"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-2.cisco.com with ESMTP; 09 Feb 2010 01:16:26 +0000
Received: from dwingwxp01 (dhcp-128-107-166-142.cisco.com [128.107.166.142]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o191GQmQ021413; Tue, 9 Feb 2010 01:16:26 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com>
Date: Mon, 8 Feb 2010 17:16:26 -0800
Message-ID: <035601caa925$800f2240$c4f0200a@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
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com>
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cAABmZlwAABjT3A=
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 01:15:23 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Templin, Fred L
> Sent: Monday, February 08, 2010 5:11 PM
> To: Dan Wing; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> Dan,
> 
> > -----Original Message-----
> > From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > Sent: Monday, February 08, 2010 4:24 PM
> > To: Templin, Fred L; 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > Sent: Monday, February 08, 2010 4:02 PM
> > > To: Dan Wing; 'Iljitsch van Beijnum'
> > > Cc: behave@ietf.org
> > > Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > > The concern with setting DF=0 on the IPv4 side for packets
> > > that are 1280 or smaller on the IPv6 side is the possibility
> > > for RFC4963 data corruption if we let it run at line rate.
> > 
> > At high speed with the same source/destination addresses, and when
> > fragmentation on the IPv4 network occurs.  That is, sending 
> lots of packets
> > with DF=0 does not, by itself, cause a problem even if they 
> are fragmented on
> > the same link -- so long as they have different source or different
> > destination addresses.  I agree we should make a note of that.
> 
> Yes, the concern is for same src,dst operating at line 
> rate. IPv6 apps assume that there is no possibility for
> fragmentation in the network, hence they may not be as
> shy as IPv4 apps when it comes to sending large packets
> at high data rates. Having the translator set DF=0 can
> break that assumption.

There are three approaches discussed in new text in
http://tools.ietf.org/html/draft-ietf-behave-v6v4-xlate-08#page-18,
which only set DF=0 for "small packets" (packets that were
less than 1280 on the IPv6 side).

I don't think that eliminates your concern, though.

> > Is there another approach that should be considered to 
> > avoid that concern?
> 
> I still believe placement of the translator matters.
> Placing the translator closer to the IPv4 host
> reduces the portion of the path that is exposed to
> IPv4 hops. This is true whether the DF=0 or DF=1
> approach is used.

Agreed.

However, that isn't always possible.  For example,
someone operating an IPv6-only network will have to
place their IPv6/IPv4 translator at their network
border.

But perhaps some text could be added to 
draft-ietf-behave-v6v4-xlate which highlighted
this recommendation to place the translator as
close to the IPv4 host as possible.  Or, similarly,
to ensure the IPv4 network has an MTU greater than
1280 (minus whatever the IPv6/IPv4 header differences
are).

-d


> Fred
> fred.l.templin@boeing.com
> 
> > > There are certainly plenty of websites on the IPv4 Internet
> > > that set DF=0 on every packet they send, and many even use
> > > packet sizes larger than 1280. But, how many of them send
> > > large packets at line rate?
> > 
> > Content delivery networks?
> > 
> > -d
> > 
> > 
> > > Fred
> > > fred.l.templin@boeing.com
> > >
> > > > -----Original Message-----
> > > > From: behave-bounces@ietf.org
> > > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > > Sent: Monday, February 08, 2010 3:29 PM
> > > > To: 'Iljitsch van Beijnum'
> > > > Cc: behave@ietf.org
> > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > > > Sent: Monday, February 08, 2010 3:02 PM
> > > > > To: Dan Wing
> > > > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 
> byte packets
> > > > >
> > > > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > > > >
> > > > > >> So essentially this means doing more work (keeping PMTUD
> > > > > >> state for the IPv4 path) in order to do even more 
> work later
> > > > > >> (fragment). Not sure how that makes sense...
> > > > >
> > > > > > Yes, it means the translator is doing the effort of 
> fragmenting
> > > > > > rather than the router immediately in front of the small-MTU
> > > > > > link.  However, by doing it this way, we can 
> maintain end-to-end
> > > > > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > > > > > packets with the fragmentation header.
> > > > >
> > > > > No, the two issues are orthogonal.
> > > > >
> > > > > At some point, an IPv6 host sends a packet that is larger
> > > > > than the IPv4 PMTU. A router sends back a too big message.
> > > > > Issue A is how to handle this too big message. Issue B is
> > > > > what happens to packets that the IPv6 host subsequently sends.
> > > >
> > > > A stateless translator cannot identify 'subsequent' packets,
> > > > because it doesn't remember previous state.
> > > >
> > > > > I think there is agreement that A should be handled by simply
> > > > > translating the IPv4 too big too IPv6 and adjusting it as per
> > > > > the header size differences, but otherwise let it through
> > > > > transparently. (I once argued for rewriting it to 
> 1280, though.)
> > > > >
> > > > > Nothing has changed here.
> > > > >
> > > > > But now for part B. A stateless translator can't monitor the
> > > > > IPv4 PMTU. Not because it's stateful (we're talking per
> > > > > destination state, not per session state, it would be doable
> > > > > to track this) but because there may be more than one
> > > > > translator so any given translator may not see all packets.
> > > > > So for stateless translation when the translator has a < 1280
> > > > > packet with no fragment header we don't know whether this is
> > > > > because PMTUD was succesful and the packet size fits in the
> > > > > PMTU, or the IPv6 host ignored the < 1280 too big message and
> > > > > is omitting the fragment header in violation of the relevant
> > > > > RFCs. In order to be compatible with the latter the only
> > > > > thing we can do is set DF to 0.
> > > > >
> > > > > (I just realize that we don't know what happens when for
> > > > > instance the PMTU is 1000 and the IPv6 host wants to send a
> > > > > 1100-byte packet: does it include a fragment header or not?)
> > > > >
> > > > > Note that for part B, if there _is_ a fragment header, that
> > > > > will also trigger the translator to set DF to 0. So in the
> > > > > case where the IPv6 hosts are well behaved there is no change
> > > > > to either parts A or B.
> > > >
> > > > So, I believe we are in agreement:  IPv6 packets less than
> > > > 1280 need to be translated to IPv4 and sent with DF=0.
> > > >
> > > > > In the stateful case we know all packets flow through the
> > > > > same translator so we get to track the IPv4 PMTU so when
> > > > > there is an IPv6 packet that needs to be translated we know
> > > > > whether it's bigger or smaller than the PMTU so we can send
> > > > > packets that are bigger with DF=1 and packets that are
> > > > > smaller with DF=0 and if we are to, also immediately fragment
> > > > > them. However, there is no advantage to doing this extra work
> > > > > because even if we get to set DF=1 on some packets that are
> > > > > smaller than the PMTU that only lets us discover a reduction
> > > > > in the PMTU, but that discovery doesn't buy us anything
> > > > > because the IPv6 host isn't going to reduce its packet size.
> > > >
> > > > I agree the IPv6 host won't reduce its packet size below
> > > > 1280.  But the IPv6 host becomes aware that the path MTU
> > > > is smaller than 1280.  I don't know if the IPv6 host finds
> > > > that useful/valuable to know the path MTU is less than the
> > > > IPv6 minimum MTU.
> > > >
> > > > > Fragmenting at the translator also doesn't buy the translator
> > > > > anything and it may even get the packet blocked or create
> > > > > more work if there's a firewall with a > 1280 MTU before the
> > > > > path hits the < 1280 MTU which would need to reassemble the
> > > > > packet to observe the port numbers. And it could be an attack
> > > > > vector: attackers could send too bigs with tiny MTUs to make
> > > > > the translator work harder.
> > > > >
> > > > > > Certainly there was some
> > > > > > perceived value in the IPv6 knowing its packets are being
> > > > > > fragmented.
> > > > >
> > > > > I don't think so. Even if the application somehow learns this
> > > > > information, what is it supposed to do then?
> > > >
> > > > Don't know.  It is obviously easier for the 6/4 translator to
> > > > simply fragment the packet (or translate and send with 
> DF=0) without
> > > > informing the IPv6 host, but there is long-standing text in both
> > > > RFC2460 and its predecessor (RFC1883) that says to send back
> > > > ICMPv6 PTB and the IPv6 host is then supposed to send packets
> > > > with the fragmentation header.
> > > >
> > > > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > > > >
> > > > > > But there isn't anything prohibiting PMTUD for UDP.
> > > > >
> > > > > With sufficient thrust pigs fly just fine...
> > > > >
> > > > > Generally, it's not easy for UDP applications to limit their
> > > > > packet sizes. So the protocol would have to support changing
> > > > > the packet size on the fly and then the application would
> > > > > have to react to too big messages.
> > > >
> > > > draft-petithuguenin-behave-stun-pmtud does not rely on
> > > > ICMP packet too big messages.
> > > >
> > > > > Not impossible, but I've never seen it happen.
> > > >
> > > > Me, neither.  I'm just trying to temper the "only TCP does
> > > > PMTUD", because UDP can do PMTUD.  And of course there is value
> > > > in sending the largest packets possible.
> > > >
> > > > > But if BitTorrent goes to UDP it's
> > > > > likely they'll put this in in some way.
> > > >
> > > > As of version 2.x, the most popular BitTorrent client on
> > > > Windows (uTorrent) has implemented uTP, for whatever that's
> > > > worth.  I don't know if they're doing PMTUD, though.  Beta
> > > > versions of uTorrent are available for OSX, too, and I expect
> > > > they will soon support uTP (if they aren't already).
> > > >
> > > > > > I tend to think, though, we don't want to figure this out
> > > > > > for stateful translators at this point in time.  If it is
> > > > > > found useful/necessary, it can be specified later.
> > > > >
> > > > > Right.=
> > > >
> > > > -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
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From rvaithia@cisco.com  Mon Feb  8 19:03:25 2010
Return-Path: <rvaithia@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 443843A6B3D for <behave@core3.amsl.com>; Mon,  8 Feb 2010 19:03:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 kqiG7neIK6Hk for <behave@core3.amsl.com>; Mon,  8 Feb 2010 19:03:23 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id A9E403A6916 for <behave@ietf.org>; Mon,  8 Feb 2010 19:03:23 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEADZfcEurRN+J/2dsb2JhbAC/WZd5gjsHghIEjkc
X-IronPort-AV: E=Sophos;i="4.49,433,1262563200";  d="scan'208,223";a="480270179"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-6.cisco.com with ESMTP; 09 Feb 2010 03:04:28 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1934SFi014214; Tue, 9 Feb 2010 03:04:28 GMT
Received: from xmb-sjc-231.amer.cisco.com ([128.107.191.73]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 8 Feb 2010 19:04:28 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Feb 2010 19:04:26 -0800
Message-ID: <A0988C2F192F124FAFE3D70264C045870ADE5BC2@xmb-sjc-231.amer.cisco.com>
In-Reply-To: <032d01caa91e$343c71d0$c4f0200a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cAAB3dhw
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com> <032d01caa91e$343c71d0$c4f0200a@cisco.com>
From: "Ramji Vaithianathan (rvaithia)" <rvaithia@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 09 Feb 2010 03:04:28.0412 (UTC) FILETIME=[97D3E3C0:01CAA934]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 03:03:25 -0000

>From my understanding, this will be a problem only if the=20
  1. MTU on some link on IPv4 side is less than 1280
  2. We have high speed traffic less than 1280 bytes but greater than
the above MTU value.

Generally most links on intermediate routers are 1500 or greater. =20

So this may not be a common case, unless there is a link attached to an
end host is of smaller MTU (< 1280) and can take in high traffic as well
in the range MTU_value .. 1280.=20

Regards,

Ramji
-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of Dan Wing (dwing)
Sent: Tuesday, February 09, 2010 5:54 AM
To: 'Templin, Fred L'; 'Iljitsch van Beijnum'
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets


=20

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Monday, February 08, 2010 4:02 PM
> To: Dan Wing; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
> The concern with setting DF=3D0 on the IPv4 side for packets that are=20
> 1280 or smaller on the IPv6 side is the possibility for RFC4963 data=20
> corruption if we let it run at line rate.

At high speed with the same source/destination addresses, and when
fragmentation on the IPv4 network occurs.  That is, sending lots of
packets with DF=3D0 does not, by itself, cause a problem even if they =
are
fragmented on the same link -- so long as they have different source or
different destination addresses.  I agree we should make a note of that.


Is there another approach that should be considered to avoid that
concern?

> There are certainly plenty of websites on the IPv4 Internet that set=20
> DF=3D0 on every packet they send, and many even use packet sizes =
larger=20
> than 1280. But, how many of them send large packets at line rate?

Content delivery networks?

-d


> Fred
> fred.l.templin@boeing.com
>=20
> > -----Original Message-----
> > From: behave-bounces@ietf.org
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > Sent: Monday, February 08, 2010 3:29 PM
> > To: 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > Sent: Monday, February 08, 2010 3:02 PM
> > > To: Dan Wing
> > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > >
> > > >> So essentially this means doing more work (keeping PMTUD state=20
> > > >> for the IPv4 path) in order to do even more work later=20
> > > >> (fragment). Not sure how that makes sense...
> > >
> > > > Yes, it means the translator is doing the effort of fragmenting=20
> > > > rather than the router immediately in front of the small-MTU=20
> > > > link.  However, by doing it this way, we can maintain end-to-end

> > > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send=20
> > > > packets with the fragmentation header.
> > >
> > > No, the two issues are orthogonal.
> > >
> > > At some point, an IPv6 host sends a packet that is larger than the

> > > IPv4 PMTU. A router sends back a too big message.
> > > Issue A is how to handle this too big message. Issue B is what=20
> > > happens to packets that the IPv6 host subsequently sends.
> >=20
> > A stateless translator cannot identify 'subsequent' packets, because

> > it doesn't remember previous state.
> >=20
> > > I think there is agreement that A should be handled by simply=20
> > > translating the IPv4 too big too IPv6 and adjusting it as per the=20
> > > header size differences, but otherwise let it through=20
> > > transparently. (I once argued for rewriting it to 1280, though.)
> > >
> > > Nothing has changed here.
> > >
> > > But now for part B. A stateless translator can't monitor the
> > > IPv4 PMTU. Not because it's stateful (we're talking per=20
> > > destination state, not per session state, it would be doable to=20
> > > track this) but because there may be more than one translator so=20
> > > any given translator may not see all packets.
> > > So for stateless translation when the translator has a < 1280=20
> > > packet with no fragment header we don't know whether this is=20
> > > because PMTUD was succesful and the packet size fits in the PMTU,=20
> > > or the IPv6 host ignored the < 1280 too big message and is=20
> > > omitting the fragment header in violation of the relevant RFCs. In

> > > order to be compatible with the latter the only thing we can do is

> > > set DF to 0.
> > >
> > > (I just realize that we don't know what happens when for instance=20
> > > the PMTU is 1000 and the IPv6 host wants to send a 1100-byte=20
> > > packet: does it include a fragment header or not?)
> > >
> > > Note that for part B, if there _is_ a fragment header, that will=20
> > > also trigger the translator to set DF to 0. So in the case where=20
> > > the IPv6 hosts are well behaved there is no change to either parts

> > > A or B.
> >=20
> > So, I believe we are in agreement:  IPv6 packets less than 1280 need

> > to be translated to IPv4 and sent with DF=3D0.
> >=20
> > > In the stateful case we know all packets flow through the same=20
> > > translator so we get to track the IPv4 PMTU so when there is an=20
> > > IPv6 packet that needs to be translated we know whether it's=20
> > > bigger or smaller than the PMTU so we can send packets that are=20
> > > bigger with DF=3D1 and packets that are smaller with DF=3D0 and if =
we=20
> > > are to, also immediately fragment them. However, there is no=20
> > > advantage to doing this extra work because even if we get to set=20
> > > DF=3D1 on some packets that are smaller than the PMTU that only =
lets

> > > us discover a reduction in the PMTU, but that discovery doesn't=20
> > > buy us anything because the IPv6 host isn't going to reduce its=20
> > > packet size.
> >=20
> > I agree the IPv6 host won't reduce its packet size below 1280.  But=20
> > the IPv6 host becomes aware that the path MTU is smaller than 1280.

> > I don't know if the IPv6 host finds that useful/valuable to know the

> > path MTU is less than the
> > IPv6 minimum MTU.
> >=20
> > > Fragmenting at the translator also doesn't buy the translator=20
> > > anything and it may even get the packet blocked or create more=20
> > > work if there's a firewall with a > 1280 MTU before the path hits=20
> > > the < 1280 MTU which would need to reassemble the packet to=20
> > > observe the port numbers. And it could be an attack
> > > vector: attackers could send too bigs with tiny MTUs to make the=20
> > > translator work harder.
> > >
> > > > Certainly there was some
> > > > perceived value in the IPv6 knowing its packets are being=20
> > > > fragmented.
> > >
> > > I don't think so. Even if the application somehow learns this=20
> > > information, what is it supposed to do then?
> >=20
> > Don't know.  It is obviously easier for the 6/4 translator to simply

> > fragment the packet (or translate and send with DF=3D0) without=20
> > informing the IPv6 host, but there is long-standing text in both=20
> > RFC2460 and its predecessor (RFC1883) that says to send back
> > ICMPv6 PTB and the IPv6 host is then supposed to send packets with=20
> > the fragmentation header.
> >=20
> > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > >
> > > > But there isn't anything prohibiting PMTUD for UDP.
> > >
> > > With sufficient thrust pigs fly just fine...
> > >
> > > Generally, it's not easy for UDP applications to limit their=20
> > > packet sizes. So the protocol would have to support changing the=20
> > > packet size on the fly and then the application would have to=20
> > > react to too big messages.
> >=20
> > draft-petithuguenin-behave-stun-pmtud does not rely on ICMP packet=20
> > too big messages.
> >=20
> > > Not impossible, but I've never seen it happen.
> >=20
> > Me, neither.  I'm just trying to temper the "only TCP does PMTUD",=20
> > because UDP can do PMTUD.  And of course there is value in sending=20
> > the largest packets possible.
> >=20
> > > But if BitTorrent goes to UDP it's likely they'll put this in in=20
> > > some way.
> >=20
> > As of version 2.x, the most popular BitTorrent client on Windows=20
> > (uTorrent) has implemented uTP, for whatever that's worth.  I don't=20
> > know if they're doing PMTUD, though.  Beta versions of uTorrent are=20
> > available for OSX, too, and I expect they will soon support uTP (if=20
> > they aren't already).
> >=20
> > > > I tend to think, though, we don't want to figure this out for=20
> > > > stateful translators at this point in time.  If it is found=20
> > > > useful/necessary, it can be specified later.
> > >
> > > Right.=3D
> >=20
> > -d
> >=20
> > _______________________________________________
> > 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 iljitsch@muada.com  Mon Feb  8 23:28:25 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 C468F3A7547 for <behave@core3.amsl.com>; Mon,  8 Feb 2010 23:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 88MhEHm4G2Jb for <behave@core3.amsl.com>; Mon,  8 Feb 2010 23:28:25 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id E3BBD3A69F4 for <behave@ietf.org>; Mon,  8 Feb 2010 23:28:24 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o197Rjk4036008 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 08:27:46 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 08:28:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF1E263A-C84C-49FD-AEB2-BCA361E19D60@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com> <02f101caa916$712d0170$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 07:28:25 -0000

On 9 feb 2010, at 1:01, Templin, Fred L wrote:

> The concern with setting DF=3D0 on the IPv4 side for packets
> that are 1280 or smaller on the IPv6 side is the possibility
> for RFC4963 data corruption if we let it run at line rate.

But how can this be avoided by the translator?

In theory if the IPv6 host sees a < 1280 too big it could deduce that =
its packets are going to be translated to IPv4 with DF=3D0 and then slow =
down to avoid wrapping the ID during a packet lifetime, but I don't see =
that happening...

If an IPv4 network is stupid enough to use such a small MTU then =
incorrect reassemly of fragments is a risk they are apparently willing =
to run.

But again, note that few fragments will happen because the TCP MSS will =
usually make the IPv6 host send packets that don't require =
fragmentation. The only two applications that I know of that send high =
rates of non-TCP packets are RTSP video streaming, which I assume won't =
be done much from an IPv6 client towards and IPv4 server, and tunneling, =
which I assume will also be rare across a NAT64. Maybe in the future =
there will also be UDP BitTorrent, but BitTorrent usually doesn't send =
too much traffic to any given destination and it uses application layer =
checksums.=

From remi.despres@free.fr  Tue Feb  9 01:57:53 2010
Return-Path: <remi.despres@free.fr>
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 1A0C63A6EEB; Tue,  9 Feb 2010 01:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 ZEP2jErfk6TS; Tue,  9 Feb 2010 01:57:52 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 9478D3A6B45; Tue,  9 Feb 2010 01:57:49 -0800 (PST)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 671ECE0801C; Tue,  9 Feb 2010 10:58:49 +0100 (CET)
Received: from [192.168.0.13] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id DE2F6E08207; Tue,  9 Feb 2010 10:58:46 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 10:58:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com> <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com> <E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "softwires@ietf.org" <softwires@ietf.org>, Behave WG <behave@ietf.org>, Ed Jankiewicz <edward.jankiewicz@sri.com>, Dave Dolson <ddolson@sandvine.com>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 09 Feb 2010 09:57:53 -0000

Le 8 f=E9vr. 2010 =E0 22:08, Templin, Fred L a =E9crit :

> Also, there seems to be some evidence that ICMPv6 PTB
> messages are being dropped in the network.

In IPv6, I hope it will be possible to agree at least that PTB messages =
SHOULD be forwarded (if not MUST).
Reasons to not agree should IMHO be seriously documented.

> ... for DF=3D1 packets the tunnel
> ingress MUST send an ICMP PTB when the packet is larger
> than a fixed minimum tunnel MTU and also too large to
> traverse the tunnel in a single piece. For packets that
> are no larger than the fixed minimum tunnel MTU, the
> tunnel ingress SHOULD use tunnel fragmentation (i.e.,
> SEAL segmentation and reassembly). Presumably, the tunnel
> ingress would choose a fixed minimum tunnel MTU that is
> large enough so that source hosts will not see excessive
> data loss and retransmissions due to path MTU discovery
> interactions.
>=20
> For many/most deployments, a fixed minimum tunnel MTU of
> 1500 bytes would seem advisable.

In my understanding, we can keep the current IPv6 value of 1280 as the =
minimum that has to traverse ALL tunnels, and note that if a tunnel has =
an internal mechanism to fragment at entrance and reassemble at exit =
(e.g. SEAL), the tunnel advertised MTU can become independent from that =
of the traversed infrastructure.=20

Thoughts?

Cheers,
RD=

From Fred.L.Templin@boeing.com  Tue Feb  9 07:47:33 2010
Return-Path: <Fred.L.Templin@boeing.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 2152E28C1F8; Tue,  9 Feb 2010 07:47:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level: 
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[AWL=0.003,  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 qZEELlvrs77c; Tue,  9 Feb 2010 07:47:32 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 191B728C12F; Tue,  9 Feb 2010 07:47:30 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19FmXtJ015547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 09:48:34 -0600 (CST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19FmXUD008229; Tue, 9 Feb 2010 07:48:33 -0800 (PST)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19FmXe3008213 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 07:48:33 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Tue, 9 Feb 2010 07:48:32 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tero Kivinen <kivinen@iki.fi>
Date: Tue, 9 Feb 2010 07:48:31 -0800
Thread-Topic: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
Thread-Index: AcqpkJvbSP/WJrEQSNOEGivF/qYUbwADkr9w
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A649510380FF@XCH-NW-01V.nw.nos.boeing.com>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A649510 37BF6@XCH-NW-01V.nw.nos.boeing.com><F489AB573A749146B33461ECE080913A0D7DEE3 6@EXCHANGE-1.sandvine.com><E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com> <19313.27410.93467.295717@fireball.kivinen.iki.fi>
In-Reply-To: <19313.27410.93467.295717@fireball.kivinen.iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, Behave WG <behave@ietf.org>, Ed Jankiewicz <edward.jankiewicz@sri.com>, Dave Dolson <ddolson@sandvine.com>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 09 Feb 2010 15:47:33 -0000

Tero,

> -----Original Message-----
> From: Tero Kivinen [mailto:kivinen@iki.fi]
> Sent: Tuesday, February 09, 2010 6:03 AM
> To: Templin, Fred L
> Cc: Dave Dolson; Ed Jankiewicz; Behave WG; softwires@ietf.org
> Subject: Re: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
>=20
> Templin, Fred L writes:
> > > I believe this is referring to mapping of ICMP "too big" messages. Wh=
en
> > > a tunnel end-point receives a "too big" message, it would have to map
> > > the message to an ICMP message for the original host. I believe this
> > > could be done in a stateless manner using the packet quoted in the
> > > message. (RFC2463 says the "too big" message will include "As much of
> > > invoking packet as will fit without the ICMPv6 packet exceeding the
> > > minimum IPv6 MTU")
> >
> > But, if the packet-in-error encapsulated in the ICMP
> > PTB message is encrypted and not complete (i.e., only
> > the leading 1200 or so bytes of the encrypted packet
> > are included), how will the tunnel ingress know how to
> > decrypt it in order to do the stateless translation?
>=20
> If we are talking about IPsec, then that ICMP packet will have the SPI
> of the packet, so the gateway can find the related IPsec SA for the
> the packet which caused the PTB message to be sent. After that it
> simply stores the maximum path MTU it got from the ICMP message to the
> IPsec SA.

That would be a stateful means for determining path MTU.
I was responding to the assertion that a stateless method
was possible.

Fred
fred.l.templin@boeing.com
=20
> When the next packet comes through which is bigger than what the MTU
> stored for the SA (where the MTU is already modified accordingly to
> match the overhead of IPsec headers), it will directly send PTB
> message back to the original sender of the packet.
>=20
> I.e. it will dynamically find out the PMTU for each IPsec SA (taking
> the overhead in to account, as it does know the overhead), and then
> send PTB messages if packet is bigger than that.
>=20
> See section 8.2.1 of RFC4301:
> ----------------------------------------------------------------------
> 8.2.1.  Propagation of PMTU
>=20
>    When an IPsec implementation receives an unauthenticated PMTU
>    message, and it is configured to process (vs. ignore) such messages,
>    it maps the message to the SA to which it corresponds.  This mapping
>    is effected by extracting the header information from the payload of
>    the PMTU message and applying the procedure described in Section 5.2.
>    The PMTU determined by this message is used to update the SAD PMTU
>    field, taking into account the size of the AH or ESP header that will
>    be applied, any crypto synchronization data, and the overhead imposed
>    by an additional IP header, in the case of a tunnel mode SA.
>=20
>    In a native host implementation, it is possible to maintain PMTU data
>    at the same granularity as for unprotected communication, so there is
>    no loss of functionality.  Signaling of the PMTU information is
>    internal to the host.  For all other IPsec implementation options,
>    the PMTU data must be propagated via a synthesized ICMP PMTU.  In
>    these cases, the IPsec implementation SHOULD wait for outbound
>    traffic to be mapped to the SAD entry.  When such traffic arrives, if
>    the traffic would exceed the updated PMTU value the traffic MUST be
>    handled as follows:
>=20
>        Case 1: Original (cleartext) packet is IPv4 and has the DF
>                bit set.  The implementation SHOULD discard the packet
>                and send a PMTU ICMP message.
>=20
>        Case 2: Original (cleartext) packet is IPv4 and has the DF
>                bit clear.  The implementation SHOULD fragment (before or
>                after encryption per its configuration) and then forward
>                the fragments.  It SHOULD NOT send a PMTU ICMP message.
>=20
>        Case 3: Original (cleartext) packet is IPv6.  The implementation
>                SHOULD discard the packet and send a PMTU ICMP message.
> --
> kivinen@iki.fi

From Fred.L.Templin@boeing.com  Tue Feb  9 07:50:45 2010
Return-Path: <Fred.L.Templin@boeing.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 AA75628C207 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 07:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level: 
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[AWL=0.003,  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 opTffMR3ckQ2 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 07:50:44 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 1F26F3A708D for <behave@ietf.org>; Tue,  9 Feb 2010 07:50:44 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19FpTFl017544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2010 09:51:29 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19FpTMb010372; Tue, 9 Feb 2010 09:51:29 -0600 (CST)
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19FpSgR010360 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 09:51:29 -0600 (CST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-08.nw.nos.boeing.com ([130.247.25.112]) with mapi; Tue, 9 Feb 2010 07:51:28 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Ramji Vaithianathan (rvaithia)" <rvaithia@cisco.com>, "Dan Wing (dwing)" <dwing@cisco.com>, Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 9 Feb 2010 07:51:27 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cAAB3dhwAB7Cu4A=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951038105@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com> <032d01caa91e$343c71d0$c4f0200a@cisco.com> <A0988C2F192F124FAFE3D70264C045870ADE5BC2@xmb-sjc-231.amer.cisco.com>
In-Reply-To: <A0988C2F192F124FAFE3D70264C045870ADE5BC2@xmb-sjc-231.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 15:50:45 -0000

Ramji,

> -----Original Message-----
> From: Ramji Vaithianathan (rvaithia) [mailto:rvaithia@cisco.com]
> Sent: Monday, February 08, 2010 7:04 PM
> To: Dan Wing (dwing); Templin, Fred L; Iljitsch van Beijnum
> Cc: behave@ietf.org
> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
> From my understanding, this will be a problem only if the
>   1. MTU on some link on IPv4 side is less than 1280
>   2. We have high speed traffic less than 1280 bytes but greater than
> the above MTU value.
>=20
> Generally most links on intermediate routers are 1500 or greater.

I think it is reasonable to assume that the vast
majority of intermediate routers configure an MTU
of 1500 or greater. Where there might be a concern
for links with smaller MTUs is within end sites.

> So this may not be a common case, unless there is a link attached to an
> end host is of smaller MTU (< 1280) and can take in high traffic as well
> in the range MTU_value .. 1280.

Right.

Fred
fred.l.templin@boeing.com
=20
> Regards,
>=20
> Ramji
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Dan Wing (dwing)
> Sent: Tuesday, February 09, 2010 5:54 AM
> To: 'Templin, Fred L'; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > Sent: Monday, February 08, 2010 4:02 PM
> > To: Dan Wing; 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> >
> > The concern with setting DF=3D0 on the IPv4 side for packets that are
> > 1280 or smaller on the IPv6 side is the possibility for RFC4963 data
> > corruption if we let it run at line rate.
>=20
> At high speed with the same source/destination addresses, and when
> fragmentation on the IPv4 network occurs.  That is, sending lots of
> packets with DF=3D0 does not, by itself, cause a problem even if they are
> fragmented on the same link -- so long as they have different source or
> different destination addresses.  I agree we should make a note of that.
>=20
>=20
> Is there another approach that should be considered to avoid that
> concern?
>=20
> > There are certainly plenty of websites on the IPv4 Internet that set
> > DF=3D0 on every packet they send, and many even use packet sizes larger
> > than 1280. But, how many of them send large packets at line rate?
>=20
> Content delivery networks?
>=20
> -d
>=20
>=20
> > Fred
> > fred.l.templin@boeing.com
> >
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > Sent: Monday, February 08, 2010 3:29 PM
> > > To: 'Iljitsch van Beijnum'
> > > Cc: behave@ietf.org
> > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > > Sent: Monday, February 08, 2010 3:02 PM
> > > > To: Dan Wing
> > > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > > >
> > > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > > >
> > > > >> So essentially this means doing more work (keeping PMTUD state
> > > > >> for the IPv4 path) in order to do even more work later
> > > > >> (fragment). Not sure how that makes sense...
> > > >
> > > > > Yes, it means the translator is doing the effort of fragmenting
> > > > > rather than the router immediately in front of the small-MTU
> > > > > link.  However, by doing it this way, we can maintain end-to-end
>=20
> > > > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > > > > packets with the fragmentation header.
> > > >
> > > > No, the two issues are orthogonal.
> > > >
> > > > At some point, an IPv6 host sends a packet that is larger than the
>=20
> > > > IPv4 PMTU. A router sends back a too big message.
> > > > Issue A is how to handle this too big message. Issue B is what
> > > > happens to packets that the IPv6 host subsequently sends.
> > >
> > > A stateless translator cannot identify 'subsequent' packets, because
>=20
> > > it doesn't remember previous state.
> > >
> > > > I think there is agreement that A should be handled by simply
> > > > translating the IPv4 too big too IPv6 and adjusting it as per the
> > > > header size differences, but otherwise let it through
> > > > transparently. (I once argued for rewriting it to 1280, though.)
> > > >
> > > > Nothing has changed here.
> > > >
> > > > But now for part B. A stateless translator can't monitor the
> > > > IPv4 PMTU. Not because it's stateful (we're talking per
> > > > destination state, not per session state, it would be doable to
> > > > track this) but because there may be more than one translator so
> > > > any given translator may not see all packets.
> > > > So for stateless translation when the translator has a < 1280
> > > > packet with no fragment header we don't know whether this is
> > > > because PMTUD was succesful and the packet size fits in the PMTU,
> > > > or the IPv6 host ignored the < 1280 too big message and is
> > > > omitting the fragment header in violation of the relevant RFCs. In
>=20
> > > > order to be compatible with the latter the only thing we can do is
>=20
> > > > set DF to 0.
> > > >
> > > > (I just realize that we don't know what happens when for instance
> > > > the PMTU is 1000 and the IPv6 host wants to send a 1100-byte
> > > > packet: does it include a fragment header or not?)
> > > >
> > > > Note that for part B, if there _is_ a fragment header, that will
> > > > also trigger the translator to set DF to 0. So in the case where
> > > > the IPv6 hosts are well behaved there is no change to either parts
>=20
> > > > A or B.
> > >
> > > So, I believe we are in agreement:  IPv6 packets less than 1280 need
>=20
> > > to be translated to IPv4 and sent with DF=3D0.
> > >
> > > > In the stateful case we know all packets flow through the same
> > > > translator so we get to track the IPv4 PMTU so when there is an
> > > > IPv6 packet that needs to be translated we know whether it's
> > > > bigger or smaller than the PMTU so we can send packets that are
> > > > bigger with DF=3D1 and packets that are smaller with DF=3D0 and if =
we
> > > > are to, also immediately fragment them. However, there is no
> > > > advantage to doing this extra work because even if we get to set
> > > > DF=3D1 on some packets that are smaller than the PMTU that only let=
s
>=20
> > > > us discover a reduction in the PMTU, but that discovery doesn't
> > > > buy us anything because the IPv6 host isn't going to reduce its
> > > > packet size.
> > >
> > > I agree the IPv6 host won't reduce its packet size below 1280.  But
> > > the IPv6 host becomes aware that the path MTU is smaller than 1280.
>=20
> > > I don't know if the IPv6 host finds that useful/valuable to know the
>=20
> > > path MTU is less than the
> > > IPv6 minimum MTU.
> > >
> > > > Fragmenting at the translator also doesn't buy the translator
> > > > anything and it may even get the packet blocked or create more
> > > > work if there's a firewall with a > 1280 MTU before the path hits
> > > > the < 1280 MTU which would need to reassemble the packet to
> > > > observe the port numbers. And it could be an attack
> > > > vector: attackers could send too bigs with tiny MTUs to make the
> > > > translator work harder.
> > > >
> > > > > Certainly there was some
> > > > > perceived value in the IPv6 knowing its packets are being
> > > > > fragmented.
> > > >
> > > > I don't think so. Even if the application somehow learns this
> > > > information, what is it supposed to do then?
> > >
> > > Don't know.  It is obviously easier for the 6/4 translator to simply
>=20
> > > fragment the packet (or translate and send with DF=3D0) without
> > > informing the IPv6 host, but there is long-standing text in both
> > > RFC2460 and its predecessor (RFC1883) that says to send back
> > > ICMPv6 PTB and the IPv6 host is then supposed to send packets with
> > > the fragmentation header.
> > >
> > > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > > >
> > > > > But there isn't anything prohibiting PMTUD for UDP.
> > > >
> > > > With sufficient thrust pigs fly just fine...
> > > >
> > > > Generally, it's not easy for UDP applications to limit their
> > > > packet sizes. So the protocol would have to support changing the
> > > > packet size on the fly and then the application would have to
> > > > react to too big messages.
> > >
> > > draft-petithuguenin-behave-stun-pmtud does not rely on ICMP packet
> > > too big messages.
> > >
> > > > Not impossible, but I've never seen it happen.
> > >
> > > Me, neither.  I'm just trying to temper the "only TCP does PMTUD",
> > > because UDP can do PMTUD.  And of course there is value in sending
> > > the largest packets possible.
> > >
> > > > But if BitTorrent goes to UDP it's likely they'll put this in in
> > > > some way.
> > >
> > > As of version 2.x, the most popular BitTorrent client on Windows
> > > (uTorrent) has implemented uTP, for whatever that's worth.  I don't
> > > know if they're doing PMTUD, though.  Beta versions of uTorrent are
> > > available for OSX, too, and I expect they will soon support uTP (if
> > > they aren't already).
> > >
> > > > > I tend to think, though, we don't want to figure this out for
> > > > > stateful translators at this point in time.  If it is found
> > > > > useful/necessary, it can be specified later.
> > > >
> > > > Right.=3D
> > >
> > > -d
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From Fred.L.Templin@boeing.com  Tue Feb  9 09:51:11 2010
Return-Path: <Fred.L.Templin@boeing.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 E273028C25A for <behave@core3.amsl.com>; Tue,  9 Feb 2010 09:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.296
X-Spam-Level: 
X-Spam-Status: No, score=-6.296 tagged_above=-999 required=5 tests=[AWL=-0.297, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, 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 Mf1TNxSM8kZ8 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 09:51:10 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 4609928C24E for <behave@ietf.org>; Tue,  9 Feb 2010 09:51:10 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19HpfsX023020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 09:51:41 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19HpeM5020696; Tue, 9 Feb 2010 09:51:40 -0800 (PST)
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19Hpe6r020682 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 09:51:40 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-08.nw.nos.boeing.com ([130.247.25.112]) with mapi; Tue, 9 Feb 2010 09:51:40 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Dan Wing <dwing@cisco.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Date: Tue, 9 Feb 2010 09:51:38 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cAABmZlwAABjT3AAId8FAA==
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boein g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com>
In-Reply-To: <035601caa925$800f2240$c4f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 17:51:12 -0000

Dan,

About the placement of the translator, in the IPv6->IPv4
direction the packet incurs a size reduction due to the
substitution of an IPv4 header in place of the IPv6 header.
In the IPv4->IPv6 direction, however, the size of the packet
is inflated. So, e.g., if the translator receives a 1500byte
IPv4 packet and has to translate it into a 1520byte IPv6
packet, there is a chance that it may be dropped due to a
link MTU restriction somewhere in the IPv6 network and an
ICMPv6 PTB sent back toward the translator. Presumably, the
translator would translate that into an ICMPv4 PTB message
that it forwards on to the IPv4 host.

If I have that right, there may be a concern for whether
the ICMPv4 PTB would be dropped in the IPv4 network before
it arrives at the IPv4 host. I ran some tests and found
that path MTU discovery in IPv4 seems to be problematic
for a substantial number of the top 1000 websites:

http://www.ietf.org/mail-archive/web/rrg/current/msg05907.html

This suggests to me that path MTU discovery in the IPv4
network "works" simply because it is rarely invoked. In
other words, the IPv4 network seems to be getting by
based on the good fortune that most links in the Internet
core configure an MTU of 1500 or larger. But, this state
of affairs may be disrupted if more and more translators
are used that cause IPv4 packets to be inflated in size
after they are translated into IPv6 packets.

So, if the translator were located at the site border of
the IPv4 host (i.e., rather than at the site border of
the IPv6 host) the bulk of the path would be over IPv6
instead of IPv4, hence the incidence of ICMPv4 filtering
would be isolated to the end site of the IPv4 host.

Has the translator deployment analysis taken IPv4 path
MTU-related black holing into consideration?

Fred
fred.l.templin@boeing.com =20

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Monday, February 08, 2010 5:16 PM
> To: Templin, Fred L; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
>=20
>=20
> > -----Original Message-----
> > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of Templin, Fred L
> > Sent: Monday, February 08, 2010 5:11 PM
> > To: Dan Wing; 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> >
> > Dan,
> >
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > Sent: Monday, February 08, 2010 4:24 PM
> > > To: Templin, Fred L; 'Iljitsch van Beijnum'
> > > Cc: behave@ietf.org
> > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > Sent: Monday, February 08, 2010 4:02 PM
> > > > To: Dan Wing; 'Iljitsch van Beijnum'
> > > > Cc: behave@ietf.org
> > > > Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > > >
> > > > The concern with setting DF=3D0 on the IPv4 side for packets
> > > > that are 1280 or smaller on the IPv6 side is the possibility
> > > > for RFC4963 data corruption if we let it run at line rate.
> > >
> > > At high speed with the same source/destination addresses, and when
> > > fragmentation on the IPv4 network occurs.  That is, sending
> > lots of packets
> > > with DF=3D0 does not, by itself, cause a problem even if they
> > are fragmented on
> > > the same link -- so long as they have different source or different
> > > destination addresses.  I agree we should make a note of that.
> >
> > Yes, the concern is for same src,dst operating at line
> > rate. IPv6 apps assume that there is no possibility for
> > fragmentation in the network, hence they may not be as
> > shy as IPv4 apps when it comes to sending large packets
> > at high data rates. Having the translator set DF=3D0 can
> > break that assumption.
>=20
> There are three approaches discussed in new text in
> http://tools.ietf.org/html/draft-ietf-behave-v6v4-xlate-08#page-18,
> which only set DF=3D0 for "small packets" (packets that were
> less than 1280 on the IPv6 side).
>=20
> I don't think that eliminates your concern, though.
>=20
> > > Is there another approach that should be considered to
> > > avoid that concern?
> >
> > I still believe placement of the translator matters.
> > Placing the translator closer to the IPv4 host
> > reduces the portion of the path that is exposed to
> > IPv4 hops. This is true whether the DF=3D0 or DF=3D1
> > approach is used.
>=20
> Agreed.
>=20
> However, that isn't always possible.  For example,
> someone operating an IPv6-only network will have to
> place their IPv6/IPv4 translator at their network
> border.
>=20
> But perhaps some text could be added to
> draft-ietf-behave-v6v4-xlate which highlighted
> this recommendation to place the translator as
> close to the IPv4 host as possible.  Or, similarly,
> to ensure the IPv4 network has an MTU greater than
> 1280 (minus whatever the IPv6/IPv4 header differences
> are).
>=20
> -d
>=20
>=20
> > Fred
> > fred.l.templin@boeing.com
> >
> > > > There are certainly plenty of websites on the IPv4 Internet
> > > > that set DF=3D0 on every packet they send, and many even use
> > > > packet sizes larger than 1280. But, how many of them send
> > > > large packets at line rate?
> > >
> > > Content delivery networks?
> > >
> > > -d
> > >
> > >
> > > > Fred
> > > > fred.l.templin@boeing.com
> > > >
> > > > > -----Original Message-----
> > > > > From: behave-bounces@ietf.org
> > > > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > > > Sent: Monday, February 08, 2010 3:29 PM
> > > > > To: 'Iljitsch van Beijnum'
> > > > > Cc: behave@ietf.org
> > > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > > > > Sent: Monday, February 08, 2010 3:02 PM
> > > > > > To: Dan Wing
> > > > > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280
> > byte packets
> > > > > >
> > > > > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > > > > >
> > > > > > >> So essentially this means doing more work (keeping PMTUD
> > > > > > >> state for the IPv4 path) in order to do even more
> > work later
> > > > > > >> (fragment). Not sure how that makes sense...
> > > > > >
> > > > > > > Yes, it means the translator is doing the effort of
> > fragmenting
> > > > > > > rather than the router immediately in front of the small-MTU
> > > > > > > link.  However, by doing it this way, we can
> > maintain end-to-end
> > > > > > > PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
> > > > > > > packets with the fragmentation header.
> > > > > >
> > > > > > No, the two issues are orthogonal.
> > > > > >
> > > > > > At some point, an IPv6 host sends a packet that is larger
> > > > > > than the IPv4 PMTU. A router sends back a too big message.
> > > > > > Issue A is how to handle this too big message. Issue B is
> > > > > > what happens to packets that the IPv6 host subsequently sends.
> > > > >
> > > > > A stateless translator cannot identify 'subsequent' packets,
> > > > > because it doesn't remember previous state.
> > > > >
> > > > > > I think there is agreement that A should be handled by simply
> > > > > > translating the IPv4 too big too IPv6 and adjusting it as per
> > > > > > the header size differences, but otherwise let it through
> > > > > > transparently. (I once argued for rewriting it to
> > 1280, though.)
> > > > > >
> > > > > > Nothing has changed here.
> > > > > >
> > > > > > But now for part B. A stateless translator can't monitor the
> > > > > > IPv4 PMTU. Not because it's stateful (we're talking per
> > > > > > destination state, not per session state, it would be doable
> > > > > > to track this) but because there may be more than one
> > > > > > translator so any given translator may not see all packets.
> > > > > > So for stateless translation when the translator has a < 1280
> > > > > > packet with no fragment header we don't know whether this is
> > > > > > because PMTUD was succesful and the packet size fits in the
> > > > > > PMTU, or the IPv6 host ignored the < 1280 too big message and
> > > > > > is omitting the fragment header in violation of the relevant
> > > > > > RFCs. In order to be compatible with the latter the only
> > > > > > thing we can do is set DF to 0.
> > > > > >
> > > > > > (I just realize that we don't know what happens when for
> > > > > > instance the PMTU is 1000 and the IPv6 host wants to send a
> > > > > > 1100-byte packet: does it include a fragment header or not?)
> > > > > >
> > > > > > Note that for part B, if there _is_ a fragment header, that
> > > > > > will also trigger the translator to set DF to 0. So in the
> > > > > > case where the IPv6 hosts are well behaved there is no change
> > > > > > to either parts A or B.
> > > > >
> > > > > So, I believe we are in agreement:  IPv6 packets less than
> > > > > 1280 need to be translated to IPv4 and sent with DF=3D0.
> > > > >
> > > > > > In the stateful case we know all packets flow through the
> > > > > > same translator so we get to track the IPv4 PMTU so when
> > > > > > there is an IPv6 packet that needs to be translated we know
> > > > > > whether it's bigger or smaller than the PMTU so we can send
> > > > > > packets that are bigger with DF=3D1 and packets that are
> > > > > > smaller with DF=3D0 and if we are to, also immediately fragment
> > > > > > them. However, there is no advantage to doing this extra work
> > > > > > because even if we get to set DF=3D1 on some packets that are
> > > > > > smaller than the PMTU that only lets us discover a reduction
> > > > > > in the PMTU, but that discovery doesn't buy us anything
> > > > > > because the IPv6 host isn't going to reduce its packet size.
> > > > >
> > > > > I agree the IPv6 host won't reduce its packet size below
> > > > > 1280.  But the IPv6 host becomes aware that the path MTU
> > > > > is smaller than 1280.  I don't know if the IPv6 host finds
> > > > > that useful/valuable to know the path MTU is less than the
> > > > > IPv6 minimum MTU.
> > > > >
> > > > > > Fragmenting at the translator also doesn't buy the translator
> > > > > > anything and it may even get the packet blocked or create
> > > > > > more work if there's a firewall with a > 1280 MTU before the
> > > > > > path hits the < 1280 MTU which would need to reassemble the
> > > > > > packet to observe the port numbers. And it could be an attack
> > > > > > vector: attackers could send too bigs with tiny MTUs to make
> > > > > > the translator work harder.
> > > > > >
> > > > > > > Certainly there was some
> > > > > > > perceived value in the IPv6 knowing its packets are being
> > > > > > > fragmented.
> > > > > >
> > > > > > I don't think so. Even if the application somehow learns this
> > > > > > information, what is it supposed to do then?
> > > > >
> > > > > Don't know.  It is obviously easier for the 6/4 translator to
> > > > > simply fragment the packet (or translate and send with
> > DF=3D0) without
> > > > > informing the IPv6 host, but there is long-standing text in both
> > > > > RFC2460 and its predecessor (RFC1883) that says to send back
> > > > > ICMPv6 PTB and the IPv6 host is then supposed to send packets
> > > > > with the fragmentation header.
> > > > >
> > > > > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > > > > >
> > > > > > > But there isn't anything prohibiting PMTUD for UDP.
> > > > > >
> > > > > > With sufficient thrust pigs fly just fine...
> > > > > >
> > > > > > Generally, it's not easy for UDP applications to limit their
> > > > > > packet sizes. So the protocol would have to support changing
> > > > > > the packet size on the fly and then the application would
> > > > > > have to react to too big messages.
> > > > >
> > > > > draft-petithuguenin-behave-stun-pmtud does not rely on
> > > > > ICMP packet too big messages.
> > > > >
> > > > > > Not impossible, but I've never seen it happen.
> > > > >
> > > > > Me, neither.  I'm just trying to temper the "only TCP does
> > > > > PMTUD", because UDP can do PMTUD.  And of course there is value
> > > > > in sending the largest packets possible.
> > > > >
> > > > > > But if BitTorrent goes to UDP it's
> > > > > > likely they'll put this in in some way.
> > > > >
> > > > > As of version 2.x, the most popular BitTorrent client on
> > > > > Windows (uTorrent) has implemented uTP, for whatever that's
> > > > > worth.  I don't know if they're doing PMTUD, though.  Beta
> > > > > versions of uTorrent are available for OSX, too, and I expect
> > > > > they will soon support uTP (if they aren't already).
> > > > >
> > > > > > > I tend to think, though, we don't want to figure this out
> > > > > > > for stateful translators at this point in time.  If it is
> > > > > > > found useful/necessary, it can be specified later.
> > > > > >
> > > > > > Right.=3D
> > > > >
> > > > > -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
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave


From iljitsch@muada.com  Tue Feb  9 10:01:15 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 3CC9B28C24C for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:01:15 -0800 (PST)
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 WNYjLC0AhsLL for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:01:14 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 53EED28C154 for <behave@ietf.org>; Tue,  9 Feb 2010 10:01:14 -0800 (PST)
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 o19I0J5a040396 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 19:00:20 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 19:01:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F007392F-B8ED-4856-A525-3ABA032A9DE2@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boein g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 18:01:15 -0000

On 9 feb 2010, at 18:51, Templin, Fred L wrote:

> So, e.g., if the translator receives a 1500byte
> IPv4 packet and has to translate it into a 1520byte IPv6
> packet, there is a chance that it may be dropped due to a
> link MTU restriction somewhere in the IPv6 network and an
> ICMPv6 PTB sent back toward the translator. Presumably, the
> translator would translate that into an ICMPv4 PTB message
> that it forwards on to the IPv4 host.

If the IPv6 host is connected through a link with a 1500-byte MTU, it =
will advertise a maximum segment size (MSS option) in its TCP SYN packet =
of 1500 - 40 (IPv6 header) - 20 (TCP header) =3D 1440. So the IPv4 host =
will send 1480-byte IPv4 packets which are then translated into =
1500-byte IPv6 packets and there are no issues.

Only when the IPv6 host has an MTU larger than 1500 but the translator =
doesnt the IPv4 PTMUD black holes will be triggered.


From dwing@cisco.com  Tue Feb  9 10:08:19 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 11B263A6CED for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.142
X-Spam-Level: 
X-Spam-Status: No, score=-10.142 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315]
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 94NbjyOcvNyA for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:08:17 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 6C90C3A68B4 for <behave@ietf.org>; Tue,  9 Feb 2010 10:08:17 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0GAFAzcUurRN+J/2dsb2JhbACHe4ESuUeYHII7B4ISBI5H
X-IronPort-AV: E=Sophos;i="4.49,437,1262563200"; d="scan'208";a="480579080"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-6.cisco.com with ESMTP; 09 Feb 2010 18:09:24 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o19I9OiY004200; Tue, 9 Feb 2010 18:09:24 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 10:09:24 -0800
Message-ID: <055401caa9b3$02d42c60$c4f0200a@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
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
Thread-Index: AcqpEs0oJ90THNJHSZaghnxxd0OyXwAASZ1wAAGlmNAAAJb/cAABmZlwAABjT3AAId8FAAABULbg
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 18:08:19 -0000

 

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] 
> Sent: Tuesday, February 09, 2010 9:52 AM
> To: Dan Wing; 'Iljitsch van Beijnum'
> Cc: behave@ietf.org
> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> Dan,
> 
> About the placement of the translator, in the IPv6->IPv4
> direction the packet incurs a size reduction due to the
> substitution of an IPv4 header in place of the IPv6 header.
> In the IPv4->IPv6 direction, however, the size of the packet
> is inflated. So, e.g., if the translator receives a 1500byte
> IPv4 packet and has to translate it into a 1520byte IPv6
> packet, there is a chance that it may be dropped due to a
> link MTU restriction somewhere in the IPv6 network and an
> ICMPv6 PTB sent back toward the translator. Presumably, the
> translator would translate that into an ICMPv4 PTB message
> that it forwards on to the IPv4 host.
> 
> If I have that right, there may be a concern for whether
> the ICMPv4 PTB would be dropped in the IPv4 network before
> it arrives at the IPv4 host. I ran some tests and found
> that path MTU discovery in IPv4 seems to be problematic
> for a substantial number of the top 1000 websites:
> 
> http://www.ietf.org/mail-archive/web/rrg/current/msg05907.html
> 
> This suggests to me that path MTU discovery in the IPv4
> network "works" simply because it is rarely invoked. 

Agreed.

> In other words, the IPv4 network seems to be getting by
> based on the good fortune that most links in the Internet
> core configure an MTU of 1500 or larger. But, this state
> of affairs may be disrupted if more and more translators
> are used that cause IPv4 packets to be inflated in size
> after they are translated into IPv6 packets.

Agreed.

Which is why tweaking the TCP MSS is a helpful workaround
to blocked ICMP PTB.  But tweaking TCP MSS restricts us to 
the lowest common denominator (that is, limiting TCP MSS 
means we can't expect to use larger-than-1500 frames).

I know Lars Eggert had concerns with a translator tweaking
TCP MSS in a translator, and there is only a very brief 
mention in draft-ietf-behave-v6v4-xlate.

> So, if the translator were located at the site border of
> the IPv4 host (i.e., rather than at the site border of
> the IPv6 host) the bulk of the path would be over IPv6
> instead of IPv4, hence the incidence of ICMPv4 filtering
> would be isolated to the end site of the IPv4 host.

That places the onus on the content provider to make their
content available to IPv6.  And there are millions of 
content providers from the local school district's website
to magazine sites, online stores, and so on.  

They can't add IPv6 support in time:  there simply isn't
enough time left.

> Has the translator deployment analysis taken IPv4 path
> MTU-related black holing into consideration?

No.

-d


> Fred
> fred.l.templin@boeing.com  
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Monday, February 08, 2010 5:16 PM
> > To: Templin, Fred L; 'Iljitsch van Beijnum'
> > Cc: behave@ietf.org
> > Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org
> > > [mailto:behave-bounces@ietf.org] On Behalf Of Templin, Fred L
> > > Sent: Monday, February 08, 2010 5:11 PM
> > > To: Dan Wing; 'Iljitsch van Beijnum'
> > > Cc: behave@ietf.org
> > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > >
> > > Dan,
> > >
> > > > -----Original Message-----
> > > > From: behave-bounces@ietf.org
> > > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > > Sent: Monday, February 08, 2010 4:24 PM
> > > > To: Templin, Fred L; 'Iljitsch van Beijnum'
> > > > Cc: behave@ietf.org
> > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > Sent: Monday, February 08, 2010 4:02 PM
> > > > > To: Dan Wing; 'Iljitsch van Beijnum'
> > > > > Cc: behave@ietf.org
> > > > > Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 
> byte packets
> > > > >
> > > > > The concern with setting DF=0 on the IPv4 side for packets
> > > > > that are 1280 or smaller on the IPv6 side is the possibility
> > > > > for RFC4963 data corruption if we let it run at line rate.
> > > >
> > > > At high speed with the same source/destination 
> addresses, and when
> > > > fragmentation on the IPv4 network occurs.  That is, sending
> > > lots of packets
> > > > with DF=0 does not, by itself, cause a problem even if they
> > > are fragmented on
> > > > the same link -- so long as they have different source 
> or different
> > > > destination addresses.  I agree we should make a note of that.
> > >
> > > Yes, the concern is for same src,dst operating at line
> > > rate. IPv6 apps assume that there is no possibility for
> > > fragmentation in the network, hence they may not be as
> > > shy as IPv4 apps when it comes to sending large packets
> > > at high data rates. Having the translator set DF=0 can
> > > break that assumption.
> > 
> > There are three approaches discussed in new text in
> > http://tools.ietf.org/html/draft-ietf-behave-v6v4-xlate-08#page-18,
> > which only set DF=0 for "small packets" (packets that were
> > less than 1280 on the IPv6 side).
> > 
> > I don't think that eliminates your concern, though.
> > 
> > > > Is there another approach that should be considered to
> > > > avoid that concern?
> > >
> > > I still believe placement of the translator matters.
> > > Placing the translator closer to the IPv4 host
> > > reduces the portion of the path that is exposed to
> > > IPv4 hops. This is true whether the DF=0 or DF=1
> > > approach is used.
> > 
> > Agreed.
> > 
> > However, that isn't always possible.  For example,
> > someone operating an IPv6-only network will have to
> > place their IPv6/IPv4 translator at their network
> > border.
> > 
> > But perhaps some text could be added to
> > draft-ietf-behave-v6v4-xlate which highlighted
> > this recommendation to place the translator as
> > close to the IPv4 host as possible.  Or, similarly,
> > to ensure the IPv4 network has an MTU greater than
> > 1280 (minus whatever the IPv6/IPv4 header differences
> > are).
> > 
> > -d
> > 
> > 
> > > Fred
> > > fred.l.templin@boeing.com
> > >
> > > > > There are certainly plenty of websites on the IPv4 Internet
> > > > > that set DF=0 on every packet they send, and many even use
> > > > > packet sizes larger than 1280. But, how many of them send
> > > > > large packets at line rate?
> > > >
> > > > Content delivery networks?
> > > >
> > > > -d
> > > >
> > > >
> > > > > Fred
> > > > > fred.l.templin@boeing.com
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: behave-bounces@ietf.org
> > > > > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > > > > > Sent: Monday, February 08, 2010 3:29 PM
> > > > > > To: 'Iljitsch van Beijnum'
> > > > > > Cc: behave@ietf.org
> > > > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 
> byte packets
> > > > > >
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> > > > > > > Sent: Monday, February 08, 2010 3:02 PM
> > > > > > > To: Dan Wing
> > > > > > > Cc: 'marcelo bagnulo braun'; behave@ietf.org
> > > > > > > Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280
> > > byte packets
> > > > > > >
> > > > > > > On 8 feb 2010, at 23:34, Dan Wing wrote:
> > > > > > >
> > > > > > > >> So essentially this means doing more work 
> (keeping PMTUD
> > > > > > > >> state for the IPv4 path) in order to do even more
> > > work later
> > > > > > > >> (fragment). Not sure how that makes sense...
> > > > > > >
> > > > > > > > Yes, it means the translator is doing the effort of
> > > fragmenting
> > > > > > > > rather than the router immediately in front of 
> the small-MTU
> > > > > > > > link.  However, by doing it this way, we can
> > > maintain end-to-end
> > > > > > > > PMTUD for those IPv6 hosts that receive ICMPv6 
> PTB and send
> > > > > > > > packets with the fragmentation header.
> > > > > > >
> > > > > > > No, the two issues are orthogonal.
> > > > > > >
> > > > > > > At some point, an IPv6 host sends a packet that is larger
> > > > > > > than the IPv4 PMTU. A router sends back a too big message.
> > > > > > > Issue A is how to handle this too big message. Issue B is
> > > > > > > what happens to packets that the IPv6 host 
> subsequently sends.
> > > > > >
> > > > > > A stateless translator cannot identify 'subsequent' packets,
> > > > > > because it doesn't remember previous state.
> > > > > >
> > > > > > > I think there is agreement that A should be 
> handled by simply
> > > > > > > translating the IPv4 too big too IPv6 and 
> adjusting it as per
> > > > > > > the header size differences, but otherwise let it through
> > > > > > > transparently. (I once argued for rewriting it to
> > > 1280, though.)
> > > > > > >
> > > > > > > Nothing has changed here.
> > > > > > >
> > > > > > > But now for part B. A stateless translator can't 
> monitor the
> > > > > > > IPv4 PMTU. Not because it's stateful (we're talking per
> > > > > > > destination state, not per session state, it 
> would be doable
> > > > > > > to track this) but because there may be more than one
> > > > > > > translator so any given translator may not see 
> all packets.
> > > > > > > So for stateless translation when the translator 
> has a < 1280
> > > > > > > packet with no fragment header we don't know 
> whether this is
> > > > > > > because PMTUD was succesful and the packet size 
> fits in the
> > > > > > > PMTU, or the IPv6 host ignored the < 1280 too big 
> message and
> > > > > > > is omitting the fragment header in violation of 
> the relevant
> > > > > > > RFCs. In order to be compatible with the latter the only
> > > > > > > thing we can do is set DF to 0.
> > > > > > >
> > > > > > > (I just realize that we don't know what happens when for
> > > > > > > instance the PMTU is 1000 and the IPv6 host wants 
> to send a
> > > > > > > 1100-byte packet: does it include a fragment 
> header or not?)
> > > > > > >
> > > > > > > Note that for part B, if there _is_ a fragment 
> header, that
> > > > > > > will also trigger the translator to set DF to 0. So in the
> > > > > > > case where the IPv6 hosts are well behaved there 
> is no change
> > > > > > > to either parts A or B.
> > > > > >
> > > > > > So, I believe we are in agreement:  IPv6 packets less than
> > > > > > 1280 need to be translated to IPv4 and sent with DF=0.
> > > > > >
> > > > > > > In the stateful case we know all packets flow through the
> > > > > > > same translator so we get to track the IPv4 PMTU so when
> > > > > > > there is an IPv6 packet that needs to be 
> translated we know
> > > > > > > whether it's bigger or smaller than the PMTU so 
> we can send
> > > > > > > packets that are bigger with DF=1 and packets that are
> > > > > > > smaller with DF=0 and if we are to, also 
> immediately fragment
> > > > > > > them. However, there is no advantage to doing 
> this extra work
> > > > > > > because even if we get to set DF=1 on some 
> packets that are
> > > > > > > smaller than the PMTU that only lets us discover 
> a reduction
> > > > > > > in the PMTU, but that discovery doesn't buy us anything
> > > > > > > because the IPv6 host isn't going to reduce its 
> packet size.
> > > > > >
> > > > > > I agree the IPv6 host won't reduce its packet size below
> > > > > > 1280.  But the IPv6 host becomes aware that the path MTU
> > > > > > is smaller than 1280.  I don't know if the IPv6 host finds
> > > > > > that useful/valuable to know the path MTU is less than the
> > > > > > IPv6 minimum MTU.
> > > > > >
> > > > > > > Fragmenting at the translator also doesn't buy 
> the translator
> > > > > > > anything and it may even get the packet blocked or create
> > > > > > > more work if there's a firewall with a > 1280 MTU 
> before the
> > > > > > > path hits the < 1280 MTU which would need to 
> reassemble the
> > > > > > > packet to observe the port numbers. And it could 
> be an attack
> > > > > > > vector: attackers could send too bigs with tiny 
> MTUs to make
> > > > > > > the translator work harder.
> > > > > > >
> > > > > > > > Certainly there was some
> > > > > > > > perceived value in the IPv6 knowing its packets 
> are being
> > > > > > > > fragmented.
> > > > > > >
> > > > > > > I don't think so. Even if the application somehow 
> learns this
> > > > > > > information, what is it supposed to do then?
> > > > > >
> > > > > > Don't know.  It is obviously easier for the 6/4 
> translator to
> > > > > > simply fragment the packet (or translate and send with
> > > DF=0) without
> > > > > > informing the IPv6 host, but there is long-standing 
> text in both
> > > > > > RFC2460 and its predecessor (RFC1883) that says to send back
> > > > > > ICMPv6 PTB and the IPv6 host is then supposed to 
> send packets
> > > > > > with the fragmentation header.
> > > > > >
> > > > > > > > I agree that nearly 100% of PMTUD on IPv4 is with TCP.
> > > > > > >
> > > > > > > > But there isn't anything prohibiting PMTUD for UDP.
> > > > > > >
> > > > > > > With sufficient thrust pigs fly just fine...
> > > > > > >
> > > > > > > Generally, it's not easy for UDP applications to 
> limit their
> > > > > > > packet sizes. So the protocol would have to 
> support changing
> > > > > > > the packet size on the fly and then the application would
> > > > > > > have to react to too big messages.
> > > > > >
> > > > > > draft-petithuguenin-behave-stun-pmtud does not rely on
> > > > > > ICMP packet too big messages.
> > > > > >
> > > > > > > Not impossible, but I've never seen it happen.
> > > > > >
> > > > > > Me, neither.  I'm just trying to temper the "only TCP does
> > > > > > PMTUD", because UDP can do PMTUD.  And of course 
> there is value
> > > > > > in sending the largest packets possible.
> > > > > >
> > > > > > > But if BitTorrent goes to UDP it's
> > > > > > > likely they'll put this in in some way.
> > > > > >
> > > > > > As of version 2.x, the most popular BitTorrent client on
> > > > > > Windows (uTorrent) has implemented uTP, for whatever that's
> > > > > > worth.  I don't know if they're doing PMTUD, though.  Beta
> > > > > > versions of uTorrent are available for OSX, too, 
> and I expect
> > > > > > they will soon support uTP (if they aren't already).
> > > > > >
> > > > > > > > I tend to think, though, we don't want to 
> figure this out
> > > > > > > > for stateful translators at this point in time. 
>  If it is
> > > > > > > > found useful/necessary, it can be specified later.
> > > > > > >
> > > > > > > Right.=
> > > > > >
> > > > > > -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
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www.ietf.org/mailman/listinfo/behave
> 


From iljitsch@muada.com  Tue Feb  9 10:18:33 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 964923A6919 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:18:33 -0800 (PST)
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 eXdLl8uQt8SH for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:18:32 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 818743A6870 for <behave@ietf.org>; Tue,  9 Feb 2010 10:18:32 -0800 (PST)
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 o19IGrl5040506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 19:16:54 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <055401caa9b3$02d42c60$c4f0200a@cisco.com>
Date: Tue, 9 Feb 2010 19:18:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 18:18:33 -0000

On 9 feb 2010, at 19:09, Dan Wing wrote:

> Which is why tweaking the TCP MSS is a helpful workaround
> to blocked ICMP PTB.

There very little need to do anything to the MSS option, see my previous =
message.

Only in the case where the IPv6 host supports an MTU larger than 1500 =
but the translator doesn't, there is a possible optimization by having =
the translator rewrite the MSS to the maximum that the translator =
supports so the translator wouldn't have to send too bigs and there is =
less risk of PMTUD black holes. However, it's not clear to me that this =
case is worth the trouble.

> But tweaking TCP MSS restricts us to=20
> the lowest common denominator (that is, limiting TCP MSS=20
> means we can't expect to use larger-than-1500 frames).

Obviously you would be advertising the minimum of what the IPv6 host and =
the translator can handle and not simply hardcode 1500. If both do more =
than 1500 bytes then you advertise more than 1500 bytes and you get to =
use more than 1500 bytes. Note that this won't trigger any black holes =
because the IPv4 hosts will send 1500-byte packets. (The intersection =
between users with broken PMTUD setups and users with an MTU larger than =
1500 is rather small.)=

From Fred.L.Templin@boeing.com  Tue Feb  9 10:33:46 2010
Return-Path: <Fred.L.Templin@boeing.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 243103A6CED for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:33:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 XqcsgGFbkEci for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:33:45 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 230383A6849 for <behave@ietf.org>; Tue,  9 Feb 2010 10:33:45 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19IYkoH001612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2010 12:34:47 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19IYkmS029244; Tue, 9 Feb 2010 10:34:46 -0800 (PST)
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19IYkqc029239 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 10:34:46 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Tue, 9 Feb 2010 10:34:46 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, Dan Wing <dwing@cisco.com>
Date: Tue, 9 Feb 2010 10:34:45 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqptHCcGRwWD3tQRBCY4zj6piIppQAAabyA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boein g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com>
In-Reply-To: <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 18:33:46 -0000

Iljitsch,

You may be missing the "dumbbell configutation" where
both the IPv6 host and translator are on 9KB links but
there are 1500 links in between?

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Tuesday, February 09, 2010 10:18 AM
> To: Dan Wing
> Cc: Templin, Fred L; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
> On 9 feb 2010, at 19:09, Dan Wing wrote:
>=20
> > Which is why tweaking the TCP MSS is a helpful workaround
> > to blocked ICMP PTB.
>=20
> There very little need to do anything to the MSS option, see my previous =
message.
>=20
> Only in the case where the IPv6 host supports an MTU larger than 1500 but=
 the translator doesn't,
> there is a possible optimization by having the translator rewrite the MSS=
 to the maximum that the
> translator supports so the translator wouldn't have to send too bigs and =
there is less risk of PMTUD
> black holes. However, it's not clear to me that this case is worth the tr=
ouble.
>=20
> > But tweaking TCP MSS restricts us to
> > the lowest common denominator (that is, limiting TCP MSS
> > means we can't expect to use larger-than-1500 frames).
>=20
> Obviously you would be advertising the minimum of what the IPv6 host and =
the translator can handle
> and not simply hardcode 1500. If both do more than 1500 bytes then you ad=
vertise more than 1500 bytes
> and you get to use more than 1500 bytes. Note that this won't trigger any=
 black holes because the
> IPv4 hosts will send 1500-byte packets. (The intersection between users w=
ith broken PMTUD setups and
> users with an MTU larger than 1500 is rather small.)

From dwing@cisco.com  Tue Feb  9 10:49:26 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 550913A6849 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.542
X-Spam-Level: 
X-Spam-Status: No, score=-10.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 0kN8u+hT3zsa for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:49:25 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 7F1773A6F19 for <behave@ietf.org>; Tue,  9 Feb 2010 10:49:25 -0800 (PST)
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: Ag0GAOs8cUurRN+K/2dsb2JhbACHe4ESuT6YIII7ghkE
X-IronPort-AV: E=Sophos;i="4.49,437,1262563200"; d="scan'208";a="85759184"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 09 Feb 2010 18:50:32 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o19IoW7w017231; Tue, 9 Feb 2010 18:50:32 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com>
Date: Tue, 9 Feb 2010 10:50:32 -0800
Message-ID: <05b401caa9b8$c215ddd0$c4f0200a@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
In-Reply-To: <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com>
Thread-Index: AcqptHQR+99HGJ3YTzqUekhzldpULQABB5yQ
Cc: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 18:49:26 -0000

 

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com] 
> Sent: Tuesday, February 09, 2010 10:18 AM
> To: Dan Wing
> Cc: 'Templin, Fred L'; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> On 9 feb 2010, at 19:09, Dan Wing wrote:
> 
> > Which is why tweaking the TCP MSS is a helpful workaround
> > to blocked ICMP PTB.
> 
> There very little need to do anything to the MSS option, see 
> my previous message.
> 
> Only in the case where the IPv6 host supports an MTU larger 
> than 1500 but the translator doesn't, there is a possible 
> optimization by having the translator rewrite the MSS to the 
> maximum that the translator supports so the translator 
> wouldn't have to send too bigs and there is less risk of 
> PMTUD black holes. However, it's not clear to me that this 
> case is worth the trouble.

There are long-standing desires to MTUs larger than 1500
with IPv6, under the theory that IPv6 Did Things Correctly.

-d


> > But tweaking TCP MSS restricts us to 
> > the lowest common denominator (that is, limiting TCP MSS 
> > means we can't expect to use larger-than-1500 frames).
> 
> Obviously you would be advertising the minimum of what the 
> IPv6 host and the translator can handle and not simply 
> hardcode 1500. If both do more than 1500 bytes then you 
> advertise more than 1500 bytes and you get to use more than 
> 1500 bytes. Note that this won't trigger any black holes 
> because the IPv4 hosts will send 1500-byte packets. (The 
> intersection between users with broken PMTUD setups and users 
> with an MTU larger than 1500 is rather small.)=


From iljitsch@muada.com  Tue Feb  9 10:49:31 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 E398C3A746C for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:49:31 -0800 (PST)
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 ze5e6oXOTy9E for <behave@core3.amsl.com>; Tue,  9 Feb 2010 10:49:31 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 8B31D3A7461 for <behave@ietf.org>; Tue,  9 Feb 2010 10:49:30 -0800 (PST)
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 o19ImmZc040668 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 19:48:49 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 19:50:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boein g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 18:49:32 -0000

On 9 feb 2010, at 19:34, Templin, Fred L wrote:

> You may be missing the "dumbbell configutation" where
> both the IPv6 host and translator are on 9KB links but
> there are 1500 links in between?

Yes, that could happen. And it would suck.  :-)

For the IPv6-to-IPv4 direction there is no problem, because the IPv6 =
host simply runs PMTUD. For the IPv4-to-IPv6 direction with DF=3D1 any =
black holes on the IPv4 side will be triggered and with DF=3D0 I believe =
the current text specifies always fragmenting to 1280, which I very much =
disagree with and which we haven't had any discussion about.

But you really don't want to run a translator with jumboframes if you =
can't reach at least _some_ translator clients with large packets.=

From iljitsch@muada.com  Tue Feb  9 11:04:59 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 D9C973A742D for <behave@core3.amsl.com>; Tue,  9 Feb 2010 11:04:59 -0800 (PST)
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 DuuazDV9Axue for <behave@core3.amsl.com>; Tue,  9 Feb 2010 11:04:59 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 298553A72D1 for <behave@ietf.org>; Tue,  9 Feb 2010 11:04:57 -0800 (PST)
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 o19J4NMH040784 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 20:04:24 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <05b401caa9b8$c215ddd0$c4f0200a@cisco.com>
Date: Tue, 9 Feb 2010 20:05:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1F65873-4140-424F-9DCC-4A737D3EDA38@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <05b401caa9b8$c215ddd0$c4f0200a@cisco.com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 19:05:00 -0000

On 9 feb 2010, at 19:50, Dan Wing wrote:

>> Only in the case where the IPv6 host supports an MTU larger=20
>> than 1500 but the translator doesn't, there is a possible=20
>> optimization by having the translator rewrite the MSS to the=20
>> maximum that the translator supports so the translator=20
>> wouldn't have to send too bigs and there is less risk of=20
>> PMTUD black holes. However, it's not clear to me that this=20
>> case is worth the trouble.

> There are long-standing desires to MTUs larger than 1500
> with IPv6, under the theory that IPv6 Did Things Correctly.

You can send large packets with IPv4, too. Having a bigger than 1500 =
byte MTU causes much fewer problems than having a smaller than 1500 byte =
MTU for a number of reasons which are explained in =
http://tools.ietf.org/html/draft-van-beijnum-multi-mtu-02

However, if you have a 1500+ MTU on the IPv6 side (but the translator =
has 1500), the MSS doesn't fix the PMTUD black holes that are caused by =
the fact that that the IPv6 host has a 1480 path MTU seen from the IPv4 =
side while it advertising a larger one in the MSS.

If we want to avoid this particular black hole the solution is to =
rewrite the MSS in the translator to the minimum of the IPv6 host's MSS =
and the translator MTU on the IPv6 side + sizeof(IPv4) - sizeof(IPv6).

I don't remember the discussion about MSS rewriting in the softwires =
context, just that my conclusion was that that issue doesn't apply here. =
In any event, MSS clamping has been a staple of cheap NAT/PPPoE boxes =
and I don't believe it causes any problems.=

From Fred.L.Templin@boeing.com  Tue Feb  9 11:09:24 2010
Return-Path: <Fred.L.Templin@boeing.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 E04F83A7451 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 11:09:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.583
X-Spam-Level: 
X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016,  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 s45wcNKo+Syv for <behave@core3.amsl.com>; Tue,  9 Feb 2010 11:09:24 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id EFF333A73F6 for <behave@ietf.org>; Tue,  9 Feb 2010 11:09:23 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19JAMNA024687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2010 13:10:22 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19JALNM027791; Tue, 9 Feb 2010 11:10:21 -0800 (PST)
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19JALGS027786 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 11:10:21 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-09.nw.nos.boeing.com ([130.247.25.115]) with mapi; Tue, 9 Feb 2010 11:10:21 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 9 Feb 2010 11:10:19 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: AcqpuN71RMYjGRACQpqME6dnRXfcKAAAeAnQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A6495103828D@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007 @ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7 F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boei n g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com> <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com>
In-Reply-To: <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 19:09:25 -0000

Iljitsch,

Another concern I should have called out earlier is what
if the IPv6 host is on a 1500 link and opens a TCP
connection to the IPv4 server with MSS=3D1440. The IPv4
server sends a 1480b IPv4 packet that gets translated
into a 1500b IPv6 packet. The packet makes its way
through the IPv6 network toward the IPv6 host, but
first it hits a 1480 MTU link (e.g., and IPv6 over IPv4
tunnel). The ICMPv6 PTB gets triggered, then translated
into ICMPv4 fragmentation needed, then dropped by
a filtering gateway in the IPv4 Internet.

Black hole, right?

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Tuesday, February 09, 2010 10:50 AM
> To: Templin, Fred L
> Cc: Dan Wing; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
> On 9 feb 2010, at 19:34, Templin, Fred L wrote:
>=20
> > You may be missing the "dumbbell configutation" where
> > both the IPv6 host and translator are on 9KB links but
> > there are 1500 links in between?
>=20
> Yes, that could happen. And it would suck.  :-)
>=20
> For the IPv6-to-IPv4 direction there is no problem, because the IPv6 host=
 simply runs PMTUD. For the
> IPv4-to-IPv6 direction with DF=3D1 any black holes on the IPv4 side will =
be triggered and with DF=3D0 I
> believe the current text specifies always fragmenting to 1280, which I ve=
ry much disagree with and
> which we haven't had any discussion about.
>=20
> But you really don't want to run a translator with jumboframes if you can=
't reach at least _some_
> translator clients with large packets.

From dwing@cisco.com  Tue Feb  9 12:13:52 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 9C1B53A62C1 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.548
X-Spam-Level: 
X-Spam-Status: No, score=-10.548 tagged_above=-999 required=5 tests=[AWL=0.051, 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 FmEX0VC8ayft for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:13:51 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 2B71C3A68B4 for <behave@ietf.org>; Tue,  9 Feb 2010 12:13:51 -0800 (PST)
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: Ag0GAOZQcUurRN+J/2dsb2JhbACHe4ESuRWYJ4RUBA
X-IronPort-AV: E=Sophos;i="4.49,438,1262563200"; d="scan'208";a="85818198"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 09 Feb 2010 20:14:58 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o19KEwbi024312; Tue, 9 Feb 2010 20:14:58 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <05b401caa9b8$c215ddd0$c4f0200a@cisco.com> <A1F65873-4140-424F-9DCC-4A737D3EDA38@muada.com>
Date: Tue, 9 Feb 2010 12:14:58 -0800
Message-ID: <068601caa9c4$8d9ea8f0$c4f0200a@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
In-Reply-To: <A1F65873-4140-424F-9DCC-4A737D3EDA38@muada.com>
Thread-Index: Acqpuu0T3nweyweERpiv+G2fjh03NwACTmxg
Cc: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 20:13:52 -0000

 

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com] 
> Sent: Tuesday, February 09, 2010 11:06 AM
> To: Dan Wing
> Cc: 'Templin, Fred L'; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
> 
> On 9 feb 2010, at 19:50, Dan Wing wrote:
> 
> >> Only in the case where the IPv6 host supports an MTU larger 
> >> than 1500 but the translator doesn't, there is a possible 
> >> optimization by having the translator rewrite the MSS to the 
> >> maximum that the translator supports so the translator 
> >> wouldn't have to send too bigs and there is less risk of 
> >> PMTUD black holes. However, it's not clear to me that this 
> >> case is worth the trouble.
> 
> > There are long-standing desires to MTUs larger than 1500
> > with IPv6, under the theory that IPv6 Did Things Correctly.
> 
> You can send large packets with IPv4, too.

Yes, but experience on the IPv4 Internet shows that ICMP packet-too-big are
unreliable.  So many have given up on IPv4.  Closed environments, including
where tunnels are operating over equipment you own/control, are different.
But that is why I said 'desires' and put 
'Did Things Correctly' in quotes.  My goal, as chair, is to make sure
translators do not make deployment of large-MTU networks worse.  If they do,
it will complicate acceptance by IESG.

-d


> Having a bigger 
> than 1500 byte MTU causes much fewer problems than having a 
> smaller than 1500 byte MTU for a number of reasons which are 
> explained in http://tools.ietf.org/html/draft-van-beijnum-multi-mtu-02
> 
> However, if you have a 1500+ MTU on the IPv6 side (but the 
> translator has 1500), the MSS doesn't fix the PMTUD black 
> holes that are caused by the fact that that the IPv6 host has 
> a 1480 path MTU seen from the IPv4 side while it advertising 
> a larger one in the MSS.
> 
> If we want to avoid this particular black hole the solution 
> is to rewrite the MSS in the translator to the minimum of the 
> IPv6 host's MSS and the translator MTU on the IPv6 side + 
> sizeof(IPv4) - sizeof(IPv6).
> 
> I don't remember the discussion about MSS rewriting in the 
> softwires context, just that my conclusion was that that 
> issue doesn't apply here. In any event, MSS clamping has been 
> a staple of cheap NAT/PPPoE boxes and I don't believe it 
> causes any problems.=


From iljitsch@muada.com  Tue Feb  9 12:24:56 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 559433A75F9 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 o-M0vZZVVjSD for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:24:55 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id B35D23A7486 for <behave@ietf.org>; Tue,  9 Feb 2010 12:24:54 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o19KOYas041314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 21:24:35 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A6495103828D@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 21:25:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B264313-3BE0-4C44-9BD3-718FC6F8A9E5@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007 @ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7 F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boei n g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com> <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103828D@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 20:24:56 -0000

On 9 feb 2010, at 20:10, Templin, Fred L wrote:

> Another concern I should have called out earlier is what
> if the IPv6 host is on a 1500 link and opens a TCP
> connection to the IPv4 server with MSS=3D1440. The IPv4
> server sends a 1480b IPv4 packet that gets translated
> into a 1500b IPv6 packet. The packet makes its way
> through the IPv6 network toward the IPv6 host, but
> first it hits a 1480 MTU link (e.g., and IPv6 over IPv4
> tunnel). The ICMPv6 PTB gets triggered, then translated
> into ICMPv4 fragmentation needed, then dropped by
> a filtering gateway in the IPv4 Internet.

> Black hole, right?

Indeed. Note however that the same black hole would exist if both ends =
are IPv6 or both ends are IPv4 and there is no translator. I don't think =
we can reasonably expect NAT64s to fix all possible black holes.

In practice, I think NAT64 users would have to avoid reduced MTUs =
between the translator and the IPv6 hosts (and I would assume that a =
deployment that needs NAT64 is far enough along that it doesn't need =
IPv6-in-IP tunneling) or artificially lower the IPv6 host MTU or the =
translator MTU / rewrite the MSS if a reduced MTU is present between the =
translator and the IPv6 hosts.=

From dwing@cisco.com  Tue Feb  9 12:25:53 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 233A13A75F9; Tue,  9 Feb 2010 12:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.403
X-Spam-Level: 
X-Spam-Status: No, score=-10.403 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 aS2BIiVNf7fS; Tue,  9 Feb 2010 12:25:52 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 2D0E93A7486; Tue,  9 Feb 2010 12:25:52 -0800 (PST)
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: Ag0GAGtTcUurRN+J/2dsb2JhbACHe4ESuQqYJ4RUBA
X-IronPort-AV: E=Sophos;i="4.49,438,1262563200"; d="scan'208";a="85830134"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 09 Feb 2010 20:26:59 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o19KQxdP002942; Tue, 9 Feb 2010 20:26:59 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com><F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com><E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com> <9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr>
Date: Tue, 9 Feb 2010 12:26:59 -0800
Message-ID: <069e01caa9c6$3b575b80$c4f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr>
Thread-Index: AcqpboELmirW5NtqQn2Gq57lz2MpegAV02rw
Cc: softwires@ietf.org, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 09 Feb 2010 20:25:53 -0000

=20

> -----Original Message-----
> From: softwires-bounces@ietf.org=20
> [mailto:softwires-bounces@ietf.org] On Behalf Of R=E9mi Despr=E9s
> Sent: Tuesday, February 09, 2010 1:59 AM
> To: Templin, Fred L
> Cc: softwires@ietf.org; Behave WG
> Subject: Re: [Softwires] [BEHAVE] PMTU Discovery and ICMPv6 filtering
>=20
>=20
> Le 8 f=E9vr. 2010 =E0 22:08, Templin, Fred L a =E9crit :
>=20
> > Also, there seems to be some evidence that ICMPv6 PTB
> > messages are being dropped in the network.
>=20
> In IPv6, I hope it will be possible to agree at least that=20
> PTB messages SHOULD be forwarded (if not MUST).
> Reasons to not agree should IMHO be seriously documented.

Ben Stasiewicz's tests [*] on the IPv6 Internet show that 56% of
IPv6 hosts do not properly respond to ICMPv6 packet-too-big
with an MTU<1280.  I do not believe additional MUSTs in RFCs=20
from the IETF would have a noticeable effect.

[*] http://www.ietf.org/mail-archive/web/behave/current/msg08093.html

-d


> > ... for DF=3D1 packets the tunnel
> > ingress MUST send an ICMP PTB when the packet is larger
> > than a fixed minimum tunnel MTU and also too large to
> > traverse the tunnel in a single piece. For packets that
> > are no larger than the fixed minimum tunnel MTU, the
> > tunnel ingress SHOULD use tunnel fragmentation (i.e.,
> > SEAL segmentation and reassembly). Presumably, the tunnel
> > ingress would choose a fixed minimum tunnel MTU that is
> > large enough so that source hosts will not see excessive
> > data loss and retransmissions due to path MTU discovery
> > interactions.
> >=20
> > For many/most deployments, a fixed minimum tunnel MTU of
> > 1500 bytes would seem advisable.
>=20
> In my understanding, we can keep the current IPv6 value of=20
> 1280 as the minimum that has to traverse ALL tunnels, and=20
> note that if a tunnel has an internal mechanism to fragment=20
> at entrance and reassemble at exit (e.g. SEAL), the tunnel=20
> advertised MTU can become independent from that of the=20
> traversed infrastructure.=20
>=20
> Thoughts?
>=20
> Cheers,
> RD
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From iljitsch@muada.com  Tue Feb  9 12:41:05 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 4E8F13A6F43 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 1+rC20GeBtuS for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:41:04 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 2395C3A7270 for <behave@ietf.org>; Tue,  9 Feb 2010 12:41:03 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o19KdhgR041420 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 21:39:44 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <068601caa9c4$8d9ea8f0$c4f0200a@cisco.com>
Date: Tue, 9 Feb 2010 21:40:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD773A16-7CA0-4767-BD66-202CE71E8F76@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <05b401caa9b8$c215ddd0$c4f0200a@cisco.com> <A1F65873-4140-424F-9DCC-4A737D3EDA38@muada.com> <068601caa9c4$8d9ea8f0$c4f0200a@cisco.com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 20:41:05 -0000

On 9 feb 2010, at 21:14, Dan Wing wrote:

>> You can send large packets with IPv4, too.

> Yes, but experience on the IPv4 Internet shows that ICMP =
packet-too-big are
> unreliable.  So many have given up on IPv4.

I don't know about the latter, but please don't think that issues you =
see with too bigs in one direction translate to the same issues with too =
bigs in the other direction.

The reason PMTUD black holes are common is because people filter them =
out in their firewalls or their hosts because they have some irrational =
fear of ICMP messages and/or they don't think they need to see those =
messages. If you have a reduced MTU, you depend on the side with the =
regular 1500-byte MTU handling PMTUD properly. If they don't, you have a =
problem that _you_ can't fix. If you use jumboframes and communicate =
with someone with a smaller MTU, you have to run PMTUD properly =
_yourself_ to avoid problems. So you would probably not want to filter =
too big messages. Or if somehow you can't get the PMTUD to work, you can =
always reduce your MTU to avoid the problem. People with small MTUs =
generally can't increase those.

So the only issue that I see is the case where too bigs aren't properly =
generated in the first place. I'm sure there will be a few networks =
where this is the case, but these are outgoing ICMP messages and as a =
rule network operators don't filter ICMP, at least not as often as =
server operators. You also only have a jumbo-clean path towards a =
limited number of networks, so you don't need 100% of the server =
operators to handle PMTUD correctly but only a few percent of the =
network operators. So you will very likely not see any problems. If =
problems are rare they're also more likely to be fixed when they occur.

Maybe we should ask people on the MTU list about their experiences.=

From Fred.L.Templin@boeing.com  Tue Feb  9 12:47:09 2010
Return-Path: <Fred.L.Templin@boeing.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 9A22E3A73F6 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.083
X-Spam-Level: 
X-Spam-Status: No, score=-6.083 tagged_above=-999 required=5 tests=[AWL=-0.484, BAYES_00=-2.599, J_BACKHAIR_44=1, 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 rWlbmDUx9zwv for <behave@core3.amsl.com>; Tue,  9 Feb 2010 12:47:08 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 8518A3A7328 for <behave@ietf.org>; Tue,  9 Feb 2010 12:47:08 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id o19Km6u9011552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2010 12:48:06 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id o19Km5jt023965; Tue, 9 Feb 2010 14:48:05 -0600 (CST)
Received: from XCH-NWHT-05.nw.nos.boeing.com (xch-nwht-05.nw.nos.boeing.com [130.247.25.109]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id o19Km5vU023947 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 9 Feb 2010 14:48:05 -0600 (CST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-05.nw.nos.boeing.com ([130.247.25.109]) with mapi; Tue, 9 Feb 2010 12:48:05 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 9 Feb 2010 12:48:03 -0800
Thread-Topic: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
Thread-Index: Acqpxlb55ZCvlBsoTyWWPsAXGCZ1twAAVwlQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951038309@XCH-NW-01V.nw.nos.boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007 @ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7 F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boei n g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com> <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103828D@XCH-NW-01V.nw.nos.boeing.com> <5B264313-3BE0-4C44-9BD3-718FC6F8A9E5@muada.com>
In-Reply-To: <5B264313-3BE0-4C44-9BD3-718FC6F8A9E5@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 20:47:09 -0000

Hi Iljitsch,

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Tuesday, February 09, 2010 12:26 PM
> To: Templin, Fred L
> Cc: Dan Wing; behave@ietf.org
> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>=20
> On 9 feb 2010, at 20:10, Templin, Fred L wrote:
>=20
> > Another concern I should have called out earlier is what
> > if the IPv6 host is on a 1500 link and opens a TCP
> > connection to the IPv4 server with MSS=3D1440. The IPv4
> > server sends a 1480b IPv4 packet that gets translated
> > into a 1500b IPv6 packet. The packet makes its way
> > through the IPv6 network toward the IPv6 host, but
> > first it hits a 1480 MTU link (e.g., and IPv6 over IPv4
> > tunnel). The ICMPv6 PTB gets triggered, then translated
> > into ICMPv4 fragmentation needed, then dropped by
> > a filtering gateway in the IPv4 Internet.
>=20
> > Black hole, right?
>=20
> Indeed. Note however that the same black hole would exist if both ends ar=
e IPv6 or both ends are IPv4
> and there is no translator.

Eh? For IPv6<->IPv6, we have been assured that PMTUD
is fixed. Is that not the case?

Also, for IPv4-to-IPv4 we have the convenient fact that
links with MTU<1500 are rare in the Internet core so
tripping over a low MTU link is a rare event. Granted
that does not get us on the path to 9KB MTUs, but at
least it works in some fashion through good fortune.

> I don't think we can reasonably expect NAT64s to fix all possible black
> holes.

It's not a matter of fixing all black holes; it is
rather an analysis of what new sorts of black holes
are made possible when translators are used.

> In practice, I think NAT64 users would have to avoid reduced MTUs between=
 the translator and the IPv6
> hosts (and I would assume that a deployment that needs NAT64 is far enoug=
h along that it doesn't need
> IPv6-in-IP tunneling)

AFAICT, it may still be some time before ISP networks can
enable ubiquitous native IPv6. For those that can't there
is IPv6-in-IPv4 tunneling for the near term. Does that
mean that those ISPs can't deploy translators?

> or artificially lower the IPv6 host MTU or the translator MTU / rewrite t=
he MSS
> if a reduced MTU is present between the translator and the IPv6 hosts.

Artificially lowering the IPv6 host MTU may be unsatisfactory
if the host is connected to a network where it could otherwise
be using larger packet sizes. And, MSS clamping only works
for TCP.

Fred
fred.l.templin@boeing.com

From remi.despres@free.fr  Tue Feb  9 13:13:09 2010
Return-Path: <remi.despres@free.fr>
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 7B1203A760A; Tue,  9 Feb 2010 13:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 8hT0thi2jkH7; Tue,  9 Feb 2010 13:13:08 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id B90FF3A75FA; Tue,  9 Feb 2010 13:13:06 -0800 (PST)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id AA771E0806A; Tue,  9 Feb 2010 22:14:08 +0100 (CET)
Received: from [192.168.0.10] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 59F02E08115; Tue,  9 Feb 2010 22:14:05 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <069e01caa9c6$3b575b80$c4f0200a@cisco.com>
Date: Tue, 9 Feb 2010 22:14:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A0FCB3E-AA6A-4DED-8EE9-4F1897137ADA@free.fr>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com><F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com><E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com> <9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr> <069e01caa9c6$3b575b80$c4f0200a@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1077)
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 09 Feb 2010 21:13:09 -0000

Dan,

There must have been a confusion: I am AGAINST IPv6 PTB messages with =
MTU<1280.
(Your last message, addressed to both Fred and me suggests you believe I =
support them.)

My personal point is AGAINST networks purposely losing "normal" PTB =
error messages, i.e. with MTB>1280.

Considering that these losses become a MAY, even in IPv6, just because =
it is believed that some networks lose them would be IMHO a mistake, at =
least without a good understanding of where and why it is done.=20

Regards,

RD

=20

Le 9 f=E9vr. 2010 =E0 21:26, Dan Wing a =E9crit :


>> -----Original Message-----
>> From: softwires-bounces@ietf.org=20
>> [mailto:softwires-bounces@ietf.org] On Behalf Of R=E9mi Despr=E9s
>> ...
>> In IPv6, I hope it will be possible to agree at least that=20
>> PTB messages SHOULD be forwarded (if not MUST).
>> Reasons to not agree should IMHO be seriously documented.
>=20
> Ben Stasiewicz's tests [*] on the IPv6 Internet show that 56% of
> IPv6 hosts do not properly respond to ICMPv6 packet-too-big
> with an MTU<1280.

Not related to the point I made.=20

>  I do not believe additional MUSTs in RFCs=20
> from the IETF would have a noticeable effect.

A SHOULD is the proposal.
AFAIK it is not written anywhere that networks are authorized to do =
otherwise.




From joelja@bogus.com  Tue Feb  9 14:21:56 2010
Return-Path: <joelja@bogus.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 54AB03A6E17 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 14:21:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 FSfPNBBb8vm3 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 14:21:54 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [147.28.0.81]) by core3.amsl.com (Postfix) with ESMTP id D23513A7417 for <behave@ietf.org>; Tue,  9 Feb 2010 14:21:54 -0800 (PST)
Received: from [10.192.0.252] ([206.132.194.20]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id o19MLscp081924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Feb 2010 22:22:38 GMT (envelope-from joelja@bogus.com)
Message-ID: <4B71E002.9090502@bogus.com>
Date: Tue, 09 Feb 2010 14:21:54 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8	593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@	it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1	1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F	0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci	sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boein	g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com>	<E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com>	<035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Tue, 09 Feb 2010 22:22:39 +0000 (UTC)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 22:21:56 -0000

Templin, Fred L wrote:
> Dan,
> 
> About the placement of the translator, in the IPv6->IPv4
> direction the packet incurs a size reduction due to the
> substitution of an IPv4 header in place of the IPv6 header.
> In the IPv4->IPv6 direction, however, the size of the packet
> is inflated. So, e.g., if the translator receives a 1500byte
> IPv4 packet and has to translate it into a 1520byte IPv6
> packet, there is a chance that it may be dropped due to a
> link MTU restriction somewhere in the IPv6 network and an
> ICMPv6 PTB sent back toward the translator. Presumably, the
> translator would translate that into an ICMPv4 PTB message
> that it forwards on to the IPv4 host.
> 
> If I have that right, there may be a concern for whether
> the ICMPv4 PTB would be dropped in the IPv4 network before
> it arrives at the IPv4 host. I ran some tests and found
> that path MTU discovery in IPv4 seems to be problematic
> for a substantial number of the top 1000 websites:
> 
> http://www.ietf.org/mail-archive/web/rrg/current/msg05907.html
> 
> This suggests to me that path MTU discovery in the IPv4
> network "works" simply because it is rarely invoked. In
> other words, the IPv4 network seems to be getting by
> based on the good fortune that most links in the Internet
> core configure an MTU of 1500 or larger. But, this state
> of affairs may be disrupted if more and more translators
> are used that cause IPv4 packets to be inflated in size
> after they are translated into IPv6 packets.

well note that as (rfc 2923) observes and some platforms implement pmtu
black -hole avoidance which involves dropping back to 576 (rfc 791).
Appart from being kind of suboptimal that will work in places where
pmutd won't such as when you have a 9k mtu on your nic, but need to talk
to a printer on the same subnet.

> So, if the translator were located at the site border of
> the IPv4 host (i.e., rather than at the site border of
> the IPv6 host) the bulk of the path would be over IPv6
> instead of IPv4, hence the incidence of ICMPv4 filtering
> would be isolated to the end site of the IPv4 host.
> 
> Has the translator deployment analysis taken IPv4 path
> MTU-related black holing into consideration?
> 
> Fred
> fred.l.templin@boeing.com  
> 
>> -----Original Message-----
>> From: Dan Wing [mailto:dwing@cisco.com]
>> Sent: Monday, February 08, 2010 5:16 PM
>> To: Templin, Fred L; 'Iljitsch van Beijnum'
>> Cc: behave@ietf.org
>> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>>
>>
>>
>>> -----Original Message-----
>>> From: behave-bounces@ietf.org
>>> [mailto:behave-bounces@ietf.org] On Behalf Of Templin, Fred L
>>> Sent: Monday, February 08, 2010 5:11 PM
>>> To: Dan Wing; 'Iljitsch van Beijnum'
>>> Cc: behave@ietf.org
>>> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>>>
>>> Dan,
>>>
>>>> -----Original Message-----
>>>> From: behave-bounces@ietf.org
>>> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
>>>> Sent: Monday, February 08, 2010 4:24 PM
>>>> To: Templin, Fred L; 'Iljitsch van Beijnum'
>>>> Cc: behave@ietf.org
>>>> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
>>>>> Sent: Monday, February 08, 2010 4:02 PM
>>>>> To: Dan Wing; 'Iljitsch van Beijnum'
>>>>> Cc: behave@ietf.org
>>>>> Subject: RE: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>>>>>
>>>>> The concern with setting DF=0 on the IPv4 side for packets
>>>>> that are 1280 or smaller on the IPv6 side is the possibility
>>>>> for RFC4963 data corruption if we let it run at line rate.
>>>> At high speed with the same source/destination addresses, and when
>>>> fragmentation on the IPv4 network occurs.  That is, sending
>>> lots of packets
>>>> with DF=0 does not, by itself, cause a problem even if they
>>> are fragmented on
>>>> the same link -- so long as they have different source or different
>>>> destination addresses.  I agree we should make a note of that.
>>> Yes, the concern is for same src,dst operating at line
>>> rate. IPv6 apps assume that there is no possibility for
>>> fragmentation in the network, hence they may not be as
>>> shy as IPv4 apps when it comes to sending large packets
>>> at high data rates. Having the translator set DF=0 can
>>> break that assumption.
>> There are three approaches discussed in new text in
>> http://tools.ietf.org/html/draft-ietf-behave-v6v4-xlate-08#page-18,
>> which only set DF=0 for "small packets" (packets that were
>> less than 1280 on the IPv6 side).
>>
>> I don't think that eliminates your concern, though.
>>
>>>> Is there another approach that should be considered to
>>>> avoid that concern?
>>> I still believe placement of the translator matters.
>>> Placing the translator closer to the IPv4 host
>>> reduces the portion of the path that is exposed to
>>> IPv4 hops. This is true whether the DF=0 or DF=1
>>> approach is used.
>> Agreed.
>>
>> However, that isn't always possible.  For example,
>> someone operating an IPv6-only network will have to
>> place their IPv6/IPv4 translator at their network
>> border.
>>
>> But perhaps some text could be added to
>> draft-ietf-behave-v6v4-xlate which highlighted
>> this recommendation to place the translator as
>> close to the IPv4 host as possible.  Or, similarly,
>> to ensure the IPv4 network has an MTU greater than
>> 1280 (minus whatever the IPv6/IPv4 header differences
>> are).
>>
>> -d
>>
>>
>>> Fred
>>> fred.l.templin@boeing.com
>>>
>>>>> There are certainly plenty of websites on the IPv4 Internet
>>>>> that set DF=0 on every packet they send, and many even use
>>>>> packet sizes larger than 1280. But, how many of them send
>>>>> large packets at line rate?
>>>> Content delivery networks?
>>>>
>>>> -d
>>>>
>>>>
>>>>> Fred
>>>>> fred.l.templin@boeing.com
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: behave-bounces@ietf.org
>>>>> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
>>>>>> Sent: Monday, February 08, 2010 3:29 PM
>>>>>> To: 'Iljitsch van Beijnum'
>>>>>> Cc: behave@ietf.org
>>>>>> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
>>>>>>> Sent: Monday, February 08, 2010 3:02 PM
>>>>>>> To: Dan Wing
>>>>>>> Cc: 'marcelo bagnulo braun'; behave@ietf.org
>>>>>>> Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280
>>> byte packets
>>>>>>> On 8 feb 2010, at 23:34, Dan Wing wrote:
>>>>>>>
>>>>>>>>> So essentially this means doing more work (keeping PMTUD
>>>>>>>>> state for the IPv4 path) in order to do even more
>>> work later
>>>>>>>>> (fragment). Not sure how that makes sense...
>>>>>>>> Yes, it means the translator is doing the effort of
>>> fragmenting
>>>>>>>> rather than the router immediately in front of the small-MTU
>>>>>>>> link.  However, by doing it this way, we can
>>> maintain end-to-end
>>>>>>>> PMTUD for those IPv6 hosts that receive ICMPv6 PTB and send
>>>>>>>> packets with the fragmentation header.
>>>>>>> No, the two issues are orthogonal.
>>>>>>>
>>>>>>> At some point, an IPv6 host sends a packet that is larger
>>>>>>> than the IPv4 PMTU. A router sends back a too big message.
>>>>>>> Issue A is how to handle this too big message. Issue B is
>>>>>>> what happens to packets that the IPv6 host subsequently sends.
>>>>>> A stateless translator cannot identify 'subsequent' packets,
>>>>>> because it doesn't remember previous state.
>>>>>>
>>>>>>> I think there is agreement that A should be handled by simply
>>>>>>> translating the IPv4 too big too IPv6 and adjusting it as per
>>>>>>> the header size differences, but otherwise let it through
>>>>>>> transparently. (I once argued for rewriting it to
>>> 1280, though.)
>>>>>>> Nothing has changed here.
>>>>>>>
>>>>>>> But now for part B. A stateless translator can't monitor the
>>>>>>> IPv4 PMTU. Not because it's stateful (we're talking per
>>>>>>> destination state, not per session state, it would be doable
>>>>>>> to track this) but because there may be more than one
>>>>>>> translator so any given translator may not see all packets.
>>>>>>> So for stateless translation when the translator has a < 1280
>>>>>>> packet with no fragment header we don't know whether this is
>>>>>>> because PMTUD was succesful and the packet size fits in the
>>>>>>> PMTU, or the IPv6 host ignored the < 1280 too big message and
>>>>>>> is omitting the fragment header in violation of the relevant
>>>>>>> RFCs. In order to be compatible with the latter the only
>>>>>>> thing we can do is set DF to 0.
>>>>>>>
>>>>>>> (I just realize that we don't know what happens when for
>>>>>>> instance the PMTU is 1000 and the IPv6 host wants to send a
>>>>>>> 1100-byte packet: does it include a fragment header or not?)
>>>>>>>
>>>>>>> Note that for part B, if there _is_ a fragment header, that
>>>>>>> will also trigger the translator to set DF to 0. So in the
>>>>>>> case where the IPv6 hosts are well behaved there is no change
>>>>>>> to either parts A or B.
>>>>>> So, I believe we are in agreement:  IPv6 packets less than
>>>>>> 1280 need to be translated to IPv4 and sent with DF=0.
>>>>>>
>>>>>>> In the stateful case we know all packets flow through the
>>>>>>> same translator so we get to track the IPv4 PMTU so when
>>>>>>> there is an IPv6 packet that needs to be translated we know
>>>>>>> whether it's bigger or smaller than the PMTU so we can send
>>>>>>> packets that are bigger with DF=1 and packets that are
>>>>>>> smaller with DF=0 and if we are to, also immediately fragment
>>>>>>> them. However, there is no advantage to doing this extra work
>>>>>>> because even if we get to set DF=1 on some packets that are
>>>>>>> smaller than the PMTU that only lets us discover a reduction
>>>>>>> in the PMTU, but that discovery doesn't buy us anything
>>>>>>> because the IPv6 host isn't going to reduce its packet size.
>>>>>> I agree the IPv6 host won't reduce its packet size below
>>>>>> 1280.  But the IPv6 host becomes aware that the path MTU
>>>>>> is smaller than 1280.  I don't know if the IPv6 host finds
>>>>>> that useful/valuable to know the path MTU is less than the
>>>>>> IPv6 minimum MTU.
>>>>>>
>>>>>>> Fragmenting at the translator also doesn't buy the translator
>>>>>>> anything and it may even get the packet blocked or create
>>>>>>> more work if there's a firewall with a > 1280 MTU before the
>>>>>>> path hits the < 1280 MTU which would need to reassemble the
>>>>>>> packet to observe the port numbers. And it could be an attack
>>>>>>> vector: attackers could send too bigs with tiny MTUs to make
>>>>>>> the translator work harder.
>>>>>>>
>>>>>>>> Certainly there was some
>>>>>>>> perceived value in the IPv6 knowing its packets are being
>>>>>>>> fragmented.
>>>>>>> I don't think so. Even if the application somehow learns this
>>>>>>> information, what is it supposed to do then?
>>>>>> Don't know.  It is obviously easier for the 6/4 translator to
>>>>>> simply fragment the packet (or translate and send with
>>> DF=0) without
>>>>>> informing the IPv6 host, but there is long-standing text in both
>>>>>> RFC2460 and its predecessor (RFC1883) that says to send back
>>>>>> ICMPv6 PTB and the IPv6 host is then supposed to send packets
>>>>>> with the fragmentation header.
>>>>>>
>>>>>>>> I agree that nearly 100% of PMTUD on IPv4 is with TCP.
>>>>>>>> But there isn't anything prohibiting PMTUD for UDP.
>>>>>>> With sufficient thrust pigs fly just fine...
>>>>>>>
>>>>>>> Generally, it's not easy for UDP applications to limit their
>>>>>>> packet sizes. So the protocol would have to support changing
>>>>>>> the packet size on the fly and then the application would
>>>>>>> have to react to too big messages.
>>>>>> draft-petithuguenin-behave-stun-pmtud does not rely on
>>>>>> ICMP packet too big messages.
>>>>>>
>>>>>>> Not impossible, but I've never seen it happen.
>>>>>> Me, neither.  I'm just trying to temper the "only TCP does
>>>>>> PMTUD", because UDP can do PMTUD.  And of course there is value
>>>>>> in sending the largest packets possible.
>>>>>>
>>>>>>> But if BitTorrent goes to UDP it's
>>>>>>> likely they'll put this in in some way.
>>>>>> As of version 2.x, the most popular BitTorrent client on
>>>>>> Windows (uTorrent) has implemented uTP, for whatever that's
>>>>>> worth.  I don't know if they're doing PMTUD, though.  Beta
>>>>>> versions of uTorrent are available for OSX, too, and I expect
>>>>>> they will soon support uTP (if they aren't already).
>>>>>>
>>>>>>>> I tend to think, though, we don't want to figure this out
>>>>>>>> for stateful translators at this point in time.  If it is
>>>>>>>> found useful/necessary, it can be specified later.
>>>>>>> Right.=
>>>>>> -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
>>> _______________________________________________
>>> 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 iljitsch@muada.com  Tue Feb  9 14:54:46 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 C8F0828C168 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 14:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, J_BACKHAIR_44=1]
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 EFtuEyo4ZBP9 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 14:54:46 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 9AC533A7636 for <behave@ietf.org>; Tue,  9 Feb 2010 14:54:45 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o19MsOU5042209 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 23:54:25 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951038309@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 9 Feb 2010 23:55:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <27AF6467-B1E0-4FB1-AE8D-DB9529AB4B89@muada.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8 593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007 @ it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B1 1A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7 F 0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@ci sco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boei n g.com><032d01caa91e$343c71d0$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com> <035601caa925$800f2240$c4f0200a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com> <055401caa9b3$02d42c60$c4f0200a@cisco.com> <0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103824D@XCH-NW-01V.nw.nos.boeing.com> <D6D71E40-644D-4D1C-B535-A31AAD0C7589@muada.com> <E1829B60731D1740BB7A0626B4FAF0A6495103828D@XCH-NW-01V.nw.nos.boeing.com> ! <5B264313-3BE0-4C44-9BD3-718FC6F8A9E5@muada.com> <E1829B60731D1740BB7A0626B4FAF0A64951038309@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 22:54:46 -0000

On 9 feb 2010, at 21:48, Templin, Fred L wrote:

>> Indeed. Note however that the same black hole would exist if both =
ends are IPv6 or both ends are IPv4 and there is no translator.

> Eh? For IPv6<->IPv6, we have been assured that PMTUD
> is fixed. Is that not the case?

Fixed how? I know Microsoft has PMTUD blackhole detection and maybe =
others as well, but that has nothing to do with IPv6. I've had my share =
of black holes with IPv6, although not recently.

> Also, for IPv4-to-IPv4 we have the convenient fact that
> links with MTU<1500 are rare in the Internet core so
> tripping over a low MTU link is a rare event.

PPP over ethernet is pretty common with ADSL and reduces a user's MTU =
below 1500, usually without the hosts knowing it. This is solved with =
adjusting (clamping) the value in the MSS option.

> Granted that does not get us on the path to 9KB MTUs,

Like I said before, you can do this without trouble. I didn't even =
mention the MSS, which will save you if there's a network in the middle =
that doesn't generate too bigs correctly.

>> I don't think we can reasonably expect NAT64s to fix all possible =
black
>> holes.

> It's not a matter of fixing all black holes; it is
> rather an analysis of what new sorts of black holes
> are made possible when translators are used.

Right. But your example wasn't very particular to the translation case.

>> In practice, I think NAT64 users would have to avoid reduced MTUs =
between the translator and the IPv6
>> hosts (and I would assume that a deployment that needs NAT64 is far =
enough along that it doesn't need
>> IPv6-in-IP tunneling)

> AFAICT, it may still be some time before ISP networks can
> enable ubiquitous native IPv6. For those that can't there
> is IPv6-in-IPv4 tunneling for the near term.

What kind of tunneling do you foresee? Obviously not 6to4. Other types =
of tunneling are more complex, native IPv6 makes life much simpler.

> Does that mean that those ISPs can't deploy translators?

No:

>> or artificially lower the IPv6 host MTU or the translator MTU / =
rewrite the MSS
>> if a reduced MTU is present between the translator and the IPv6 =
hosts.

> Artificially lowering the IPv6 host MTU may be unsatisfactory
> if the host is connected to a network where it could otherwise
> be using larger packet sizes. And, MSS clamping only works
> for TCP.

If you have a better solution I'm all ears.=

From joelja@bogus.com  Tue Feb  9 15:30:54 2010
Return-Path: <joelja@bogus.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 49C8D3A67B4 for <behave@core3.amsl.com>; Tue,  9 Feb 2010 15:30:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  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 cdjYkzRa4yWE for <behave@core3.amsl.com>; Tue,  9 Feb 2010 15:30:53 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [147.28.0.81]) by core3.amsl.com (Postfix) with ESMTP id 468903A74C1 for <behave@ietf.org>; Tue,  9 Feb 2010 15:30:53 -0800 (PST)
Received: from [10.192.0.252] ([206.132.194.20]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id o19NVDiN085619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Feb 2010 23:31:58 GMT (envelope-from joelja@bogus.com)
Message-ID: <4B71F040.9000305@bogus.com>
Date: Tue, 09 Feb 2010 15:31:12 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <4B6F08CC.2070900@wand.net.nz>	<063A973F-EBC3-4CD0-B5B6-B0FB42A8593D@muada.com><00f201caa8da$b78e3e90$c4f0200a@cisco.com><4B704153.2020007@it.uc3m.es><015801caa8e6$9b72fff0$c4f0200a@cisco.com><75A95C0D-E2CC-4FD6-B11A-5C772FCD0F5C@muada.com><02cd01caa90e$dde921c0$c4f0200a@cisco.com><B50C7F0A-19DB-4C63-9F72-867B5C2D4841@muada.com><02f101caa916$712d0170$c4f0200a@cisco.com><E1829B60731D1740BB7A0626B4FAF0A64951038053@XCH-NW-01V.nw.nos.boeing.com><032d01caa91e$343c71d0$c4f0200a@cisco.com>	<E1829B60731D1740BB7A0626B4FAF0A64951038079@XCH-NW-01V.nw.nos.boeing.com>	<035601caa925$800f2240$c4f0200a@cisco.com>	<E1829B60731D1740BB7A0626B4FAF0A649510381E7@XCH-NW-01V.nw.nos.boeing.com>	<055401caa9b3$02d42c60$c4f0200a@cisco.com>	<0F11A6F7-69E0-4B4E-AB23-C74779370973@muada.com> <05b401caa9b8$c215ddd0$c4f0200a@cisco.com>
In-Reply-To: <05b401caa9b8$c215ddd0$c4f0200a@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Tue, 09 Feb 2010 23:31:59 +0000 (UTC)
Cc: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, behave@ietf.org
Subject: Re: [BEHAVE] Fwd: IPv6 hosts sending <1280 byte packets
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, 09 Feb 2010 23:30:54 -0000

Dan Wing wrote:
>> Only in the case where the IPv6 host supports an MTU larger than
>> 1500 but the translator doesn't, there is a possible optimization
>> by having the translator rewrite the MSS to the maximum that the
>> translator supports so the translator wouldn't have to send too
>> bigs and there is less risk of PMTUD black holes. However, it's not
>> clear to me that this case is worth the trouble.
> 
> There are long-standing desires to MTUs larger than 1500 with IPv6,
> under the theory that IPv6 Did Things Correctly.

There are longing standing desires for the same under ipv4... ;)

it even works some of the time, and sometimes pmtud works, sometimes
it doesn't.

my first experience with end-to-end 9k mtu's across the internet was
over a decade ago. Things have gotten a little better since then I
guess, or not.

From dwing@cisco.com  Tue Feb  9 17:05:22 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 2A57E3A7646; Tue,  9 Feb 2010 17:05:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.544
X-Spam-Level: 
X-Spam-Status: No, score=-10.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 rpLEL1DSqjsU; Tue,  9 Feb 2010 17:05:21 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 552AD3A74DA; Tue,  9 Feb 2010 17:05:21 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokGAM+UcUurRN+J/2dsb2JhbACHUYESkgJ0pVCKSI1qhFQE
X-IronPort-AV: E=Sophos;i="4.49,439,1262563200"; d="scan'208";a="238957478"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-2.cisco.com with ESMTP; 10 Feb 2010 01:06:29 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1A16TJu013347; Wed, 10 Feb 2010 01:06:29 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <mcr@sandelman.ca>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com><F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com><E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com> <9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr> <069e01caa9c6$3b575b80$c4f0200a@cisco.com> <27565.1265748903@marajade.sandelman.ca>
Date: Tue, 9 Feb 2010 17:06:29 -0800
Message-ID: <07c001caa9ed$470cb980$c4f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <27565.1265748903@marajade.sandelman.ca>
Thread-Index: Acqpyi0u4YQOqBWxSHesVTKkw0TIQAAIvuig
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] PMTU Discovery and ICMPv6 filtering
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, 10 Feb 2010 01:05:22 -0000

> >>>>> "Dan" == Dan Wing <dwing@cisco.com> writes:
>     >> In IPv6, I hope it will be possible to agree at least that PTB
>     >> messages SHOULD be forwarded (if not MUST).  Reasons 
> to not agree
>     >> should IMHO be seriously documented.
> 
>     Dan> Ben Stasiewicz's tests [*] on the IPv6 Internet show that 56%
>     Dan> of IPv6 hosts do not properly respond to ICMPv6 
> packet-too-big
>     Dan> with an MTU<1280.  I do not believe additional MUSTs in RFCs
>     Dan> from the IETF would have a noticeable effect.
> 
> We need to push out plpmtud.

I agree with you.  But that isn't in scope for BEHAVE or SOFTWIRE.  Perhaps
TCPM, maybe; I'm not sure.

-d


> 
> -- 
> ]       He who is tired of Weird Al is tired of life!         
>   |  firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON  
>   |net architect[
> ] mcr@sandelman.ottawa.on.ca 
> http://www.sandelman.ottawa.on.ca/ |device driver[
>    Kyoto Plus: watch the video 
> <http://www.youtube.com/watch?v=kzx1ycLXQSE>
> 	               then sign the petition. 


From dwing@cisco.com  Tue Feb  9 17:16:06 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 6166628C25F; Tue,  9 Feb 2010 17:16:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level: 
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 WyBmJvfPI16o; Tue,  9 Feb 2010 17:16:04 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id BC69C28C25E; Tue,  9 Feb 2010 17:16:04 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokGACKYcUurRN+J/2dsb2JhbACHUYESkgJ0pWKYL4RUBA
X-IronPort-AV: E=Sophos;i="4.49,439,1262563200"; d="scan'208";a="297643895"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-1.cisco.com with ESMTP; 10 Feb 2010 01:17:10 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1A1HA5D024466; Wed, 10 Feb 2010 01:17:10 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com><F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com><E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com><9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr><069e01caa9c6$3b575b80$c4f0200a@cisco.com> <8A0FCB3E-AA6A-4DED-8EE9-4F1897137ADA@free.fr>
Date: Tue, 9 Feb 2010 17:17:09 -0800
Message-ID: <07c601caa9ee$c4d144c0$c4f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <8A0FCB3E-AA6A-4DED-8EE9-4F1897137ADA@free.fr>
Thread-Index: AcqpzNlxXCEv7rsCT2agMu8AANfMTgAIHKOQ
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 10 Feb 2010 01:16:06 -0000

=20

> -----Original Message-----
> From: behave-bounces@ietf.org=20
> [mailto:behave-bounces@ietf.org] On Behalf Of R=E9mi Despr=E9s
> Sent: Tuesday, February 09, 2010 1:14 PM
> To: Dan Wing
> Cc: softwires@ietf.org; 'Templin, Fred L'; 'Behave WG'
> Subject: Re: [BEHAVE] [Softwires] PMTU Discovery and ICMPv6 filtering
>=20
> Dan,
>=20
> There must have been a confusion: I am AGAINST IPv6 PTB=20
> messages with MTU<1280.
> (Your last message, addressed to both Fred and me suggests=20
> you believe I support them.)

Sorry if I mis-characterized.

> My personal point is AGAINST networks purposely losing=20
> "normal" PTB error messages, i.e. with MTB>1280.
>=20
> Considering that these losses become a MAY, even in IPv6,=20
> just because it is believed that some networks lose them=20
> would be IMHO a mistake, at least without a good=20
> understanding of where and why it is done.=20

Remi,

I can tell I'm not fully understanding what you're saying.  But perhaps =
if you
read=20
Ben Stasiewicz's analysis of ICMPv6 PTB with MTU=3D1280, you'll be =
happier -- it
shows much higher sucess than his later tests using MTU<1280.  His =
MTU=3D1280
test is at:

http://listserver.internetnz.net.nz/pipermail/ipv6-techsig/2009-October/0=
00708
.html

-d


> Regards,
>=20
> RD
>=20
> =20
>=20
> Le 9 f=E9vr. 2010 =E0 21:26, Dan Wing a =E9crit :
>=20
>=20
> >> -----Original Message-----
> >> From: softwires-bounces@ietf.org=20
> >> [mailto:softwires-bounces@ietf.org] On Behalf Of R=E9mi Despr=E9s
> >> ...
> >> In IPv6, I hope it will be possible to agree at least that=20
> >> PTB messages SHOULD be forwarded (if not MUST).
> >> Reasons to not agree should IMHO be seriously documented.
> >=20
> > Ben Stasiewicz's tests [*] on the IPv6 Internet show that 56% of
> > IPv6 hosts do not properly respond to ICMPv6 packet-too-big
> > with an MTU<1280.
>=20
> Not related to the point I made.=20
>=20
> >  I do not believe additional MUSTs in RFCs=20
> > from the IETF would have a noticeable effect.
>=20
> A SHOULD is the proposal.
> AFAIK it is not written anywhere that networks are authorized=20
> to do otherwise.
>=20
>=20
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From kivinen@iki.fi  Tue Feb  9 06:02:05 2010
Return-Path: <kivinen@iki.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 5AA963A7590; Tue,  9 Feb 2010 06:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101,  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 8a9GgFxOWYS2; Tue,  9 Feb 2010 06:02:03 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by core3.amsl.com (Postfix) with ESMTP id D0D5728C1FE; Tue,  9 Feb 2010 06:02:02 -0800 (PST)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.3/8.14.3) with ESMTP id o19E30g2007817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 16:03:00 +0200 (EET)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id o19E2wON006926; Tue, 9 Feb 2010 16:02:58 +0200 (EET)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19313.27410.93467.295717@fireball.kivinen.iki.fi>
Date: Tue, 9 Feb 2010 16:02:58 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com>
References: <4B69B06D.7080606@sri.com> <E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com> <F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com> <E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 12 min
X-Total-Time: 11 min
X-Mailman-Approved-At: Tue, 09 Feb 2010 18:33:14 -0800
Cc: "softwires@ietf.org" <softwires@ietf.org>, Behave WG <behave@ietf.org>, Ed Jankiewicz <edward.jankiewicz@sri.com>, Dave Dolson <ddolson@sandvine.com>
Subject: Re: [BEHAVE] [Softwires]  PMTU Discovery and ICMPv6 filtering
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, 09 Feb 2010 14:02:05 -0000

Templin, Fred L writes:
> > I believe this is referring to mapping of ICMP "too big" messages. When
> > a tunnel end-point receives a "too big" message, it would have to map
> > the message to an ICMP message for the original host. I believe this
> > could be done in a stateless manner using the packet quoted in the
> > message. (RFC2463 says the "too big" message will include "As much of
> > invoking packet as will fit without the ICMPv6 packet exceeding the
> > minimum IPv6 MTU")
> 
> But, if the packet-in-error encapsulated in the ICMP
> PTB message is encrypted and not complete (i.e., only
> the leading 1200 or so bytes of the encrypted packet
> are included), how will the tunnel ingress know how to
> decrypt it in order to do the stateless translation?

If we are talking about IPsec, then that ICMP packet will have the SPI
of the packet, so the gateway can find the related IPsec SA for the
the packet which caused the PTB message to be sent. After that it
simply stores the maximum path MTU it got from the ICMP message to the
IPsec SA.

When the next packet comes through which is bigger than what the MTU
stored for the SA (where the MTU is already modified accordingly to
match the overhead of IPsec headers), it will directly send PTB
message back to the original sender of the packet.

I.e. it will dynamically find out the PMTU for each IPsec SA (taking
the overhead in to account, as it does know the overhead), and then
send PTB messages if packet is bigger than that.

See section 8.2.1 of RFC4301:
----------------------------------------------------------------------
8.2.1.  Propagation of PMTU

   When an IPsec implementation receives an unauthenticated PMTU
   message, and it is configured to process (vs. ignore) such messages,
   it maps the message to the SA to which it corresponds.  This mapping
   is effected by extracting the header information from the payload of
   the PMTU message and applying the procedure described in Section 5.2.
   The PMTU determined by this message is used to update the SAD PMTU
   field, taking into account the size of the AH or ESP header that will
   be applied, any crypto synchronization data, and the overhead imposed
   by an additional IP header, in the case of a tunnel mode SA.

   In a native host implementation, it is possible to maintain PMTU data
   at the same granularity as for unprotected communication, so there is
   no loss of functionality.  Signaling of the PMTU information is
   internal to the host.  For all other IPsec implementation options,
   the PMTU data must be propagated via a synthesized ICMP PMTU.  In
   these cases, the IPsec implementation SHOULD wait for outbound
   traffic to be mapped to the SAD entry.  When such traffic arrives, if
   the traffic would exceed the updated PMTU value the traffic MUST be
   handled as follows:

       Case 1: Original (cleartext) packet is IPv4 and has the DF
               bit set.  The implementation SHOULD discard the packet
               and send a PMTU ICMP message.

       Case 2: Original (cleartext) packet is IPv4 and has the DF
               bit clear.  The implementation SHOULD fragment (before or
               after encryption per its configuration) and then forward
               the fragments.  It SHOULD NOT send a PMTU ICMP message.

       Case 3: Original (cleartext) packet is IPv6.  The implementation
               SHOULD discard the packet and send a PMTU ICMP message.
-- 
kivinen@iki.fi

From mcr@sandelman.ca  Tue Feb  9 12:53:58 2010
Return-Path: <mcr@sandelman.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 87C223A71C3; Tue,  9 Feb 2010 12:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[AWL=1.254,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, 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 H-otZRQROhWk; Tue,  9 Feb 2010 12:53:57 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by core3.amsl.com (Postfix) with ESMTP id 969D53A6C7E; Tue,  9 Feb 2010 12:53:57 -0800 (PST)
Received: from sandelman.ottawa.on.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id B8C9934351; Tue,  9 Feb 2010 15:48:59 -0500 (EST)
Received: from marajade.sandelman.ca (unknown [127.0.0.1]) by sandelman.ottawa.on.ca (Postfix) with ESMTP id D50C34E7F6; Tue,  9 Feb 2010 15:55:03 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <069e01caa9c6$3b575b80$c4f0200a@cisco.com> 
References: <4B69B06D.7080606@sri.com><E1829B60731D1740BB7A0626B4FAF0A64951037BF6@XCH-NW-01V.nw.nos.boeing.com><F489AB573A749146B33461ECE080913A0D7DEE36@EXCHANGE-1.sandvine.com><E1829B60731D1740BB7A0626B4FAF0A64951037F71@XCH-NW-01V.nw.nos.boeing.com> <9B8CB322-5464-473A-A3C8-77425376CA4F@free.fr> <069e01caa9c6$3b575b80$c4f0200a@cisco.com> 
X-Mailer: MH-E 8.1; nmh 1.1; XEmacs 21.4 (patch 21)
Date: Tue, 09 Feb 2010 15:55:03 -0500
Message-ID: <27565.1265748903@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-Mailman-Approved-At: Tue, 09 Feb 2010 18:33:20 -0800
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] PMTU Discovery and ICMPv6 filtering
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, 09 Feb 2010 20:53:58 -0000

>>>>> "Dan" == Dan Wing <dwing@cisco.com> writes:
    >> In IPv6, I hope it will be possible to agree at least that PTB
    >> messages SHOULD be forwarded (if not MUST).  Reasons to not agree
    >> should IMHO be seriously documented.

    Dan> Ben Stasiewicz's tests [*] on the IPv6 Internet show that 56%
    Dan> of IPv6 hosts do not properly respond to ICMPv6 packet-too-big
    Dan> with an MTU<1280.  I do not believe additional MUSTs in RFCs
    Dan> from the IETF would have a noticeable effect.

We need to push out plpmtud.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From iljitsch@muada.com  Tue Feb  9 23:18:53 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 239C828C0DD for <behave@core3.amsl.com>; Tue,  9 Feb 2010 23:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 CnWGctu6-ccx for <behave@core3.amsl.com>; Tue,  9 Feb 2010 23:18:51 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id B8BCE3A68D6 for <behave@ietf.org>; Tue,  9 Feb 2010 23:18:49 -0800 (PST)
Received: from [192.168.2.11] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o1A7Ieu8044668 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <behave@ietf.org>; Wed, 10 Feb 2010 08:18:41 +0100 (CET) (envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Feb 2010 08:19:52 +0100
Message-Id: <FB6800D2-6304-42E8-82C2-17D2D016EB81@muada.com>
To: "behave@ietf.org WG" <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
Subject: [BEHAVE] General PMTUD black hole detection in translators
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, 10 Feb 2010 07:18:53 -0000

If we want to avoid cases where there is a link with a reduced MTU =
between the IPv6 hosts and a translator that triggers path MTU discovery =
black holes towards certain IPv4 servers, we could add a form of PMTUD =
black hole detection to translators.

It would work like this: the translator of course translates too big =
messages from the IPv6 side to IPv4. If it remembers that it did this =
and then sees that the IPv4 host doesn't lower its packet sizes within a =
reasonable timeframe, it can then when new sessions are set up from the =
same IPv6 host towards the same IPv4 host, adjust the MSS to the value =
that was present in the earlier too big message.

So then the first TCP session would time out but subsequent ones would =
have their MSS clamped and those would work. This would only kick in =
when there is an actual black hole so there is no impact for well =
behaved systems. The initial session would still fail so there would =
still be good reason for PMTUD breakers to fix their systems, but after =
the initial failure, the user would have something that works.=

From dwing@cisco.com  Wed Feb 10 08:48:01 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 ACC4B3A73EF for <behave@core3.amsl.com>; Wed, 10 Feb 2010 08:48:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.545
X-Spam-Level: 
X-Spam-Status: No, score=-10.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 06P5Q-vOt4vk for <behave@core3.amsl.com>; Wed, 10 Feb 2010 08:48:00 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 9C30B28C118 for <behave@ietf.org>; Wed, 10 Feb 2010 08:48:00 -0800 (PST)
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: Am8IAMNyckurRN+K/2dsb2JhbACHUoESkXp0pE6XeIRVBA
X-IronPort-AV: E=Sophos;i="4.49,445,1262563200"; d="scan'208";a="85113425"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by rtp-iport-1.cisco.com with ESMTP; 10 Feb 2010 16:49:10 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1AGnAp6007581; Wed, 10 Feb 2010 16:49:10 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>, <behave@ietf.org>
References: <FB6800D2-6304-42E8-82C2-17D2D016EB81@muada.com>
Date: Wed, 10 Feb 2010 08:49:10 -0800
Message-ID: <09f701caaa70$f7d8a570$c4f0200a@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
In-Reply-To: <FB6800D2-6304-42E8-82C2-17D2D016EB81@muada.com>
Thread-Index: AcqqIXxTba6rUHa7RuSWSRpqxzBrBQATyxPQ
Subject: Re: [BEHAVE] General PMTUD black hole detection in translators
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, 10 Feb 2010 16:48:01 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Iljitsch van Beijnum
> Sent: Tuesday, February 09, 2010 11:20 PM
> To: behave@ietf.org WG
> Subject: [BEHAVE] General PMTUD black hole detection in translators
> 
> If we want to avoid cases where there is a link with a 
> reduced MTU between the IPv6 hosts and a translator that 
> triggers path MTU discovery black holes towards certain IPv4 
> servers, we could add a form of PMTUD black hole detection to 
> translators.
> 
> It would work like this: the translator of course translates 
> too big messages from the IPv6 side to IPv4. If it remembers 
> that it did this and then sees that the IPv4 host doesn't 
> lower its packet sizes within a reasonable timeframe, it can 
> then when new sessions are set up from the same IPv6 host 
> towards the same IPv4 host, adjust the MSS to the value that 
> was present in the earlier too big message.
> 
> So then the first TCP session would time out but subsequent 
> ones would have their MSS clamped and those would work. This 
> would only kick in when there is an actual black hole so 
> there is no impact for well behaved systems. The initial 
> session would still fail so there would still be good reason 
> for PMTUD breakers to fix their systems, but after the 
> initial failure, the user would have something that works.

Can we defer this to an improvement of the stateful translator?
This feels like it could be described in a new I-D describing 
how to best utilize a path's MTU using extra smarts in the 
translator.

If anyone feels this sort of behavior needs to be in the 
stateless or stateful I-Ds, please speak up now.

-d


> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From ajs@shinkuro.com  Wed Feb 10 12:12:08 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 8A2FE28C272 for <behave@core3.amsl.com>; Wed, 10 Feb 2010 12:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level: 
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[AWL=0.390,  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 Sb62bJxsXWBO for <behave@core3.amsl.com>; Wed, 10 Feb 2010 12:11:54 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id B90743A7794 for <behave@ietf.org>; Wed, 10 Feb 2010 12:11:43 -0800 (PST)
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 49DF41ECB4E8 for <behave@ietf.org>; Wed, 10 Feb 2010 20:12:54 +0000 (UTC)
Date: Wed, 10 Feb 2010 15:12:52 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100210201252.GS5187@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [BEHAVE] DNS64 and SRV records
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, 10 Feb 2010 20:12:08 -0000

Dear colleagues,

We have received an interesting observation from Rick van Rein about
the DNS64 draft.

The current draft says that DNS64 MUST NOT alter the Additional
section when assembling the answer.

Some records habitually include A and AAAA records in the Additional
section in order to allow a querying client to proceed without
querying again for the answer.  The particular case that troubles Rick
van Rein is the case of SRV records (but MX records and similar might
have this problem as well).

The RFC 2782 (which specifies the SRV RR) encourages servers to
include records in the additional section in order that targets of SRV
records can be resolved without additional queries.  It notes,
however, that clients cannot depend on there being data in the
Additional section, because the TTLs on (say) an SRV record and an A
record to match the target could be different; so an SRV might be
satisfied from cache without a corresponding A for the additional.

Now, suppose a client gets an SRV record with data in the additional
containing only A records.  Suppose also that the client has only IPv6
connectivity, so the A records do the client no good.

My reading is that the client _should_ go and query for the AAAA of
the target in the SRV record, because there's no data in the
additional section that will be useful to the client.  If the client
does this, it should end up with a synthetic AAAA as usual, and
everything will work.

The question is whether we know that there are clients that won't just
query for the AAAA.  If we do know of such clients, then the approach
currently in the draft won't work.  In that case, I propose changing
the draft to require the additional section to be truncated whenever
it does not contain at least one AAAA record.

Thoughts?

A

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

From marka@isc.org  Wed Feb 10 16:38:50 2010
Return-Path: <marka@isc.org>
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 6DE813A67B2 for <behave@core3.amsl.com>; Wed, 10 Feb 2010 16:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 DhyTjTRL4ig9 for <behave@core3.amsl.com>; Wed, 10 Feb 2010 16:38:48 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id E15C228C0EA for <behave@ietf.org>; Wed, 10 Feb 2010 16:38:46 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 9DE3DE60A9; Thu, 11 Feb 2010 00:39:56 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1B0dsRu092024; Thu, 11 Feb 2010 11:39:54 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002110039.o1B0dsRu092024@drugs.dv.isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
From: Mark Andrews <marka@isc.org>
References: <20100210201252.GS5187@shinkuro.com> 
In-reply-to: Your message of "Wed, 10 Feb 2010 15:12:52 CDT." <20100210201252.GS5187@shinkuro.com> 
Date: Thu, 11 Feb 2010 11:39:54 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] DNS64 and SRV records
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, 11 Feb 2010 00:38:50 -0000

In message <20100210201252.GS5187@shinkuro.com>, Andrew Sullivan writes:
> Dear colleagues,
> 
> We have received an interesting observation from Rick van Rein about
> the DNS64 draft.
> 
> The current draft says that DNS64 MUST NOT alter the Additional
> section when assembling the answer.
> 
> Some records habitually include A and AAAA records in the Additional
> section in order to allow a querying client to proceed without
> querying again for the answer.  The particular case that troubles Rick
> van Rein is the case of SRV records (but MX records and similar might
> have this problem as well).
> 
> The RFC 2782 (which specifies the SRV RR) encourages servers to
> include records in the additional section in order that targets of SRV
> records can be resolved without additional queries.  It notes,
> however, that clients cannot depend on there being data in the
> Additional section, because the TTLs on (say) an SRV record and an A
> record to match the target could be different; so an SRV might be
> satisfied from cache without a corresponding A for the additional.
> 
> Now, suppose a client gets an SRV record with data in the additional
> containing only A records.  Suppose also that the client has only IPv6
> connectivity, so the A records do the client no good.
> 
> My reading is that the client _should_ go and query for the AAAA of
> the target in the SRV record, because there's no data in the
> additional section that will be useful to the client.  If the client
> does this, it should end up with a synthetic AAAA as usual, and
> everything will work.
> 
> The question is whether we know that there are clients that won't just
> query for the AAAA.

If there are such clients they are already broken.  Ignore them.

There is no guarentee about any records in the additional section.
The may not be there for many reasons.  The authoritative server
is returning minimal responses, the records didn't fit due to space
considerations, the authorative server doesn't serve the zone the
referred to names live in, differing TTLs.  All of these are non
DNS64 issues that the SRV client has to deal with. 

If the client can't cope with these adding DNS64 to the list of
things it doesn't cope with is not a issue we need to worry about.

If the client copes with these then it will cope with what DNS64 does.

>  If we do know of such clients, then the approach
> currently in the draft won't work.  In that case, I propose changing
> the draft to require the additional section to be truncated whenever
> it does not contain at least one AAAA record.
> 
> Thoughts?
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From root@core3.amsl.com  Thu Feb 11 04:15:02 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 D82553A729E; Thu, 11 Feb 2010 04:15:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100211121502.D82553A729E@core3.amsl.com>
Date: Thu, 11 Feb 2010 04:15:02 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-09.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: Thu, 11 Feb 2010 12:15:03 -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           : IP/ICMP Translation Algorithm
	Author(s)       : X. Li, et al.
	Filename        : draft-ietf-behave-v6v4-xlate-09.txt
	Pages           : 32
	Date            : 2010-02-11

This document specifies an update to the Stateless IP/ICMP
Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
translates between IPv4 and IPv6 packet headers (including ICMP
headers) for both stateless and stateful modes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-09.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-v6v4-xlate-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xing@cernet.edu.cn  Thu Feb 11 04:36:05 2010
Return-Path: <xing@cernet.edu.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 629E628C158 for <behave@core3.amsl.com>; Thu, 11 Feb 2010 04:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.555
X-Spam-Level: 
X-Spam-Status: No, score=0.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MIME_CHARSET_FARAWAY=2.45]
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 hr325MB32qAI for <behave@core3.amsl.com>; Thu, 11 Feb 2010 04:36:04 -0800 (PST)
Received: from mail1.bur200.uecomm.net.au (mail1.bur200.uecomm.net.au [218.185.0.70]) by core3.amsl.com (Postfix) with ESMTP id 8806628C152 for <behave@ietf.org>; Thu, 11 Feb 2010 04:36:04 -0800 (PST)
Received: from [10.0.0.26] (unknown [218.185.71.66]) by mail1.bur200.uecomm.net.au (Postfix) with ESMTP id 798B5D396 for <behave@ietf.org>; Thu, 11 Feb 2010 23:36:54 +1100 (EST)
Message-ID: <4B73F9E5.9040202@cernet.edu.cn>
Date: Thu, 11 Feb 2010 20:36:53 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: 'Behave WG' <behave@ietf.org>
References: <20100211121502.D82553A729E@core3.amsl.com>
In-Reply-To: <20100211121502.D82553A729E@core3.amsl.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-09.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: Thu, 11 Feb 2010 12:36:05 -0000

Hi, All,

This is the revision for the fragmentation handling according to the
discussions on the mailing-list. The diff is at
http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-v6v4-xlate-09.txt.
Please comment.

Regards,

xing, congxiao


Internet-Drafts@ietf.org дµÀ:
> 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           : IP/ICMP Translation Algorithm
> 	Author(s)       : X. Li, et al.
> 	Filename        : draft-ietf-behave-v6v4-xlate-09.txt
> 	Pages           : 32
> 	Date            : 2010-02-11
>
> This document specifies an update to the Stateless IP/ICMP
> Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
> translates between IPv4 and IPv6 packet headers (including ICMP
> headers) for both stateless and stateful modes.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-09.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.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From ajs@shinkuro.com  Fri Feb 12 10:40:19 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 95CF63A7873 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 10:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.068
X-Spam-Level: 
X-Spam-Status: No, score=-2.068 tagged_above=-999 required=5 tests=[AWL=0.531,  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 ncqwWmYZeA8U for <behave@core3.amsl.com>; Fri, 12 Feb 2010 10:40:18 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id C85C03A7859 for <behave@ietf.org>; Fri, 12 Feb 2010 10:40:18 -0800 (PST)
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 0AA371ECB4E8 for <behave@ietf.org>; Fri, 12 Feb 2010 18:41:36 +0000 (UTC)
Date: Fri, 12 Feb 2010 13:41:35 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100212184135.GM14996@shinkuro.com>
References: <20100210201252.GS5187@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100210201252.GS5187@shinkuro.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] DNS64 and SRV records
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, 12 Feb 2010 18:40:19 -0000

Ok, as a result of feedback here and in the DNSEXT WG, I have
concluded we should still leave the Additional section alone.  Here's
some additional text that I propose to make clearer the reasoning:

           <section title="Handling the additional section" anchor="addl_sec">
             <t>DNS64 synthesis MUST NOT be performed on any records
             in the additional section of synthesized answers.  The
             DNS64 MUST pass the additional section unchanged.</t>

             <t>It may appear that adding synthetic records to the
             additional section is desirable, because clients
             sometimes use the data in the additional section to
             proceed without having to re-query.  There is in general
             no promise, however, that the additional section will
             contain all the relevant records, so any client that
             depends on the additional section being able to satisfy
             its needs (i.e. without additional queries) is
             automatically broken.  An IPv6-only client that needs a
             AAAA record, therefore, will send a query for the
             necessary AAAA record if it is unable to find such a
             record in the additional section of an answer it is
             consuming.</t>

             <t>The alternative, of removing the A records in the
             additional section and replacing them with synthetic AAAA
             records, may cause a host behind a NAT64 to query
             directly a nameserver that is unaware of the NAT64 in
             question.  The result in this case will be resolution
             failure anyway, only later in the resolution operation.</t>

Ok?

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

From dwing@cisco.com  Fri Feb 12 11:15:03 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 8614C3A78D9 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Level: 
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 oyrIgMTEamNX for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:15:02 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id AC7553A7880 for <behave@ietf.org>; Fri, 12 Feb 2010 11:15:01 -0800 (PST)
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: ApIGAEY3dUurRN+J/2dsb2JhbACHTIESkiN0qBCXTYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,462,1262563200"; d="scan'208";a="87557510"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 12 Feb 2010 19:16:21 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1CJGKUB014976; Fri, 12 Feb 2010 19:16:20 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 12 Feb 2010 11:16:20 -0800
Message-ID: <139801caac17$dc143ea0$c4f0200a@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: AcqsF9vTFuvvjIMIQxqHrrSdupzCmQ==
Cc: draft-ietf-behave-address-format@tools.ietf.org
Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-address-format-04
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, 12 Feb 2010 19:15:03 -0000

** We need at least 5 reviewers to tell us this document is ready 
** for submission to IESG.  Please email behave-chairs@tools.ietf.org 
** with a subject line containing the document name, and "ready 
** to submit to IESG" or "not ready to submit to IESG" in the 
** message body.  If not ready to submit, please propose new text.


This email starts the 2nd WGLC for draft-ietf-behave-address-format-04, ending
in one week (Friday, February 19).  For reference, the first WGLC was for
draft-ietf-behave-address-format-03.

Differences between 03 (first WGLC) and 04 (2nd WGLC) are:

http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-address-format-03&url2=dr
aft-ietf-behave-address-format-04.txt

-d


From dwing@cisco.com  Fri Feb 12 11:16:20 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 E0EE53A7880 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.563
X-Spam-Level: 
X-Spam-Status: No, score=-10.563 tagged_above=-999 required=5 tests=[AWL=0.036, 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 7YxbT28ioeKk for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:16:20 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id DDA1D3A6858 for <behave@ietf.org>; Fri, 12 Feb 2010 11:16:19 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIGAL43dUurRN+J/2dsb2JhbACHTIESkiN0qAeXTYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,462,1262563200"; d="scan'208";a="150624411"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 12 Feb 2010 19:17:39 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1CJHdlH016351; Fri, 12 Feb 2010 19:17:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 12 Feb 2010 11:17:39 -0800
Message-ID: <139901caac18$0ae0d5e0$c4f0200a@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: AcqsGAqgGYZNVLWdQ+GwrR5ZfK8Row==
Cc: draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org
Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-stateful-08
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, 12 Feb 2010 19:16:21 -0000

** We need at least 5 reviewers to tell us this document is ready 
** for submission to IESG.  Please email behave-chairs@tools.ietf.org 
** with a subject line containing the document name, and "ready 
** to submit to IESG" or "not ready to submit to IESG" in the 
** message body.  If not ready to submit, please propose new text.


This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-stateful-08,
ending in one week (Friday, February 19).  For reference, the first WGLC was
for draft-ietf-behave-v6v4-xlate-stateful-07.

Differences between 07 (first WGLC) and 08 (2nd WGLC) are:

http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-stateful-07&ur
l2=draft-ietf-behave-v6v4-xlate-stateful-08.txt

-d


From dwing@cisco.com  Fri Feb 12 11:17: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 6718E3A78D9 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.565
X-Spam-Level: 
X-Spam-Status: No, score=-10.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 vK8yGgsMvI3z for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:17:13 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 6B18E3A78E8 for <behave@ietf.org>; Fri, 12 Feb 2010 11:17:13 -0800 (PST)
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: ApIGAL43dUurRN+K/2dsb2JhbACHTIESkiN0qAeXTYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,462,1262563200"; d="scan'208";a="85693631"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by rtp-iport-1.cisco.com with ESMTP; 12 Feb 2010 19:18:32 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1CJIVr9027554; Fri, 12 Feb 2010 19:18:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 12 Feb 2010 11:18:31 -0800
Message-ID: <139a01caac18$2a031c80$c4f0200a@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: AcqsGCm956AMvKnwQVi8+qsuuj5YFQ==
Cc: draft-ietf-behave-v6v4-xlate@tools.ietf.org
Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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, 12 Feb 2010 19:17:14 -0000

** We need at least 5 reviewers to tell us this document is ready 
** for submission to IESG.  Please email behave-chairs@tools.ietf.org 
** with a subject line containing the document name, and "ready 
** to submit to IESG" or "not ready to submit to IESG" in the 
** message body.  If not ready to submit, please propose new text.


This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-09, ending in
one week (Friday, February 19).  For reference, the first WGLC was for
draft-ietf-behave-v6v4-xlate-05.

draft-ietf-behave-v6v4-xlate-09 contains all feedback from the working group
to date, including the feedback based on Ben Stasiewicz's analysis of ICMPv6
behavior on the Internet and the resulting discussion on the mailing list,
which resulted in a new sentence and a new paragraph between -07 and -09.
Differences between 07 and 09 are:

http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-07.txt&url2=dr
aft-ietf-behave-v6v4-xlate-09.txt


Differences between 05 (first WGLC) and 09 (2nd WGLC) are:

http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-05.txt&url2=dr
aft-ietf-behave-v6v4-xlate-09.txt

-d



From dwing@cisco.com  Fri Feb 12 11:18:49 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 BF56328C1E1 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level: 
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 yKwwMU1XrIxA for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:18:48 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 8C86F28C1DE for <behave@ietf.org>; Fri, 12 Feb 2010 11:18:48 -0800 (PST)
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: ApIGAK84dUurRN+J/2dsb2JhbACHTIESkiN0qAaXTYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,462,1262563200"; d="scan'208";a="87560063"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 12 Feb 2010 19:20:08 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1CJK7ce018726; Fri, 12 Feb 2010 19:20:07 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 12 Feb 2010 11:20:07 -0800
Message-ID: <13a401caac18$636b4f10$c4f0200a@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: AcqsGGMyIPFd8i9FQECSH1TLoLq9CA==
Cc: draft-ietf-behave-v6v4-framework@tools.ietf.org
Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-framework-06
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, 12 Feb 2010 19:18:49 -0000

** We need at least 5 reviewers to tell us this document is ready 
** for submission to IESG.  Please email behave-chairs@tools.ietf.org 
** with a subject line containing the document name, and "ready 
** to submit to IESG" or "not ready to submit to IESG" in the 
** message body.  If not ready to submit, please propose new text.


This email starts the 2nd WGLC for draft-ietf-behave-v6v4-framework-06, ending
in one week (Friday, February 19).  For reference, the first WGLC was for
draft-ietf-behave-v6v4-framework-04.  

Differences from -04 (first WGLC) and -06 (2nd WGLC):

http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-framework-04&url2=dr
aft-ietf-behave-v6v4-framework-06

-d


From dwing@cisco.com  Fri Feb 12 11:23:17 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 A16AB3A776A for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:23:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.567
X-Spam-Level: 
X-Spam-Status: No, score=-10.567 tagged_above=-999 required=5 tests=[AWL=0.032, 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 RhM8HSHPeIyw for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:23:16 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id B2EC63A7736 for <behave@ietf.org>; Fri, 12 Feb 2010 11:23:16 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIGACg5dUurRN+K/2dsb2JhbACHTIESkiN0qASXTYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,462,1262563200"; d="scan'208";a="85827760"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by rtp-iport-2.cisco.com with ESMTP; 12 Feb 2010 19:24:35 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1CJOYqK002871 for <behave@ietf.org>; Fri, 12 Feb 2010 19:24:34 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 12 Feb 2010 11:24:34 -0800
Message-ID: <13a701caac19$025e3a10$c4f0200a@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: AcqsGQIgMZ0KBN1JQLaTpL1EvghGQg==
Subject: [BEHAVE] 2nd WGLC status
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, 12 Feb 2010 19:23:17 -0000

As you just saw my 4 posts, we started the 2nd WGLC for 4 (of our 6)
translation documents.  The 2nd WGLC is only a week long.  As stated, we need
5 reviewers to say "looks good" before submitting to IESG.

2nd WGLC finishes Feb-19:
  draft-ietf-behave-v6v4-framework-06      
  draft-ietf-behave-v6v4-xlate-09          
  draft-ietf-behave-v6v4-xlate-stateful-08	
  draft-ietf-behave-address-format-04	

waiting for new versions from authors:
  draft-ietf-behave-dns64-06, awaiting version -06 from authors
  draft-ietf-behave-ftp64-01, awaiting version -01 from author


which is also shown at http://trac.tools.ietf.org/wg/behave/trac/wiki

-d


From ajs@shinkuro.com  Fri Feb 12 11:50:25 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 8CFD73A6858 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.054
X-Spam-Level: 
X-Spam-Status: No, score=-2.054 tagged_above=-999 required=5 tests=[AWL=0.545,  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 L+Nt9CJiKg81 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:50:24 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id C78273A75A5 for <behave@ietf.org>; Fri, 12 Feb 2010 11:50:24 -0800 (PST)
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 66D261ECB4E8 for <behave@ietf.org>; Fri, 12 Feb 2010 19:51:43 +0000 (UTC)
Date: Fri, 12 Feb 2010 14:51:41 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100212195141.GR14996@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [BEHAVE] draft-cao-behave-dsdns64-00
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, 12 Feb 2010 19:50:25 -0000

Dear colleagues,

I just read draft-cao-behave-dsdns64-00.  I confess that I am completely mystified by it.

The central point of the draft appears to be that the DNS64 should
handle A queries normally.

There is no explanation of how that would even possibly work.  The
DNS64 works by synthesizing AAAA out of A records.  It _can't_ return
an A record because it will return the AAAA first.

If that assumption is violated, actually, the entire DNS64 project is
doomed as near as I can tell.

Have I missed something?

Best regards,

A

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

From dwing@cisco.com  Fri Feb 12 11:59:20 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 C50B228C1EF for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level: 
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 1H4Iry4hsTbd for <behave@core3.amsl.com>; Fri, 12 Feb 2010 11:59:20 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 0DD1028C1ED for <behave@ietf.org>; Fri, 12 Feb 2010 11:59:20 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIGAKJBdUurRN+J/2dsb2JhbACHTIESkiN0p3OXS4RYBIMT
X-IronPort-AV: E=Sophos;i="4.49,463,1262563200"; d="scan'208";a="298797581"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-1.cisco.com with ESMTP; 12 Feb 2010 20:00:39 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1CK0dGU026569 for <behave@ietf.org>; Fri, 12 Feb 2010 20:00:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 12 Feb 2010 12:00:39 -0800
Message-ID: <13cd01caac1e$0cd62e80$c4f0200a@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: AcqsFrQAWo81hYVBRbKSjMqPHFKU+w==
Subject: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers for dual-stack/IPv6-only hosts
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, 12 Feb 2010 19:59:20 -0000

A few weeks ago there was an active thread on BEHAVE and 3Gv6@ietf.org,
worrying about how a network containing a mix of dual-stack hosts and
IPv6-only hosts would work.  Ideally, to prevent unnecessary address family
translation, the dual-stack hosts should use a 'normal' DNS resolver and the
IPv6-only hosts should use a DNS64 resolver.  However, it is difficult to
detect if a host is dual-stack or is IPv6-only.

So, I wrote an Internet Draft describing details of several approaches that
had been discussed on the mailing list, and attempted to provide a list of
advantages/disadvantages to each.


While writing them down, I came up with another approach which uses an
IPv4-mapped address in the list of IPv6 DNS servers.  An IPv6-only host cannot
use that address, so it would use the next DNS server on the list; a
dual-stack host can use such a DNS server.  Details are in:

http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.1

Please comment on this approach.  For whatever it's worth, the idea seems to
work.

-d


From dwing@cisco.com  Fri Feb 12 12:26:31 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 ADDB23A7905 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 12:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.57
X-Spam-Level: 
X-Spam-Status: No, score=-10.57 tagged_above=-999 required=5 tests=[AWL=0.029,  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 9YtCxwAER9TV for <behave@core3.amsl.com>; Fri, 12 Feb 2010 12:26:30 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id C87C73A7904 for <behave@ietf.org>; Fri, 12 Feb 2010 12:26:30 -0800 (PST)
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: ApIGABZJdUurRN+K/2dsb2JhbACHTIESkiN0qAKXSYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,463,1262563200"; d="scan'208";a="87597236"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 12 Feb 2010 20:27:50 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1CKRoHa000390; Fri, 12 Feb 2010 20:27:50 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Andrew Sullivan'" <ajs@shinkuro.com>, <behave@ietf.org>
References: <20100212195141.GR14996@shinkuro.com>
Date: Fri, 12 Feb 2010 12:27:50 -0800
Message-ID: <13e001caac21$d8b577b0$c4f0200a@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
In-Reply-To: <20100212195141.GR14996@shinkuro.com>
Thread-Index: AcqsHM/elnoraenjRVa5O8yS6bRBxwAA4+Sw
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 12 Feb 2010 20:26:31 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
> Sent: Friday, February 12, 2010 11:52 AM
> To: behave@ietf.org
> Subject: [BEHAVE] draft-cao-behave-dsdns64-00
> 
> Dear colleagues,
> 
> I just read draft-cao-behave-dsdns64-00.  I confess that I am 
> completely mystified by it.
> 
> The central point of the draft appears to be that the DNS64 should
> handle A queries normally.
> 
> There is no explanation of how that would even possibly work.  The
> DNS64 works by synthesizing AAAA out of A records.  It _can't_ return
> an A record because it will return the AAAA first.
> 
> If that assumption is violated, actually, the entire DNS64 project is
> doomed as near as I can tell.
> 
> Have I missed something?

It should work if the policy table IPv6/IPv4 preference is inverted
from the default.  That is, the host's RFC3484 policy table could be
changed to prefer IPv4.  

That would have significant implications, though:  if a server
is dual-stacked, the dual-stack client will always use IPv4.  That
IPv4 traffic is likely to be NATted (due to impending IPv4 
exhaustion and the need for the ISP to conserve IPv4 addresses),
which will harm the user's experience if they need more TCP
ports than available on the NAT.  Some applications need a lot
of TCP ports, as we know -- the canonical example is Google Maps
but there are other applications that also use a lot of TCP
ports.  To avoid the poor user experience of running out of 
TCP ports on the NAT, the content provider has an incentive to
enable IPv6.  However, if the dual-stack client continues to
prefer IPv4, the IPv6 path isn't used, and the user experience
continues to be poor.  With such an address preference, the 
user experience only improves when the A record is no longer
in the DNS.  That also means thousands, or millions, of 
clients would suddenly switch from using IPv4 to using IPv6
which would be a difficult adjustment for the content provider.

-d


> Best regards,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From simon.perreault@viagenie.ca  Fri Feb 12 12:30:00 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 E10F228C1C8 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 12:30:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 DbHG+ykGfc84 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 12:29:59 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id 2F8703A7087 for <behave@ietf.org>; Fri, 12 Feb 2010 12:29:59 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C5B1C21CC0 for <behave@ietf.org>; Fri, 12 Feb 2010 15:31:15 -0500 (EST)
Message-ID: <4B75BA93.7080204@viagenie.ca>
Date: Fri, 12 Feb 2010 15:31:15 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com>
In-Reply-To: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers for	dual-stack/IPv6-only hosts
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, 12 Feb 2010 20:30:01 -0000

On 2010-02-12 15:00, Dan Wing wrote:
> While writing them down, I came up with another approach which uses an
> IPv4-mapped address in the list of IPv6 DNS servers.  An IPv6-only host cannot
> use that address, so it would use the next DNS server on the list; a
> dual-stack host can use such a DNS server.  Details are in:
>
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.1

I'm slow... What's the advantage of this over using a plain IPv4 address?

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

From cb.list6@gmail.com  Fri Feb 12 13:06:41 2010
Return-Path: <cb.list6@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 8ABF228C202 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 13:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 CWcW78SV+Uj7 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 13:06:39 -0800 (PST)
Received: from mail-gx0-f228.google.com (mail-gx0-f228.google.com [209.85.217.228]) by core3.amsl.com (Postfix) with ESMTP id AB03928C22A for <behave@ietf.org>; Fri, 12 Feb 2010 13:06:39 -0800 (PST)
Received: by gxk28 with SMTP id 28so2344646gxk.9 for <behave@ietf.org>; Fri, 12 Feb 2010 13:07:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=l9zPDzz3osI82WuKMuSQjM4ByzRtR9Nl0Bs1Emf3WH8=; b=hyhG0vx3BIWy2tzOkVKtIKnCcFFgh75HcYoVNQgy4iX03RHJT0eIuMDoRJQqDohNbJ 5654brCzwB4CxU6PTZF80YTiGwjF+SnhPp3gk+Et3ay+oLGRCPzC1RgGpCU4H5ldjhpy SjrVmTGigbC3DV7ccRxWNDjCS5gH738pCbXDU=
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 :cc:content-type:content-transfer-encoding; b=afOSDxc2Jq++YKsTuquQthrBUzBdQpFN7tKsaxjCFZvJ7zC6GFPfJMAo5wkjAe+lur UyB5ematKzHmQHmWXfEXCs+0SX6BjZB3NRZ/hc2S63JOt3rhx4XRnGbrcMr3XarUen2o Oap5Kw1OinWyCOzxaw3lNQoR+YVJnr8GyPJPQ=
MIME-Version: 1.0
Received: by 10.150.119.42 with SMTP id r42mr871244ybc.325.1266008876186; Fri,  12 Feb 2010 13:07:56 -0800 (PST)
In-Reply-To: <13e001caac21$d8b577b0$c4f0200a@cisco.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com>
Date: Fri, 12 Feb 2010 13:07:56 -0800
Message-ID: <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 12 Feb 2010 21:06:41 -0000

On Fri, Feb 12, 2010 at 12:27 PM, Dan Wing <dwing@cisco.com> wrote:
>
>
>> -----Original Message-----
>> From: behave-bounces@ietf.org
>> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
>> Sent: Friday, February 12, 2010 11:52 AM
>> To: behave@ietf.org
>> Subject: [BEHAVE] draft-cao-behave-dsdns64-00
>>
>> Dear colleagues,
>>
>> I just read draft-cao-behave-dsdns64-00. =A0I confess that I am
>> completely mystified by it.

I don't agree with the premise of the draft -- that traffic going via
a NAT64 is entirely bad.  In some environments maybe it is bad, but in
my environment 99% of the mobile phone / device traffic goes via NAT44
today.  NAT64 and NAT44 are very similar in function and cost to the
service provider.  If the flow goes via NAT44 or NAT64 it does not
matter to me, either way the user can access the content they want and
the service provider has to support / scale  "state" in the network
for that session(s).  If the user receives a natural AAAA record, i
have less NAT state since a natural (non-DNS64 synthesized) record
will bypass the NAT64 completely, thus saving me money since i don't
have to grow the NAT capacity for any native IPv6 content (keep in
mind Google and Youtube are the largest content sources in the USA ..
and they service native IPv6)

So, using today's model, if all my users were IPv6-only with NAT64
instead of IPv4 with NAT44, i would have much less cost in the network
since native AAAA flows would not go via the NAT.


>>
>> The central point of the draft appears to be that the DNS64 should
>> handle A queries normally.
>>
>> There is no explanation of how that would even possibly work. =A0The
>> DNS64 works by synthesizing AAAA out of A records. =A0It _can't_ return
>> an A record because it will return the AAAA first.
>>
>> If that assumption is violated, actually, the entire DNS64 project is
>> doomed as near as I can tell.
>>
>> Have I missed something?
>
> It should work if the policy table IPv6/IPv4 preference is inverted
> from the default. =A0That is, the host's RFC3484 policy table could be
> changed to prefer IPv4.
>

And this is exactly what we DO NOT want to happen.  Since it means
that only IPv6-only systems will go to IPv6 content, thus perpetuating
the "chicken and egg" problem to new unforeseen levels of stale-mate.

> That would have significant implications, though: =A0if a server
> is dual-stacked, the dual-stack client will always use IPv4. =A0That
> IPv4 traffic is likely to be NATted (due to impending IPv4
> exhaustion and the need for the ISP to conserve IPv4 addresses),
> which will harm the user's experience if they need more TCP
> ports than available on the NAT. =A0Some applications need a lot
> of TCP ports, as we know -- the canonical example is Google Maps
> but there are other applications that also use a lot of TCP

This is a very important point and a powerful trend with AJAX
webpages, here is the citation for NTT's work on this topic of MANY
MANY session consuming a great deal of NAT resources.

http://www.nttv6.jp/~miyakawa/IETF72/IETF-IAB-TECH-PLENARY-NTT-miyakawa.pdf

> ports. =A0To avoid the poor user experience of running out of
> TCP ports on the NAT, the content provider has an incentive to
> enable IPv6. =A0However, if the dual-stack client continues to
> prefer IPv4, the IPv6 path isn't used, and the user experience
> continues to be poor. =A0With such an address preference, the
> user experience only improves when the A record is no longer
> in the DNS. =A0That also means thousands, or millions, of

Right, this leads to the proverbial flag-day that the IETF said would
never exists, because it will also invariably partition portions of
the Internet on the flag day

> clients would suddenly switch from using IPv4 to using IPv6
> which would be a difficult adjustment for the content provider.
>
> -d
>
>
>> Best regards,
>>
>> A
>>
>> --
>> Andrew Sullivan
>> ajs@shinkuro.com
>> Shinkuro, Inc.
>> _______________________________________________
>> 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 dwing@cisco.com  Fri Feb 12 13:09:19 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 9AB6B28C26A for <behave@core3.amsl.com>; Fri, 12 Feb 2010 13:09:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.571
X-Spam-Level: 
X-Spam-Status: No, score=-10.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 hfpUEcYsvOn0 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 13:09:18 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id E6D8028C267 for <behave@ietf.org>; Fri, 12 Feb 2010 13:09:18 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwHAP9RdUurRN+J/2dsb2JhbACHTIESkiN0p22XSIRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,463,1262563200"; d="scan'208";a="298815802"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-1.cisco.com with ESMTP; 12 Feb 2010 21:10:38 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1CLAchX019119; Fri, 12 Feb 2010 21:10:38 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Simon Perreault'" <simon.perreault@viagenie.ca>, <behave@ietf.org>
References: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com> <4B75BA93.7080204@viagenie.ca>
Date: Fri, 12 Feb 2010 13:10:38 -0800
Message-ID: <13f901caac27$d3a776f0$c4f0200a@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
In-Reply-To: <4B75BA93.7080204@viagenie.ca>
Thread-Index: AcqsIlncJwTIOvkFRDKYLUfagaB2fAABUngw
Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers for	dual-stack/IPv6-only hosts
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, 12 Feb 2010 21:09:19 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Simon Perreault
> Sent: Friday, February 12, 2010 12:31 PM
> To: behave@ietf.org
> Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers 
> for dual-stack/IPv6-only hosts
> 
> On 2010-02-12 15:00, Dan Wing wrote:
> > While writing them down, I came up with another approach 
> which uses an
> > IPv4-mapped address in the list of IPv6 DNS servers.  An 
> IPv6-only host cannot
> > use that address, so it would use the next DNS server on the list; a
> > dual-stack host can use such a DNS server.  Details are in:
> >
> > 
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#s
> ection-3.1
> 
> I'm slow... What's the advantage of this over using a plain 
> IPv4 address?

DHCPv6 only allows IPv6 addresses, 
http://tools.ietf.org/html/rfc3646#section-3

-d


From dwing@cisco.com  Fri Feb 12 13:22:58 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 7402128C227 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 13:22:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.572
X-Spam-Level: 
X-Spam-Status: No, score=-10.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 hSRN8+Z2Hwb6 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 13:22:57 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id EB64C28C204 for <behave@ietf.org>; Fri, 12 Feb 2010 13:22:56 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwHAPpVdUurRN+K/2dsb2JhbACHTIESkiN0p1uXRYRYBIMT
X-IronPort-AV: E=Sophos;i="4.49,463,1262563200"; d="scan'208";a="239786466"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-2.cisco.com with ESMTP; 12 Feb 2010 21:24:16 +0000
Received: from dwingwxp01 ([10.32.240.196]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1CLOGvD011929; Fri, 12 Feb 2010 21:24:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
References: <4AFCBC87.20009@gmail.com><C1463B96FBAB4A59B7B279C43BDCE778@china.huawei.com><4AFCDCBD.8090403@gmail.com> <E4561B14EE2A3E4E9D478EBFB5416E1B29B54AC5@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Fri, 12 Feb 2010 13:24:16 -0800
Message-ID: <140701caac29$bb3d16e0$c4f0200a@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
In-Reply-To: 
Thread-Index: AcpkBJjRNZadzFp3+k2ifBL2nWT5oAAAwHhQABTAK4ACcuQLcAAFZ1lQD3tvOjA=
Cc: 'Dean Cheng' <Chengd@huawei.com>, 'Dave Thaler' <dthaler@microsoft.com>
Subject: Re: [BEHAVE] draft-xu-behave-nat-state-sync-00
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, 12 Feb 2010 21:22:58 -0000

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Wednesday, November 25, 2009 5:58 PM
> To: 'Dave Thaler'; 'Brian E Carpenter'; 'Dean Cheng'
> Cc: 'behave@ietf.org'
> Subject: RE: [BEHAVE] draft-xu-behave-nat-state-sync-00
> 
>  
> 
> > -----Original Message-----
> > From: behave-bounces@ietf.org 
> > [mailto:behave-bounces@ietf.org] On Behalf Of Dave Thaler
> > Sent: Wednesday, November 25, 2009 3:32 PM
> > To: Brian E Carpenter; Dean Cheng
> > Cc: behave@ietf.org
> > Subject: Re: [BEHAVE] draft-xu-behave-nat-state-sync-00
> > 
> > Some other references:
> > http://genie.iitd.ernet.in/wipo/report/node28.html seems to use
> > it for mailbox sync in another thesis (with WinCE & Linux) in 2004.
> > 
> > http://www.netlab.tkk.fi/tutkimus/ipana/paperit/spiejose2.ppt
> > discusses an implementation in 1999.
> > 
> > It also looks like Nortel might have IPR in this area:
> > http://www.google.com/patents/about?id=YKYIAAAAEBAJ
> > although I don't see anything in the IETF IPR database.
> 
> Cisco apparently, too.  I just asked the inventors to work 
> with Cisco legal to get an IPR declaration issued if one is necessary.

Cisco's IPR declaration on draft-xu-behave-nat-state-sync-00.txt:

https://datatracker.ietf.org/ipr/search/?option=document_search&document_searc
h=draft-xu-behave-nat-state-sync-00.txt
https://datatracker.ietf.org/ipr/1261/

-d


> -d
> 
> 
> > -Dave
> > 
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> > > Behalf Of Brian E Carpenter
> > > Sent: Thursday, November 12, 2009 8:13 PM
> > > To: Dean Cheng
> > > Cc: behave@ietf.org
> > > Subject: Re: [BEHAVE] draft-xu-behave-nat-state-sync-00
> > > 
> > > It seems there was SCSP code in BSD some years ago, as part of the
> > > ATM support:
> > > 
> > > http://www.freebsd.org/releases/3.0R/notes.html
> > > 
> > > Also for Linux, it seems to be tied to ATM:
> > > 
> > > http://www.digipedia.pl/man/doc/view/scspd.8.html
> > > 
> > > I also found an MSc thesis discussing SCSP in SunOS 5.6.
> > > 
> > > Regards
> > >    Brian
> > > 
> > > On 2009-11-13 15:25, Dean Cheng wrote:
> > > > Brian,
> > > >
> > > >> -----Original Message-----
> > > >> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On
> > > Behalf
> > > > Of
> > > >> Brian E Carpenter
> > > >> Sent: Thursday, November 12, 2009 5:55 PM
> > > >> To: behave@ietf.org
> > > >> Subject: [BEHAVE] draft-xu-behave-nat-state-sync-00
> > > >>
> > > >> My question about this draft is whether there is available code
> > > >> and implementation experience with SCSP, which was 
> > defined in 1998.
> > > >
> > > > I don't know personally whether there is any available code, but
> > > > RFC2335 and RFC2443 documented two separate applications 
> > using SCSP,
> > > > although also about 10 years ago.
> > > >
> > > > However, SCSP (as mentioned in my presentation) itself heavily
> > > > "borrowed" link-state based algorithm and mechanisms from 
> > OSPF/ISIS
> > > > (also defined in 90's or earlier) that have been widely deployed
> > > since.
> > > >
> > > >> If there isn't code and experience, since it is a quite complex
> > > >> design, I would be a bit worried.
> > > >>
> > > >> On the other hand, I believe that something of the complexity
> > > >> of SCSP is absolutely required to provide reliable 
> > synchronisation.
> > > >> There is no simple, lightweight way to do this reliably.
> > > >
> > > > Totally agreed.
> > > >
> > > > Dean
> > > >
> > > >>     Brian
> > > >>
> > > >> _______________________________________________
> > > >> 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
> > 
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> 


From ajs@shinkuro.com  Fri Feb 12 14:38:30 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 CFF8728C169 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 14:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.07
X-Spam-Level: 
X-Spam-Status: No, score=-2.07 tagged_above=-999 required=5 tests=[AWL=0.529,  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 cTRzhYN0ygv0 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 14:38:30 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 1797728C147 for <behave@ietf.org>; Fri, 12 Feb 2010 14:38:30 -0800 (PST)
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 24E4A1ECB4E8 for <behave@ietf.org>; Fri, 12 Feb 2010 22:39:49 +0000 (UTC)
Date: Fri, 12 Feb 2010 17:39:47 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100212223947.GY14996@shinkuro.com>
References: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolvers for	dual-stack/IPv6-only hosts
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, 12 Feb 2010 22:38:30 -0000

On Fri, Feb 12, 2010 at 12:00:39PM -0800, Dan Wing wrote:
> While writing them down, I came up with another approach which uses an
> IPv4-mapped address in the list of IPv6 DNS servers.  An IPv6-only host cannot
> use that address, so it would use the next DNS server on the list; a
> dual-stack host can use such a DNS server.  Details are in:
> 
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.1
> 
> Please comment on this approach.  For whatever it's worth, the idea seems to
> work.

This is _before_ any DNS64 is happening, right?  That is, it's a way
to convince the dual-homed host to use the "plain" DNS for v4 queries
and the DNS64 for v6 queries, without a lot of complicated
co-ordination?  If I've read it right, it seems like a good idea to
me.

A

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

From marka@isc.org  Fri Feb 12 15:47:35 2010
Return-Path: <marka@isc.org>
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 1E79B28C1C2 for <behave@core3.amsl.com>; Fri, 12 Feb 2010 15:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 jg0-bDhkq0qx for <behave@core3.amsl.com>; Fri, 12 Feb 2010 15:47:34 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 17B5728C126 for <behave@ietf.org>; Fri, 12 Feb 2010 15:47:34 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 5905EE60AA; Fri, 12 Feb 2010 23:48:52 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1CNmmq0046543; Sat, 13 Feb 2010 10:48:48 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002122348.o1CNmmq0046543@drugs.dv.isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
From: Mark Andrews <marka@isc.org>
References: <20100210201252.GS5187@shinkuro.com> <20100212184135.GM14996@shinkuro.com> 
In-reply-to: Your message of "Fri, 12 Feb 2010 13:41:35 CDT." <20100212184135.GM14996@shinkuro.com> 
Date: Sat, 13 Feb 2010 10:48:48 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] DNS64 and SRV records
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, 12 Feb 2010 23:47:35 -0000

In message <20100212184135.GM14996@shinkuro.com>, Andrew Sullivan writes:
> Ok, as a result of feedback here and in the DNSEXT WG, I have
> concluded we should still leave the Additional section alone.  Here's
> some additional text that I propose to make clearer the reasoning:
> 
>            <section title="Handling the additional section" anchor="addl_sec"
> >
>              <t>DNS64 synthesis MUST NOT be performed on any records
>              in the additional section of synthesized answers.  The
>              DNS64 MUST pass the additional section unchanged.</t>
> 
>              <t>It may appear that adding synthetic records to the
>              additional section is desirable, because clients
>              sometimes use the data in the additional section to
>              proceed without having to re-query.  There is in general
>              no promise, however, that the additional section will
>              contain all the relevant records, so any client that
>              depends on the additional section being able to satisfy
>              its needs (i.e. without additional queries) is
>              automatically broken.  An IPv6-only client that needs a
>              AAAA record, therefore, will send a query for the
>              necessary AAAA record if it is unable to find such a
>              record in the additional section of an answer it is
>              consuming.</t>
> 
>              <t>The alternative, of removing the A records in the
>              additional section and replacing them with synthetic AAAA
>              records, may cause a host behind a NAT64 to query
>              directly a nameserver that is unaware of the NAT64 in
>              question.  The result in this case will be resolution
>              failure anyway, only later in the resolution operation.</t>

I would just drop the last paragraph.
 
> Ok?
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Fri Feb 12 16:12:01 2010
Return-Path: <marka@isc.org>
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 CE93A3A791E for <behave@core3.amsl.com>; Fri, 12 Feb 2010 16:12:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 h-G0MhcFSgVn for <behave@core3.amsl.com>; Fri, 12 Feb 2010 16:12:00 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 7F8223A682A for <behave@ietf.org>; Fri, 12 Feb 2010 16:12:00 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 57E60E60A9; Sat, 13 Feb 2010 00:13:19 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1D0DGEN046772; Sat, 13 Feb 2010 11:13:16 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002130013.o1D0DGEN046772@drugs.dv.isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
From: Mark Andrews <marka@isc.org>
References: <20100212195141.GR14996@shinkuro.com> 
In-reply-to: Your message of "Fri, 12 Feb 2010 14:51:41 CDT." <20100212195141.GR14996@shinkuro.com> 
Date: Sat, 13 Feb 2010 11:13:16 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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: Sat, 13 Feb 2010 00:12:02 -0000

In message <20100212195141.GR14996@shinkuro.com>, Andrew Sullivan writes:
> Dear colleagues,
> 
> I just read draft-cao-behave-dsdns64-00.  I confess that I am completely myst
> ified by it.
> 
> The central point of the draft appears to be that the DNS64 should
> handle A queries normally.
> 
> There is no explanation of how that would even possibly work.  The
> DNS64 works by synthesizing AAAA out of A records.  It _can't_ return
> an A record because it will return the AAAA first.
> 
> If that assumption is violated, actually, the entire DNS64 project is
> doomed as near as I can tell.
> 
> Have I missed something?

DNS64 synthesizes AAAA from A when there is no natural AAAA.

DNS64 does NOT affect A queries.  This is covered in "5.3.3. Other records"

	"All other RRs MUST be returned unchanged."

I see no wording equivalent to "Block A queries" in DNS64.

A IPv6 only host / application will only make AAAA queries as part
of normal host resolution.  Note a IPv4 client can ask for AAAA
queries and a IPv6 client can ask for A queries that are unrelated
to making network connection attempts from the client.

A dual stack host / applicaion will make both AAAA and A queries
and provided it has been taught about the DNS64 prefix will
de-preference any synthesized addresses.  Even if it hasn't been
taught the worst that will happen is that the traffic takes a
non-optimal path through the NAT64.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ajs@shinkuro.com  Mon Feb 15 07:04: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 412213A7038 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 07:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.058
X-Spam-Level: 
X-Spam-Status: No, score=-2.058 tagged_above=-999 required=5 tests=[AWL=0.541,  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 zSRB0LLBDsl8 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 07:04:16 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 793643A6A6B for <behave@ietf.org>; Mon, 15 Feb 2010 07:04:16 -0800 (PST)
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 88CAD1ECB402 for <behave@ietf.org>; Mon, 15 Feb 2010 15:05:46 +0000 (UTC)
Date: Mon, 15 Feb 2010 10:05:44 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100215150544.GG25973@shinkuro.com>
References: <20100212195141.GR14996@shinkuro.com> <201002130013.o1D0DGEN046772@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201002130013.o1D0DGEN046772@drugs.dv.isc.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 15 Feb 2010 15:04:17 -0000

On Sat, Feb 13, 2010 at 11:13:16AM +1100, Mark Andrews wrote:
> 
> DNS64 does NOT affect A queries.  This is covered in "5.3.3. Other records"

Right.

> 	"All other RRs MUST be returned unchanged."
> 
> I see no wording equivalent to "Block A queries" in DNS64.

Exactly.  But DNS64 relies implicitly on the premise that clients will
ask for AAAA first.  If they don't, then the end host gets an A record
and it never uses the NAT64.  See others' remarks on why that's a bad
idea in a dual-stack environment.

> A dual stack host / applicaion will make both AAAA and A queries
> and provided it has been taught about the DNS64 prefix will

The "provided it has been taught" condition is unreasonable.  We're
trying to arrange things so that clients don't need to be taught about
all this, because from the POV of deploying having to upgrade every
client is a non-starter.

> taught the worst that will happen is that the traffic takes a
> non-optimal path through the NAT64.

That's exactly my point, too.

A

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

From root@core3.amsl.com  Mon Feb 15 08:45:02 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 935AB28C10C; Mon, 15 Feb 2010 08:45:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100215164502.935AB28C10C@core3.amsl.com>
Date: Mon, 15 Feb 2010 08:45:02 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Mon, 15 Feb 2010 16:45:02 -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           : DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
	Author(s)       : M. Bagnulo, et al.
	Filename        : draft-ietf-behave-dns64-06.txt
	Pages           : 30
	Date            : 2010-02-15

DNS64 is a mechanism for synthesizing AAAA records from A records.
DNS64 is used with an IPv6/IPv4 translator to enable client-server
communication between an IPv6-only client and an IPv4-only server,
without requiring any changes to either the IPv6 or the IPv4 node,
for the class of applications that work through NATs.  This document
specifies DNS64, and provides suggestions on how it should be
deployed in conjunction with IPv6/IPv4 translators.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-dns64-06.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-dns64-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From ajs@shinkuro.com  Mon Feb 15 08:47:10 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 1B96E28C1E1 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 08:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level: 
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.526,  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 iaXwv2QEYMGA for <behave@core3.amsl.com>; Mon, 15 Feb 2010 08:47:09 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 48E7D28C1C6 for <behave@ietf.org>; Mon, 15 Feb 2010 08:47:09 -0800 (PST)
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 620C21ECB402 for <behave@ietf.org>; Mon, 15 Feb 2010 16:48:39 +0000 (UTC)
Date: Mon, 15 Feb 2010 11:48:37 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100215164837.GQ25973@shinkuro.com>
References: <20100215164502.935AB28C10C@core3.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100215164502.935AB28C10C@core3.amsl.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Mon, 15 Feb 2010 16:47:10 -0000

Dear colleagues,

On Mon, Feb 15, 2010 at 08:45:02AM -0800, Internet-Drafts@ietf.org wrote:
> 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           : DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
> 	Author(s)       : M. Bagnulo, et al.
> 	Filename        : draft-ietf-behave-dns64-06.txt
> 	Pages           : 30
> 	Date            : 2010-02-15

This version of the draft includes our responses to the comments
received during and since the previous WGLC.  Follow-up comments are
appreciated.

Best regards,

Andrew

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

From dthaler@microsoft.com  Mon Feb 15 12:05:51 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 EBC073A7BD1 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 12:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.533
X-Spam-Level: 
X-Spam-Status: No, score=-110.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, 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 LX3Qi8OcXPP9 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 12:05:51 -0800 (PST)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 076703A7372 for <behave@ietf.org>; Mon, 15 Feb 2010 12:05:50 -0800 (PST)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 15 Feb 2010 12:08:18 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 15 Feb 2010 12:07:21 -0800
Received: from TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.173]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 15 Feb 2010 12:07:22 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: "draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org" <draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org>
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-stateful-08
Thread-Index: AcqsGAqgGYZNVLWdQ+GwrR5ZfK8RowCXcBhQ
Date: Mon, 15 Feb 2010 20:07:19 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF650CE3B7AC@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
References: <139901caac18$0ae0d5e0$c4f0200a@cisco.com>
In-Reply-To: <139901caac18$0ae0d5e0$c4f0200a@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 WG <behave@ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-stateful-08
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, 15 Feb 2010 20:05:52 -0000

Just some editorial nits...

Section 1.2.1:
> Using DNS64, an IPv6 client obtains an IPv6 address that embeds the

Since stateful NAT64 has no hard dependency on DNS64, suggest:

> Using a mechanism such as DNS64, an IPv6 client obtains an IPv6 address t=
hat embeds the
        ^^^^^^^^^^^^^^^^^^^

Point being that if some other mechanism is used rather than DNS,
NAT64 will still work.  The last paragraph of Section 1.2.2 is
good, which already makes this point.

Section 1.2.2:
> uses the Well-Know Prefix 64:FF9B::/96 defined
                ^^^^
> local name server uses the Well-Know prefix 64:FF9B::/96 to create
                                  ^^^^

s/Know/Known/

Section 1.2.3:
> packets are not specific to the NAT64 and therefore is not described
                                                      ^^
s/is/are/

Section 2:
> pair.  Used to translate the addresses and ports/Query Identifiers

s/Query/ICMP/

Section 3:
> implementations are free use different data structures but they MUST

s/free use/free to use/

Section 3.5.1:
> The NAT64 sets (or resets) the timer in the Session Table Entry to =20
> maximum session lifetime. =20
 ^

Insert "the"

Section 3.5.1.1:
> (this behavior is =20
> recommended in REQ 3-a of [RFC4787])

s/this/This/
Add period before ")"

Section 3.5.2.1:
> and forwards packet in both directions for a short period of time

s/packet/packets/

Section 5.1:
> Any protocols that protect IP header information is essentially

Either s/protocols/protocol/
Or s/is/are/

Section 5.2:
> targeting the internal network.  To avoid these type of abuse, some =20
> NAT64 MAY keep track the sequence number of TCP packets in order to

Replace "these type" with either "this type" or "these types".
s/some NAT64/a NAT64/
Replace "keep track" with either "track" or "keep track of"

-Dave

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dan Wing
> Sent: Friday, February 12, 2010 11:18 AM
> To: behave@ietf.org
> Cc: draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org
> Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-stateful-08
>=20
> ** We need at least 5 reviewers to tell us this document is ready
> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
> ** with a subject line containing the document name, and "ready
> ** to submit to IESG" or "not ready to submit to IESG" in the
> ** message body.  If not ready to submit, please propose new text.
>=20
>=20
> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-
> stateful-08,
> ending in one week (Friday, February 19).  For reference, the first
> WGLC was
> for draft-ietf-behave-v6v4-xlate-stateful-07.
>=20
> Differences between 07 (first WGLC) and 08 (2nd WGLC) are:
>=20
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-behave-v6v4-xlate-
> stateful-07&ur
> l2=3Ddraft-ietf-behave-v6v4-xlate-stateful-08.txt
>=20
> -d
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From dthaler@microsoft.com  Mon Feb 15 12:42:52 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 C5D7428C1E2 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 12:42:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.541
X-Spam-Level: 
X-Spam-Status: No, score=-110.541 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, 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 XduvuxWBLcji for <behave@core3.amsl.com>; Mon, 15 Feb 2010 12:42:52 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id C4C7828C1B4 for <behave@ietf.org>; Mon, 15 Feb 2010 12:42:50 -0800 (PST)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 15 Feb 2010 12:41:49 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 15 Feb 2010 12:40:16 -0800
Received: from TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.173]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Mon, 15 Feb 2010 12:40:14 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: "draft-ietf-behave-v6v4-framework@tools.ietf.org" <draft-ietf-behave-v6v4-framework@tools.ietf.org>
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-framework-06
Thread-Index: AcqsGGMyIPFd8i9FQECSH1TLoLq9CACY8RJA
Date: Mon, 15 Feb 2010 20:40:13 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF650CE3B8BE@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
References: <13a401caac18$636b4f10$c4f0200a@cisco.com>
In-Reply-To: <13a401caac18$636b4f10$c4f0200a@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] 2nd WGLC, draft-ietf-behave-v6v4-framework-06
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, 15 Feb 2010 20:42:52 -0000

Just some editorial nits...

Section 1.2:
> IPv4-only:  An IPv4-only implementation, in this context, comprises =20
>    an IPv4-enabled end system stack, applications directly or =20
>    indirectly using that IPv6 stack, plus routing in the network.  It
                           ^^^^
s/IPv6/IPv4/

Section 1.3:
> greatly magnified.  The objective of the translators is to aviod, as

s/aviod/avoid/

Section 2.1:

> Both sateless [I-D.ietf-behave-v6v4-xlate] and stateful

s/sateless/stateless/

Section 3.2.2:

> from the IPv6 side itdoesn't support IPv4-initiation, and does not
                      ^^^^^^
Insert space

-Dave


> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dan Wing
> Sent: Friday, February 12, 2010 11:20 AM
> To: behave@ietf.org
> Cc: draft-ietf-behave-v6v4-framework@tools.ietf.org
> Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-framework-06
>=20
> ** We need at least 5 reviewers to tell us this document is ready
> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
> ** with a subject line containing the document name, and "ready
> ** to submit to IESG" or "not ready to submit to IESG" in the
> ** message body.  If not ready to submit, please propose new text.
>=20
>=20
> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-framework-06,
> ending
> in one week (Friday, February 19).  For reference, the first WGLC was
> for
> draft-ietf-behave-v6v4-framework-04.
>=20
> Differences from -04 (first WGLC) and -06 (2nd WGLC):
>=20
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-behave-v6v4-framework-
> 04&url2=3Ddr
> aft-ietf-behave-v6v4-framework-06
>=20
> -d
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From marka@isc.org  Mon Feb 15 14:41:25 2010
Return-Path: <marka@isc.org>
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 3B48E3A7BD8 for <behave@core3.amsl.com>; Mon, 15 Feb 2010 14:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  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 5yRChRJNw2xw for <behave@core3.amsl.com>; Mon, 15 Feb 2010 14:41:24 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 43A353A7BE0 for <behave@ietf.org>; Mon, 15 Feb 2010 14:41:24 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 4A3B8E606C; Mon, 15 Feb 2010 22:42:54 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1FMgZnl097630; Tue, 16 Feb 2010 09:42:35 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002152242.o1FMgZnl097630@drugs.dv.isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
From: Mark Andrews <marka@isc.org>
References: <20100212195141.GR14996@shinkuro.com> <201002130013.o1D0DGEN046772@drugs.dv.isc.org> <20100215150544.GG25973@shinkuro.com> 
In-reply-to: Your message of "Mon, 15 Feb 2010 10:05:44 CDT." <20100215150544.GG25973@shinkuro.com> 
Date: Tue, 16 Feb 2010 09:42:35 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 15 Feb 2010 22:41:25 -0000

In message <20100215150544.GG25973@shinkuro.com>, Andrew Sullivan writes:
> On Sat, Feb 13, 2010 at 11:13:16AM +1100, Mark Andrews wrote:
> > 
> > DNS64 does NOT affect A queries.  This is covered in "5.3.3. Other records"
> 
> Right.
> 
> > 	"All other RRs MUST be returned unchanged."
> > 
> > I see no wording equivalent to "Block A queries" in DNS64.
> 
> Exactly.  But DNS64 relies implicitly on the premise that clients will
> ask for AAAA first.

No it doesn't.  I relies on the premise that IPv6 only clients will ask
for AAAA records to initiate connections. 

> If they don't, then the end host gets an A record
> and it never uses the NAT64.  See others' remarks on why that's a bad
> idea in a dual-stack environment.

If they have a IPv4 path then using A's is not a issue.  If they
don't have a IPv4 path and don't ask for AAAA then they are broken.
It's not the job of the nameserver to fix broken applications.

> > A dual stack host / applicaion will make both AAAA and A queries
> > and provided it has been taught about the DNS64 prefix will
> 
> The "provided it has been taught" condition is unreasonable.  We're
> trying to arrange things so that clients don't need to be taught about
> all this, because from the POV of deploying having to upgrade every
> client is a non-starter.

It's not upgrading.  It's configuring.  It does not come close to
the point of being a non-starter.  My many years old boxes can be
configured to do this now.  It would be nice if there was automated
methods of passing this configuration information around and it's
really needed as the default rules are a heap of ~!#~ and the only
way to get sensible rules to all the boxes is to have a provisioning
system as each site is unique and this is without throwing DNS64 into
the mix.
 
> > taught the worst that will happen is that the traffic takes a
> > non-optimal path through the NAT64.
> 
> That's exactly my point, too.

And it won't hurt 99.9% of the traffic.  Very little traffic cares
whether it is going from IPv6 to IPv4.  For most applications that
do and you are dual stacked you can force the application to choose
the transport anyway.

This is "perfect" getting in the way of "good enough".

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From dthaler@microsoft.com  Mon Feb 15 18:43:55 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 741913A7C0C for <behave@core3.amsl.com>; Mon, 15 Feb 2010 18:43:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.546
X-Spam-Level: 
X-Spam-Status: No, score=-110.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, 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 0RxFL8RAPd-b for <behave@core3.amsl.com>; Mon, 15 Feb 2010 18:43:54 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 3A2373A7C0B for <behave@ietf.org>; Mon, 15 Feb 2010 18:43:54 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 15 Feb 2010 18:46:23 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 15 Feb 2010 18:45:26 -0800
Received: from TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.173]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Mon, 15 Feb 2010 18:45:25 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: "behave@ietf.org" <behave@ietf.org>
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-09
Thread-Index: AcqsGCm956AMvKnwQVi8+qsuuj5YFQClKACA
Date: Tue, 16 Feb 2010 02:45:24 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
References: <139a01caac18$2a031c80$c4f0200a@cisco.com>
In-Reply-To: <139a01caac18$2a031c80$c4f0200a@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
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Tue, 16 Feb 2010 02:43:55 -0000

Mostly editorial issues, but one substantial issue raised during
the 1st WGLC remains in sections 4.2 and 4.3.

Section 1.2:
> addresses [RFC3307] based on the unicast mapping rule.  However, if =20
> multicast address mapping rule is defined, the IP/ICMP header

s/multicast address mapping rule/a multicast address mapping mechanism/

Section 3:
> When IPv4 node performs path MTU discovery (by setting the Don't
      ^
Insert "an"

Section 3.1:
> workflow example of stateless translation is shown in Appendix of
                                                       ^
Insert "the"

Section 3.2:
> Note that if the IPv4 router =20
> did not set the MTU field (zero),

s/did not set the MTU field (zero)/set the MTU field to zero/

Section 3.3:
> In addition, the ICMP error =20
> messages contain for the packet in error, which needs to be =20
> translated just like a normal IP packet.

s/for the/the/

> This process SHOULD =20
> stop at first embedded header and drop the packet if it contains =20
> more.

s/first/the first/

Section 4:
> On the other hand, the recent study indicates that only 43.46% of

s/the/a/

Section 4.2:

> In this case, the =20
> translator can ether do stateful translation or map them to an IPv4 =20
> address block as a holder for all non IPv4-translatable IPv6 =20
> addresses in a stateless manner.

s/ether/either/

I don't understand what "map them to an IPv4 address block as a holder"
means.  I don't see anywhere in the doc where this is specified in
more detail, so this is not implementable as currently stated.
We need to either remove this phrase, or else see text that we can
get WG consensus on. =20

My preference would be to just remove that possibility and say:

 In this case, the translator can do stateful translation.

However, I'm open to seeing alternative text posted to the list.

Section 4.3:

> In addition, the ICMP error =20
> messages contain for the packet in error, which needs to be =20
> translated just like a normal IP packet.

s/for the/the/

> In this case, the translator can ether do stateful =20
> translation or map them to an IPv4 address block as a holder for all =20
> non IPv4-translatable IPv6 addresses.

Same comment as on section 4.2.

Section 4.4:

> If the reason of sending ICMPv6 is due to that the IPv6 source

Suggest:
"If the ICMPv6 error message is being sent because the IPv6 source"

Section 4.6:

> If the IP/ICMP translator also provides normal forwarding function,
                                         ^
Insert "a"

-Dave

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dan Wing
> Sent: Friday, February 12, 2010 11:19 AM
> To: behave@ietf.org
> Cc: draft-ietf-behave-v6v4-xlate@tools.ietf.org
> Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-09
>=20
> ** We need at least 5 reviewers to tell us this document is ready
> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
> ** with a subject line containing the document name, and "ready
> ** to submit to IESG" or "not ready to submit to IESG" in the
> ** message body.  If not ready to submit, please propose new text.
>=20
>=20
> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-09,
> ending in
> one week (Friday, February 19).  For reference, the first WGLC was for
> draft-ietf-behave-v6v4-xlate-05.
>=20
> draft-ietf-behave-v6v4-xlate-09 contains all feedback from the working
> group
> to date, including the feedback based on Ben Stasiewicz's analysis of
> ICMPv6
> behavior on the Internet and the resulting discussion on the mailing
> list,
> which resulted in a new sentence and a new paragraph between -07 and -
> 09.
> Differences between 07 and 09 are:
>=20
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-behave-v6v4-xlate-
> 07.txt&url2=3Ddr
> aft-ietf-behave-v6v4-xlate-09.txt
>=20
>=20
> Differences between 05 (first WGLC) and 09 (2nd WGLC) are:
>=20
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-behave-v6v4-xlate-
> 05.txt&url2=3Ddr
> aft-ietf-behave-v6v4-xlate-09.txt
>=20
> -d
>=20
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From xing@cernet.edu.cn  Tue Feb 16 03:38:43 2010
Return-Path: <xing@cernet.edu.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 E3FAC3A7CCE for <behave@core3.amsl.com>; Tue, 16 Feb 2010 03:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.441
X-Spam-Level: 
X-Spam-Status: No, score=0.441 tagged_above=-999 required=5 tests=[AWL=0.344,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 ezCWMcEQM+jd for <behave@core3.amsl.com>; Tue, 16 Feb 2010 03:38:43 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 9033D3A795E for <behave@ietf.org>; Tue, 16 Feb 2010 03:38:41 -0800 (PST)
Received: from [192.168.1.100]([119.41.189.87]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b7ab3bb; Tue, 16 Feb 2010 19:40:14 +0800
Message-ID: <4B7A840D.2070403@cernet.edu.cn>
Date: Tue, 16 Feb 2010 19:39:57 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <13a401caac18$636b4f10$c4f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF650CE3B8BE@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF650CE3B8BE@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: c6omVhXB
Cc: "draft-ietf-behave-v6v4-framework@tools.ietf.org" <draft-ietf-behave-v6v4-framework@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-framework-06
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, 16 Feb 2010 11:38:44 -0000

Hi, Dave,

Thanks. We will make modifications and upload version 07 after 2nd WGLC.

Regards,

xing, congxiao


Dave Thaler 写道:
> Just some editorial nits...
>
> Section 1.2:
>   
>> IPv4-only:  An IPv4-only implementation, in this context, comprises  
>>    an IPv4-enabled end system stack, applications directly or  
>>    indirectly using that IPv6 stack, plus routing in the network.  It
>>     
>                            ^^^^
> s/IPv6/IPv4/
>
> Section 1.3:
>   
>> greatly magnified.  The objective of the translators is to aviod, as
>>     
>
> s/aviod/avoid/
>
> Section 2.1:
>
>   
>> Both sateless [I-D.ietf-behave-v6v4-xlate] and stateful
>>     
>
> s/sateless/stateless/
>
> Section 3.2.2:
>
>   
>> from the IPv6 side itdoesn't support IPv4-initiation, and does not
>>     
>                       ^^^^^^
> Insert space
>
> -Dave
>
>
>   
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
>> Behalf Of Dan Wing
>> Sent: Friday, February 12, 2010 11:20 AM
>> To: behave@ietf.org
>> Cc: draft-ietf-behave-v6v4-framework@tools.ietf.org
>> Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-framework-06
>>
>> ** We need at least 5 reviewers to tell us this document is ready
>> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
>> ** with a subject line containing the document name, and "ready
>> ** to submit to IESG" or "not ready to submit to IESG" in the
>> ** message body.  If not ready to submit, please propose new text.
>>
>>
>> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-framework-06,
>> ending
>> in one week (Friday, February 19).  For reference, the first WGLC was
>> for
>> draft-ietf-behave-v6v4-framework-04.
>>
>> Differences from -04 (first WGLC) and -06 (2nd WGLC):
>>
>> http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-framework-
>> 04&url2=dr
>> aft-ietf-behave-v6v4-framework-06
>>
>> -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 xing@cernet.edu.cn  Tue Feb 16 03:40:22 2010
Return-Path: <xing@cernet.edu.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 33AF73A7CCE for <behave@core3.amsl.com>; Tue, 16 Feb 2010 03:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.384
X-Spam-Level: 
X-Spam-Status: No, score=0.384 tagged_above=-999 required=5 tests=[AWL=0.287,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 cJyom6QH0qsX for <behave@core3.amsl.com>; Tue, 16 Feb 2010 03:40:21 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id AAC533A7CE9 for <behave@ietf.org>; Tue, 16 Feb 2010 03:40:20 -0800 (PST)
Received: from [192.168.1.100]([119.41.189.87]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm1e4b7ab41e; Tue, 16 Feb 2010 19:41:52 +0800
Message-ID: <4B7A8483.5060908@cernet.edu.cn>
Date: Tue, 16 Feb 2010 19:41:55 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <139a01caac18$2a031c80$c4f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: caYoVhXB
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Tue, 16 Feb 2010 11:40:22 -0000

Hi, Dave,

Thanks. We will make modifications and upload version 10 after 2nd WGLC.

Regards,

xing, congxiao

Dave Thaler 写道:
> Mostly editorial issues, but one substantial issue raised during
> the 1st WGLC remains in sections 4.2 and 4.3.
>
> Section 1.2:
>   
>> addresses [RFC3307] based on the unicast mapping rule.  However, if  
>> multicast address mapping rule is defined, the IP/ICMP header
>>     
>
> s/multicast address mapping rule/a multicast address mapping mechanism/
>
> Section 3:
>   
>> When IPv4 node performs path MTU discovery (by setting the Don't
>>     
>       ^
> Insert "an"
>
> Section 3.1:
>   
>> workflow example of stateless translation is shown in Appendix of
>>     
>                                                        ^
> Insert "the"
>
> Section 3.2:
>   
>> Note that if the IPv4 router  
>> did not set the MTU field (zero),
>>     
>
> s/did not set the MTU field (zero)/set the MTU field to zero/
>
> Section 3.3:
>   
>> In addition, the ICMP error  
>> messages contain for the packet in error, which needs to be  
>> translated just like a normal IP packet.
>>     
>
> s/for the/the/
>
>   
>> This process SHOULD  
>> stop at first embedded header and drop the packet if it contains  
>> more.
>>     
>
> s/first/the first/
>
> Section 4:
>   
>> On the other hand, the recent study indicates that only 43.46% of
>>     
>
> s/the/a/
>
> Section 4.2:
>
>   
>> In this case, the  
>> translator can ether do stateful translation or map them to an IPv4  
>> address block as a holder for all non IPv4-translatable IPv6  
>> addresses in a stateless manner.
>>     
>
> s/ether/either/
>
> I don't understand what "map them to an IPv4 address block as a holder"
> means.  I don't see anywhere in the doc where this is specified in
> more detail, so this is not implementable as currently stated.
> We need to either remove this phrase, or else see text that we can
> get WG consensus on.  
>
> My preference would be to just remove that possibility and say:
>
>  In this case, the translator can do stateful translation.
>
> However, I'm open to seeing alternative text posted to the list.
>
> Section 4.3:
>
>   
>> In addition, the ICMP error  
>> messages contain for the packet in error, which needs to be  
>> translated just like a normal IP packet.
>>     
>
> s/for the/the/
>
>   
>> In this case, the translator can ether do stateful  
>> translation or map them to an IPv4 address block as a holder for all  
>> non IPv4-translatable IPv6 addresses.
>>     
>
> Same comment as on section 4.2.
>
> Section 4.4:
>
>   
>> If the reason of sending ICMPv6 is due to that the IPv6 source
>>     
>
> Suggest:
> "If the ICMPv6 error message is being sent because the IPv6 source"
>
> Section 4.6:
>
>   
>> If the IP/ICMP translator also provides normal forwarding function,
>>     
>                                          ^
> Insert "a"
>
> -Dave
>
>   
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
>> Behalf Of Dan Wing
>> Sent: Friday, February 12, 2010 11:19 AM
>> To: behave@ietf.org
>> Cc: draft-ietf-behave-v6v4-xlate@tools.ietf.org
>> Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-09
>>
>> ** We need at least 5 reviewers to tell us this document is ready
>> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
>> ** with a subject line containing the document name, and "ready
>> ** to submit to IESG" or "not ready to submit to IESG" in the
>> ** message body.  If not ready to submit, please propose new text.
>>
>>
>> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-09,
>> ending in
>> one week (Friday, February 19).  For reference, the first WGLC was for
>> draft-ietf-behave-v6v4-xlate-05.
>>
>> draft-ietf-behave-v6v4-xlate-09 contains all feedback from the working
>> group
>> to date, including the feedback based on Ben Stasiewicz's analysis of
>> ICMPv6
>> behavior on the Internet and the resulting discussion on the mailing
>> list,
>> which resulted in a new sentence and a new paragraph between -07 and -
>> 09.
>> Differences between 07 and 09 are:
>>
>> http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-
>> 07.txt&url2=dr
>> aft-ietf-behave-v6v4-xlate-09.txt
>>
>>
>> Differences between 05 (first WGLC) and 09 (2nd WGLC) are:
>>
>> http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-
>> 05.txt&url2=dr
>> aft-ietf-behave-v6v4-xlate-09.txt
>>
>> -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 xing@cernet.edu.cn  Tue Feb 16 03:53:02 2010
Return-Path: <xing@cernet.edu.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 2836F3A7816 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 03:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.343
X-Spam-Level: 
X-Spam-Status: No, score=0.343 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 xe5yL5qljw7G for <behave@core3.amsl.com>; Tue, 16 Feb 2010 03:53:01 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 8E32D3A7255 for <behave@ietf.org>; Tue, 16 Feb 2010 03:53:00 -0800 (PST)
Received: from [192.168.1.100]([119.41.189.87]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm1b4b7ab716; Tue, 16 Feb 2010 19:54:32 +0800
Message-ID: <4B7A877B.1030406@cernet.edu.cn>
Date: Tue, 16 Feb 2010 19:54:35 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <139a01caac18$2a031c80$c4f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: cUeAWhXB
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Tue, 16 Feb 2010 11:53:02 -0000

Hi, Dave,

Dave Thaler 写道:
> Mostly editorial issues, but one substantial issue raised during
> the 1st WGLC remains in sections 4.2 and 4.3.
>   
> I don't understand what "map them to an IPv4 address block as a holder"
> means.  I don't see anywhere in the doc where this is specified in
> more detail, so this is not implementable as currently stated.
> We need to either remove this phrase, or else see text that we can
> get WG consensus on.  
>
> My preference would be to just remove that possibility and say:
>
>  In this case, the translator can do stateful translation.
>
> However, I'm open to seeing alternative text posted to the list.
>
> Section 4.3:
>
>   
Thanks. Sorry that we did not make our idea clear enough in the draft 
and it is somehow complicated. We will write another draft to discuss 
this issue. For the xlate draft, we would like to say

 In this case, the translator MAY do stateful translation.


BTW, we have discussed this issue in a mail dated Jan 14, 2010 (attached 
here).

Regards,

xing, congxiao

------------------------ cut here -------------------------

>From - Thu Jan 14 16:49:26 2010
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00800000
X-Mozilla-Keys:                                                                                 
Message-ID: <4B4ED7D8.50803@cernet.edu.cn>
Date: Thu, 14 Jan 2010 16:37:44 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
CC: Dan Wing <dwing@cisco.com>, congxiao <congxiao@cernet.edu.cn>, 
 Fred Baker <fred@cisco.com>,
 Xing Li <xing@cernet.edu.cn>
Subject: Re: [BEHAVE] Comments on draft-ietf-behave-v6v4-xlate-05
References: <E4561B14EE2A3E4E9D478EBFB5416E1B29B9475E@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <4B434F6C.8070000@cernet.edu.cn> <9B57C850BB53634CACEC56EF4853FF6505D96F@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF6505D96F@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi, Dave,

Dave Thaler 写道:
>
>> Section 3.1 discusses the way to translate normal IP packets:
>> (1) When the source address is IPv4-translatable address, do stateless
>> translation.
>> (2) When the source address is non IPv4-translatable address, do the
>> stateful translation.
>>
>> Section 3.2 and 3.3 discuss the way to translate ICMP packets and the
>> ICMP Error packets:
>> (1) If the ICMP packets or ICMP Error packets are generated from the
>> end
>> system,
>> (1.1) For the stateless translation, the source address is the
>> IPv4-translatable address and it can be translated to the IPv4 address.
>> (1.2) For the stateful translation, the source address is any IPv6
>> address, but it should be in the state table for a given session, it
>> can
>> be translated to the IPv4 address.
>> (2) If the ICMP packets or ICMP Error packets are generated from an
>> intermediate router (for example TTL=0)
>> (2.1) For the stateless translation, the source address is usually not
>> the IPv4-translatable address and it can not be translated to the IPv4
>> address.
>> (2.2) For the stateful translation, the source address is usually not
>> in
>> the state table, it can not be translated to the IPv4 address.
>>
>> However, the ICMP message is important for PMTU or trouble shooting, we
>> should use a "IPv4 special block" as the source address for the ICMP
>> packets. This prevents translated ICMP messages from being discarded
>> due
>> to unknown or private IP source address.
>>     
>
> I don't understand why this would be needed.  As 3.1 behavior would do,
> if you get an ICMP error sourced from an IPv6 address that isn't an
> IPv4 translatable address, you can just do stateful transition and treat
> it the same as you would an ICMP session initiated by the sender.
> This seems much simpler than specifying some other special case.
>
> -Dave
>   
Thanks for the comment. The reasons for specifying this special case are:

(1) For the stateful or stateless/stateful translators, it is possible 
to do stateful translation for the ICMP packets. However, for a (pure) 
stateless translator, the translator cannot do the stateful translation. 
The method proposed above can help in this scenario.

(2) It is a waste of global routable IPv4 addresses for the mapping of 
the IPv6 source addresses of the ICMP packets. Since the IPv4 addresses 
are not used for the real communication between IPv4 end system and IPv6 
end system, but rather for the error reporting concerning the network 
problem. In addition, since there is no port number defined in ICMP, the 
sharing of a single IPv4 address for different non IPv4-translatable 
IPv6 addresses is difficult. Comparing with the above method, the 
special IPv4 block (we may define it as a new Well-Known IPv4 block) can 
be reused by different ISPs.

(3) The special IPv4 block actually servers as the holder of non 
IPv4-translatable IPv6 address in the ICMP packets. It can serve as an 
identifier to tell the end user or system administrator that the ICMP 
packets are generated by non IPv4-translatable IPv6 address. On the 
other hand, the stateful translation of the ICMP packets cannot indicate 
that the ICMP packets are generated by non IPv4-translatable IPv6 
addresses, since the IPv4 source addresses of the ICMP packets are 
general IPv4 addresses and there is no way to know the mapping between 
the IPv4 and IPv6 addresses (the states are maintained inside the 
translator).

(4) Generating states trigged by ICMP packets rather than the IP packets 
in the translator may introduce security problems.

Based on the above reasons, we believe that the method proposed above is 
useful not only for the stateless translators, but also useful for the 
stateful translators. However, we are fine to remove it from the current 
xlate document and willing to write a separate draft to document it.

Regards,

xing, congxiao







From ajs@shinkuro.com  Tue Feb 16 05:59:08 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 913C23A7D06 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 05:59:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.051
X-Spam-Level: 
X-Spam-Status: No, score=-2.051 tagged_above=-999 required=5 tests=[AWL=0.548,  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 zmUwgPgH-V4I for <behave@core3.amsl.com>; Tue, 16 Feb 2010 05:59:07 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id C166B3A7D0A for <behave@ietf.org>; Tue, 16 Feb 2010 05:59:07 -0800 (PST)
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 642191ECB402 for <behave@ietf.org>; Tue, 16 Feb 2010 14:00:41 +0000 (UTC)
Date: Tue, 16 Feb 2010 09:00:39 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100216140039.GF36083@shinkuro.com>
References: <20100212195141.GR14996@shinkuro.com> <201002130013.o1D0DGEN046772@drugs.dv.isc.org> <20100215150544.GG25973@shinkuro.com> <201002152242.o1FMgZnl097630@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201002152242.o1FMgZnl097630@drugs.dv.isc.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 16 Feb 2010 13:59:08 -0000

On Tue, Feb 16, 2010 at 09:42:35AM +1100, Mark Andrews wrote:
> > Exactly.  But DNS64 relies implicitly on the premise that clients will
> > ask for AAAA first.
> 
> No it doesn't.  I relies on the premise that IPv6 only clients will ask
> for AAAA records to initiate connections. 

It's interesting to me that you and I have different ideas of what the
underlying assumption is.  I really have been relying on the
assumption that v6-desiring clients will ask for AAAA records first.
It's my understanding that implementers have been encouraged to ask
for AAAA first, modulo certain conditions, and I have also been under
the impression that this behaviour is widespread.  Are you suggesting
otherwise?

> It's not upgrading.  It's configuring.  It does not come close to
> the point of being a non-starter.  My many years old boxes can be
> configured to do this now.  It would be nice if there was automated
> methods of passing this configuration information around and it's

So how is "install automated methods of passing the configuration
information around" not "upgrade the boxes"?  It might not be the
resolver that needs upgrading, but you still need to touch the client
system, or it won't know how to get the automatic configuration.  No?

A

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

From marka@isc.org  Tue Feb 16 06:51:17 2010
Return-Path: <marka@isc.org>
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 B0F7A3A7698 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 06:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  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 4dlI+ohy3cir for <behave@core3.amsl.com>; Tue, 16 Feb 2010 06:51:16 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id AE90E3A68D6 for <behave@ietf.org>; Tue, 16 Feb 2010 06:51:16 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 63E81E60A7; Tue, 16 Feb 2010 14:52:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1GEqju0086328; Wed, 17 Feb 2010 01:52:45 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002161452.o1GEqju0086328@drugs.dv.isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
From: Mark Andrews <marka@isc.org>
References: <20100212195141.GR14996@shinkuro.com> <201002130013.o1D0DGEN046772@drugs.dv.isc.org> <20100215150544.GG25973@shinkuro.com> <201002152242.o1FMgZnl097630@drugs.dv.isc.org> <20100216140039.GF36083@shinkuro.com> 
In-reply-to: Your message of "Tue, 16 Feb 2010 09:00:39 CDT." <20100216140039.GF36083@shinkuro.com> 
Date: Wed, 17 Feb 2010 01:52:45 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 16 Feb 2010 14:51:17 -0000

In message <20100216140039.GF36083@shinkuro.com>, Andrew Sullivan writes:
> On Tue, Feb 16, 2010 at 09:42:35AM +1100, Mark Andrews wrote:
> > > Exactly.  But DNS64 relies implicitly on the premise that clients will
> > > ask for AAAA first.
> > 
> > No it doesn't.  I relies on the premise that IPv6 only clients will ask
> > for AAAA records to initiate connections. 
> 
> It's interesting to me that you and I have different ideas of what the
> underlying assumption is.  I really have been relying on the
> assumption that v6-desiring clients will ask for AAAA records first.
> It's my understanding that implementers have been encouraged to ask
> for AAAA first, modulo certain conditions, and I have also been under
> the impression that this behaviour is widespread.  Are you suggesting
> otherwise?

Dual stack will ask for both.  getaddrinfo() will sort non-mapped
AAAA records to the start of the list, using default sorting rules,
but will return both to the application.  Single stack will ask for
the appropriate record for the stack.
 
> > It's not upgrading.  It's configuring.  It does not come close to
> > the point of being a non-starter.  My many years old boxes can be
> > configured to do this now.  It would be nice if there was automated
> > methods of passing this configuration information around and it's
> 
> So how is "install automated methods of passing the configuration
> information around" not "upgrade the boxes"?  It might not be the
> resolver that needs upgrading, but you still need to touch the client
> system, or it won't know how to get the automatic configuration.  No?

It will work without being touched.   It will work *better* if it
is touched or upgraded to support automated methods of passing
configuration around.

It's a show stopper if it will NOT work without being touched.  This
is not the case however.
 
> A
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From dthaler@microsoft.com  Tue Feb 16 08:06:02 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 7DCE23A7D54 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 08:06:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.551
X-Spam-Level: 
X-Spam-Status: No, score=-110.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, 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 W4KXrFce12lt for <behave@core3.amsl.com>; Tue, 16 Feb 2010 08:06:01 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 4B17D3A7D44 for <behave@ietf.org>; Tue, 16 Feb 2010 08:06:01 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 16 Feb 2010 08:08:32 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.0.639.21; Tue, 16 Feb 2010 08:07:35 -0800
Received: from TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.173]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 16 Feb 2010 08:07:37 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Xing Li <xing@cernet.edu.cn>
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-09
Thread-Index: AcqsGCm956AMvKnwQVi8+qsuuj5YFQClKACAACVE1IAAB/orEA==
Date: Tue, 16 Feb 2010 16:07:33 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF650CE3C994@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
References: <139a01caac18$2a031c80$c4f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <4B7A877B.1030406@cernet.edu.cn>
In-Reply-To: <4B7A877B.1030406@cernet.edu.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Tue, 16 Feb 2010 16:06:02 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBYaW5nIExpIFttYWlsdG86eGlu
Z0BjZXJuZXQuZWR1LmNuXQ0KPiBTZW50OiBUdWVzZGF5LCBGZWJydWFyeSAxNiwgMjAxMCAzOjU1
IEFNDQo+IFRvOiBEYXZlIFRoYWxlcg0KPiBDYzogYmVoYXZlQGlldGYub3JnDQo+IFN1YmplY3Q6
IFJlOiBbQkVIQVZFXSAybmQgV0dMQywgZHJhZnQtaWV0Zi1iZWhhdmUtdjZ2NC14bGF0ZS0wOQ0K
PiANCj4gSGksIERhdmUsDQo+IA0KPiBEYXZlIFRoYWxlciDlhpnpgZM6DQo+ID4gTW9zdGx5IGVk
aXRvcmlhbCBpc3N1ZXMsIGJ1dCBvbmUgc3Vic3RhbnRpYWwgaXNzdWUgcmFpc2VkIGR1cmluZw0K
PiA+IHRoZSAxc3QgV0dMQyByZW1haW5zIGluIHNlY3Rpb25zIDQuMiBhbmQgNC4zLg0KPiA+DQo+
ID4gSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgIm1hcCB0aGVtIHRvIGFuIElQdjQgYWRkcmVzcyBi
bG9jayBhcyBhDQo+IGhvbGRlciINCj4gPiBtZWFucy4gIEkgZG9uJ3Qgc2VlIGFueXdoZXJlIGlu
IHRoZSBkb2Mgd2hlcmUgdGhpcyBpcyBzcGVjaWZpZWQgaW4NCj4gPiBtb3JlIGRldGFpbCwgc28g
dGhpcyBpcyBub3QgaW1wbGVtZW50YWJsZSBhcyBjdXJyZW50bHkgc3RhdGVkLg0KPiA+IFdlIG5l
ZWQgdG8gZWl0aGVyIHJlbW92ZSB0aGlzIHBocmFzZSwgb3IgZWxzZSBzZWUgdGV4dCB0aGF0IHdl
IGNhbg0KPiA+IGdldCBXRyBjb25zZW5zdXMgb24uDQo+ID4NCj4gPiBNeSBwcmVmZXJlbmNlIHdv
dWxkIGJlIHRvIGp1c3QgcmVtb3ZlIHRoYXQgcG9zc2liaWxpdHkgYW5kIHNheToNCj4gPg0KPiA+
ICBJbiB0aGlzIGNhc2UsIHRoZSB0cmFuc2xhdG9yIGNhbiBkbyBzdGF0ZWZ1bCB0cmFuc2xhdGlv
bi4NCj4gPg0KPiA+IEhvd2V2ZXIsIEknbSBvcGVuIHRvIHNlZWluZyBhbHRlcm5hdGl2ZSB0ZXh0
IHBvc3RlZCB0byB0aGUgbGlzdC4NCj4gPg0KPiA+IFNlY3Rpb24gNC4zOg0KPiA+DQo+ID4NCj4g
VGhhbmtzLiBTb3JyeSB0aGF0IHdlIGRpZCBub3QgbWFrZSBvdXIgaWRlYSBjbGVhciBlbm91Z2gg
aW4gdGhlIGRyYWZ0DQo+IGFuZCBpdCBpcyBzb21laG93IGNvbXBsaWNhdGVkLiBXZSB3aWxsIHdy
aXRlIGFub3RoZXIgZHJhZnQgdG8gZGlzY3Vzcw0KPiB0aGlzIGlzc3VlLiBGb3IgdGhlIHhsYXRl
IGRyYWZ0LCB3ZSB3b3VsZCBsaWtlIHRvIHNheQ0KPiANCj4gIEluIHRoaXMgY2FzZSwgdGhlIHRy
YW5zbGF0b3IgTUFZIGRvIHN0YXRlZnVsIHRyYW5zbGF0aW9uLg0KDQpJIGRvbid0IGJlbGlldmUg
YSBNQVkgaXMgYXBwcm9wcmlhdGUgdW5sZXNzIGl0J3MgY2xlYXIgd2hhdCB0aGUNCmFsdGVybmF0
aXZlIGlzIGluIHRoZSBkb2N1bWVudC4gIEluIHRoZSBhYm92ZSB0ZXh0LCBpdCBpc24ndC4NCg0K
TWF5YmUgc29tZXRoaW5nIGxpa2U6DQoNCiAgIEluIHRoaXMgY2FzZSwgdGhlIHRyYW5zbGF0b3Ig
Y2FuIGRvIHN0YXRlZnVsIHRyYW5zbGF0aW9uLg0KICAgQSBtZWNoYW5pc20gYnkgd2hpY2ggdGhl
IHRyYW5zbGF0b3IgY2FuIGluc3RlYWQgZG8gDQogICBzdGF0ZWxlc3MgdHJhbnNsYXRpb24gaXMg
bGVmdCBmb3IgZnV0dXJlIHdvcmsuDQoNCi1EYXZlDQoNCj4gDQo+IA0KPiBCVFcsIHdlIGhhdmUg
ZGlzY3Vzc2VkIHRoaXMgaXNzdWUgaW4gYSBtYWlsIGRhdGVkIEphbiAxNCwgMjAxMA0KPiAoYXR0
YWNoZWQNCj4gaGVyZSkuDQo+IA0KPiBSZWdhcmRzLA0KPiANCj4geGluZywgY29uZ3hpYW8NCj4g
DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSBjdXQgaGVyZSAtLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+IA0KPiBGcm9tIC0gVGh1IEphbiAxNCAxNjo0OToyNiAyMDEwDQo+IFgtTW96aWxs
YS1TdGF0dXM6IDAwMDENCj4gWC1Nb3ppbGxhLVN0YXR1czI6IDAwODAwMDAwDQo+IFgtTW96aWxs
YS1LZXlzOg0KPiBNZXNzYWdlLUlEOiA8NEI0RUQ3RDguNTA4MDNAY2VybmV0LmVkdS5jbj4NCj4g
RGF0ZTogVGh1LCAxNCBKYW4gMjAxMCAxNjozNzo0NCArMDgwMA0KPiBGcm9tOiBYaW5nIExpIDx4
aW5nQGNlcm5ldC5lZHUuY24+DQo+IFVzZXItQWdlbnQ6IFRodW5kZXJiaXJkIDIuMC4wLjIzIChX
aW5kb3dzLzIwMDkwODEyKQ0KPiBNSU1FLVZlcnNpb246IDEuMA0KPiBUbzogRGF2ZSBUaGFsZXIg
PGR0aGFsZXJAbWljcm9zb2Z0LmNvbT4NCj4gQ0M6IERhbiBXaW5nIDxkd2luZ0BjaXNjby5jb20+
LCBjb25neGlhbyA8Y29uZ3hpYW9AY2VybmV0LmVkdS5jbj4sDQo+ICBGcmVkIEJha2VyIDxmcmVk
QGNpc2NvLmNvbT4sDQo+ICBYaW5nIExpIDx4aW5nQGNlcm5ldC5lZHUuY24+DQo+IFN1YmplY3Q6
IFJlOiBbQkVIQVZFXSBDb21tZW50cyBvbiBkcmFmdC1pZXRmLWJlaGF2ZS12NnY0LXhsYXRlLTA1
DQo+IFJlZmVyZW5jZXM6DQo+IDxFNDU2MUIxNEVFMkEzRTRFOUQ0NzhFQkZCNTQxNkUxQjI5Qjk0
NzVFQFRLNUVYMTRNQlhXNjUxLndpbmdyb3VwLndpbmRlDQo+IHBsb3kubnRkZXYubWljcm9zb2Z0
LmNvbT4gPDRCNDM0RjZDLjgwNzAwMDBAY2VybmV0LmVkdS5jbj4NCj4gPDlCNTdDODUwQkI1MzYz
NENBQ0VDNTZFRjQ4NTNGRjY1MDVEOTZGQFRLNUVYMTRNQlhXNjAxLndpbmdyb3VwLndpbmRlcGwN
Cj4gb3kubnRkZXYubWljcm9zb2Z0LmNvbT4NCj4gSW4tUmVwbHktVG86DQo+IDw5QjU3Qzg1MEJC
NTM2MzRDQUNFQzU2RUY0ODUzRkY2NTA1RDk2RkBUSzVFWDE0TUJYVzYwMS53aW5ncm91cC53aW5k
ZXBsDQo+IG95Lm50ZGV2Lm1pY3Jvc29mdC5jb20+DQo+IENvbnRlbnQtVHlwZTogdGV4dC9wbGFp
bjsgY2hhcnNldD1VVEYtODsgZm9ybWF0PWZsb3dlZA0KPiBDb250ZW50LVRyYW5zZmVyLUVuY29k
aW5nOiA4Yml0DQo+IA0KPiBIaSwgRGF2ZSwNCj4gDQo+IERhdmUgVGhhbGVyIOWGmemBkzoNCj4g
Pg0KPiA+PiBTZWN0aW9uIDMuMSBkaXNjdXNzZXMgdGhlIHdheSB0byB0cmFuc2xhdGUgbm9ybWFs
IElQIHBhY2tldHM6DQo+ID4+ICgxKSBXaGVuIHRoZSBzb3VyY2UgYWRkcmVzcyBpcyBJUHY0LXRy
YW5zbGF0YWJsZSBhZGRyZXNzLCBkbw0KPiBzdGF0ZWxlc3MNCj4gPj4gdHJhbnNsYXRpb24uDQo+
ID4+ICgyKSBXaGVuIHRoZSBzb3VyY2UgYWRkcmVzcyBpcyBub24gSVB2NC10cmFuc2xhdGFibGUg
YWRkcmVzcywgZG8gdGhlDQo+ID4+IHN0YXRlZnVsIHRyYW5zbGF0aW9uLg0KPiA+Pg0KPiA+PiBT
ZWN0aW9uIDMuMiBhbmQgMy4zIGRpc2N1c3MgdGhlIHdheSB0byB0cmFuc2xhdGUgSUNNUCBwYWNr
ZXRzIGFuZA0KPiB0aGUNCj4gPj4gSUNNUCBFcnJvciBwYWNrZXRzOg0KPiA+PiAoMSkgSWYgdGhl
IElDTVAgcGFja2V0cyBvciBJQ01QIEVycm9yIHBhY2tldHMgYXJlIGdlbmVyYXRlZCBmcm9tIHRo
ZQ0KPiA+PiBlbmQNCj4gPj4gc3lzdGVtLA0KPiA+PiAoMS4xKSBGb3IgdGhlIHN0YXRlbGVzcyB0
cmFuc2xhdGlvbiwgdGhlIHNvdXJjZSBhZGRyZXNzIGlzIHRoZQ0KPiA+PiBJUHY0LXRyYW5zbGF0
YWJsZSBhZGRyZXNzIGFuZCBpdCBjYW4gYmUgdHJhbnNsYXRlZCB0byB0aGUgSVB2NA0KPiBhZGRy
ZXNzLg0KPiA+PiAoMS4yKSBGb3IgdGhlIHN0YXRlZnVsIHRyYW5zbGF0aW9uLCB0aGUgc291cmNl
IGFkZHJlc3MgaXMgYW55IElQdjYNCj4gPj4gYWRkcmVzcywgYnV0IGl0IHNob3VsZCBiZSBpbiB0
aGUgc3RhdGUgdGFibGUgZm9yIGEgZ2l2ZW4gc2Vzc2lvbiwgaXQNCj4gPj4gY2FuDQo+ID4+IGJl
IHRyYW5zbGF0ZWQgdG8gdGhlIElQdjQgYWRkcmVzcy4NCj4gPj4gKDIpIElmIHRoZSBJQ01QIHBh
Y2tldHMgb3IgSUNNUCBFcnJvciBwYWNrZXRzIGFyZSBnZW5lcmF0ZWQgZnJvbSBhbg0KPiA+PiBp
bnRlcm1lZGlhdGUgcm91dGVyIChmb3IgZXhhbXBsZSBUVEw9MCkNCj4gPj4gKDIuMSkgRm9yIHRo
ZSBzdGF0ZWxlc3MgdHJhbnNsYXRpb24sIHRoZSBzb3VyY2UgYWRkcmVzcyBpcyB1c3VhbGx5DQo+
IG5vdA0KPiA+PiB0aGUgSVB2NC10cmFuc2xhdGFibGUgYWRkcmVzcyBhbmQgaXQgY2FuIG5vdCBi
ZSB0cmFuc2xhdGVkIHRvIHRoZQ0KPiBJUHY0DQo+ID4+IGFkZHJlc3MuDQo+ID4+ICgyLjIpIEZv
ciB0aGUgc3RhdGVmdWwgdHJhbnNsYXRpb24sIHRoZSBzb3VyY2UgYWRkcmVzcyBpcyB1c3VhbGx5
DQo+IG5vdA0KPiA+PiBpbg0KPiA+PiB0aGUgc3RhdGUgdGFibGUsIGl0IGNhbiBub3QgYmUgdHJh
bnNsYXRlZCB0byB0aGUgSVB2NCBhZGRyZXNzLg0KPiA+Pg0KPiA+PiBIb3dldmVyLCB0aGUgSUNN
UCBtZXNzYWdlIGlzIGltcG9ydGFudCBmb3IgUE1UVSBvciB0cm91YmxlIHNob290aW5nLA0KPiB3
ZQ0KPiA+PiBzaG91bGQgdXNlIGEgIklQdjQgc3BlY2lhbCBibG9jayIgYXMgdGhlIHNvdXJjZSBh
ZGRyZXNzIGZvciB0aGUgSUNNUA0KPiA+PiBwYWNrZXRzLiBUaGlzIHByZXZlbnRzIHRyYW5zbGF0
ZWQgSUNNUCBtZXNzYWdlcyBmcm9tIGJlaW5nIGRpc2NhcmRlZA0KPiA+PiBkdWUNCj4gPj4gdG8g
dW5rbm93biBvciBwcml2YXRlIElQIHNvdXJjZSBhZGRyZXNzLg0KPiA+Pg0KPiA+DQo+ID4gSSBk
b24ndCB1bmRlcnN0YW5kIHdoeSB0aGlzIHdvdWxkIGJlIG5lZWRlZC4gIEFzIDMuMSBiZWhhdmlv
ciB3b3VsZA0KPiBkbywNCj4gPiBpZiB5b3UgZ2V0IGFuIElDTVAgZXJyb3Igc291cmNlZCBmcm9t
IGFuIElQdjYgYWRkcmVzcyB0aGF0IGlzbid0IGFuDQo+ID4gSVB2NCB0cmFuc2xhdGFibGUgYWRk
cmVzcywgeW91IGNhbiBqdXN0IGRvIHN0YXRlZnVsIHRyYW5zaXRpb24gYW5kDQo+IHRyZWF0DQo+
ID4gaXQgdGhlIHNhbWUgYXMgeW91IHdvdWxkIGFuIElDTVAgc2Vzc2lvbiBpbml0aWF0ZWQgYnkg
dGhlIHNlbmRlci4NCj4gPiBUaGlzIHNlZW1zIG11Y2ggc2ltcGxlciB0aGFuIHNwZWNpZnlpbmcg
c29tZSBvdGhlciBzcGVjaWFsIGNhc2UuDQo+ID4NCj4gPiAtRGF2ZQ0KPiA+DQo+IFRoYW5rcyBm
b3IgdGhlIGNvbW1lbnQuIFRoZSByZWFzb25zIGZvciBzcGVjaWZ5aW5nIHRoaXMgc3BlY2lhbCBj
YXNlDQo+IGFyZToNCj4gDQo+ICgxKSBGb3IgdGhlIHN0YXRlZnVsIG9yIHN0YXRlbGVzcy9zdGF0
ZWZ1bCB0cmFuc2xhdG9ycywgaXQgaXMgcG9zc2libGUNCj4gdG8gZG8gc3RhdGVmdWwgdHJhbnNs
YXRpb24gZm9yIHRoZSBJQ01QIHBhY2tldHMuIEhvd2V2ZXIsIGZvciBhIChwdXJlKQ0KPiBzdGF0
ZWxlc3MgdHJhbnNsYXRvciwgdGhlIHRyYW5zbGF0b3IgY2Fubm90IGRvIHRoZSBzdGF0ZWZ1bA0K
PiB0cmFuc2xhdGlvbi4NCj4gVGhlIG1ldGhvZCBwcm9wb3NlZCBhYm92ZSBjYW4gaGVscCBpbiB0
aGlzIHNjZW5hcmlvLg0KPiANCj4gKDIpIEl0IGlzIGEgd2FzdGUgb2YgZ2xvYmFsIHJvdXRhYmxl
IElQdjQgYWRkcmVzc2VzIGZvciB0aGUgbWFwcGluZyBvZg0KPiB0aGUgSVB2NiBzb3VyY2UgYWRk
cmVzc2VzIG9mIHRoZSBJQ01QIHBhY2tldHMuIFNpbmNlIHRoZSBJUHY0IGFkZHJlc3Nlcw0KPiBh
cmUgbm90IHVzZWQgZm9yIHRoZSByZWFsIGNvbW11bmljYXRpb24gYmV0d2VlbiBJUHY0IGVuZCBz
eXN0ZW0gYW5kDQo+IElQdjYNCj4gZW5kIHN5c3RlbSwgYnV0IHJhdGhlciBmb3IgdGhlIGVycm9y
IHJlcG9ydGluZyBjb25jZXJuaW5nIHRoZSBuZXR3b3JrDQo+IHByb2JsZW0uIEluIGFkZGl0aW9u
LCBzaW5jZSB0aGVyZSBpcyBubyBwb3J0IG51bWJlciBkZWZpbmVkIGluIElDTVAsDQo+IHRoZQ0K
PiBzaGFyaW5nIG9mIGEgc2luZ2xlIElQdjQgYWRkcmVzcyBmb3IgZGlmZmVyZW50IG5vbiBJUHY0
LXRyYW5zbGF0YWJsZQ0KPiBJUHY2IGFkZHJlc3NlcyBpcyBkaWZmaWN1bHQuIENvbXBhcmluZyB3
aXRoIHRoZSBhYm92ZSBtZXRob2QsIHRoZQ0KPiBzcGVjaWFsIElQdjQgYmxvY2sgKHdlIG1heSBk
ZWZpbmUgaXQgYXMgYSBuZXcgV2VsbC1Lbm93biBJUHY0IGJsb2NrKQ0KPiBjYW4NCj4gYmUgcmV1
c2VkIGJ5IGRpZmZlcmVudCBJU1BzLg0KPiANCj4gKDMpIFRoZSBzcGVjaWFsIElQdjQgYmxvY2sg
YWN0dWFsbHkgc2VydmVycyBhcyB0aGUgaG9sZGVyIG9mIG5vbg0KPiBJUHY0LXRyYW5zbGF0YWJs
ZSBJUHY2IGFkZHJlc3MgaW4gdGhlIElDTVAgcGFja2V0cy4gSXQgY2FuIHNlcnZlIGFzIGFuDQo+
IGlkZW50aWZpZXIgdG8gdGVsbCB0aGUgZW5kIHVzZXIgb3Igc3lzdGVtIGFkbWluaXN0cmF0b3Ig
dGhhdCB0aGUgSUNNUA0KPiBwYWNrZXRzIGFyZSBnZW5lcmF0ZWQgYnkgbm9uIElQdjQtdHJhbnNs
YXRhYmxlIElQdjYgYWRkcmVzcy4gT24gdGhlDQo+IG90aGVyIGhhbmQsIHRoZSBzdGF0ZWZ1bCB0
cmFuc2xhdGlvbiBvZiB0aGUgSUNNUCBwYWNrZXRzIGNhbm5vdA0KPiBpbmRpY2F0ZQ0KPiB0aGF0
IHRoZSBJQ01QIHBhY2tldHMgYXJlIGdlbmVyYXRlZCBieSBub24gSVB2NC10cmFuc2xhdGFibGUg
SVB2Ng0KPiBhZGRyZXNzZXMsIHNpbmNlIHRoZSBJUHY0IHNvdXJjZSBhZGRyZXNzZXMgb2YgdGhl
IElDTVAgcGFja2V0cyBhcmUNCj4gZ2VuZXJhbCBJUHY0IGFkZHJlc3NlcyBhbmQgdGhlcmUgaXMg
bm8gd2F5IHRvIGtub3cgdGhlIG1hcHBpbmcgYmV0d2Vlbg0KPiB0aGUgSVB2NCBhbmQgSVB2NiBh
ZGRyZXNzZXMgKHRoZSBzdGF0ZXMgYXJlIG1haW50YWluZWQgaW5zaWRlIHRoZQ0KPiB0cmFuc2xh
dG9yKS4NCj4gDQo+ICg0KSBHZW5lcmF0aW5nIHN0YXRlcyB0cmlnZ2VkIGJ5IElDTVAgcGFja2V0
cyByYXRoZXIgdGhhbiB0aGUgSVANCj4gcGFja2V0cw0KPiBpbiB0aGUgdHJhbnNsYXRvciBtYXkg
aW50cm9kdWNlIHNlY3VyaXR5IHByb2JsZW1zLg0KPiANCj4gQmFzZWQgb24gdGhlIGFib3ZlIHJl
YXNvbnMsIHdlIGJlbGlldmUgdGhhdCB0aGUgbWV0aG9kIHByb3Bvc2VkIGFib3ZlDQo+IGlzDQo+
IHVzZWZ1bCBub3Qgb25seSBmb3IgdGhlIHN0YXRlbGVzcyB0cmFuc2xhdG9ycywgYnV0IGFsc28g
dXNlZnVsIGZvciB0aGUNCj4gc3RhdGVmdWwgdHJhbnNsYXRvcnMuIEhvd2V2ZXIsIHdlIGFyZSBm
aW5lIHRvIHJlbW92ZSBpdCBmcm9tIHRoZQ0KPiBjdXJyZW50DQo+IHhsYXRlIGRvY3VtZW50IGFu
ZCB3aWxsaW5nIHRvIHdyaXRlIGEgc2VwYXJhdGUgZHJhZnQgdG8gZG9jdW1lbnQgaXQuDQo+IA0K
PiBSZWdhcmRzLA0KPiANCj4geGluZywgY29uZ3hpYW8NCj4gDQo+IA0KPiANCj4gDQo+IA0KPiAN
Cg0K

From ajs@shinkuro.com  Tue Feb 16 11:11:58 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 610C428C13E for <behave@core3.amsl.com>; Tue, 16 Feb 2010 11:11:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[AWL=0.579,  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 j2odjwl5EeXw for <behave@core3.amsl.com>; Tue, 16 Feb 2010 11:11:50 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 8EC033A7D75 for <behave@ietf.org>; Tue, 16 Feb 2010 11:11:43 -0800 (PST)
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 5BFF71ECBBD7 for <behave@ietf.org>; Tue, 16 Feb 2010 19:13:17 +0000 (UTC)
Date: Tue, 16 Feb 2010 14:13:15 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100216191315.GL36083@shinkuro.com>
References: <20100212195141.GR14996@shinkuro.com> <201002130013.o1D0DGEN046772@drugs.dv.isc.org> <20100215150544.GG25973@shinkuro.com> <201002152242.o1FMgZnl097630@drugs.dv.isc.org> <20100216140039.GF36083@shinkuro.com> <201002161452.o1GEqju0086328@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201002161452.o1GEqju0086328@drugs.dv.isc.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 16 Feb 2010 19:11:58 -0000

On Wed, Feb 17, 2010 at 01:52:45AM +1100, Mark Andrews wrote:
> Dual stack will ask for both.  getaddrinfo() will sort non-mapped
> AAAA records to the start of the list, using default sorting rules,
> but will return both to the application.  Single stack will ask for
> the appropriate record for the stack.

Ah, I see where we're missing each other.  I think the idea that we're
going to have many applications properly sensitive to this is
optimistic at best.

> It will work without being touched.   It will work *better* if it
> is touched or upgraded to support automated methods of passing
> configuration around.

Ok.  Note that that does not seem to be the goal of the I-D we started
talking about, however.  It's pretty hard to tell to tell from the
sketchy draft as it stands, but it seems to be aiming at supporting
unmodified dual-stack hosts behind a NAT64+DNS64, and doing that
without having them use the NAT when they could use native v4 transit.
At least, that's the only sense I can make of it.  Otherwise, there's
no need for a draft: dual-stack hosts behind a NAT64 will just use the
NAT, and who cares; applications that do care can behave how they need
to do.

If you were going to modify the end points to deal with this
condition, why not teach them about v4 _and_ v6, teach them to do
their own resolution, and teach them to prefer native v6 when
available and native v4 when available, preferring native v6 over all
things.  This is not hard to teach an end host; but we've been
operating on the assumption that the end hosts are too numerous and
cumbersome to upgrade. 

A

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

From brian.e.carpenter@gmail.com  Tue Feb 16 11:57:17 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 E47A228C137 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 11:57:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.724
X-Spam-Level: 
X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=-0.125, 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 QDp7qbhVAdoQ for <behave@core3.amsl.com>; Tue, 16 Feb 2010 11:57:17 -0800 (PST)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.216.182]) by core3.amsl.com (Postfix) with ESMTP id 24CB028C100 for <behave@ietf.org>; Tue, 16 Feb 2010 11:57:17 -0800 (PST)
Received: by pxi12 with SMTP id 12so4249737pxi.33 for <behave@ietf.org>; Tue, 16 Feb 2010 11:58:49 -0800 (PST)
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=hwx8I0nBKsnxANAypxtVDvKlVI3hPg24Tvp8uZmygdE=; b=MMqmxVZr7bN7lW5BuBOkl79QyYk4q+maa5udqeYkREsMEG3YWXSMHtg3tkbqd7+4ua xlXAezslgsWsxTk4k58BLP/ch1SDOZvO7viiJRMP69rwug2Muz62q3A4hdym58fUSqPw B2komE7XsIiTWYzhy+m4khlHQQVhe6E83WD7c=
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=QcyWA/akygVDMtFoawZp0/K06KlikllXWFn/Ipwj0RWQd/WKEeaP+zrN17qm9E8zF2 CEO/sShxuK+Z82xLhbkIF7J1hLm1k7SMd+lTg2NdQLGDYvBk5gQklSM0A+aJcdvHwluF BDYjg9MxnLYtYESb7QClde1L0IfPYmdq6R2vg=
Received: by 10.142.56.16 with SMTP id e16mr4693256wfa.109.1266350329928; Tue, 16 Feb 2010 11:58:49 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 22sm7304119pzk.5.2010.02.16.11.58.48 (version=SSLv3 cipher=RC4-MD5); Tue, 16 Feb 2010 11:58:49 -0800 (PST)
Message-ID: <4B7AF8F6.2050103@gmail.com>
Date: Wed, 17 Feb 2010 08:58:46 +1300
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: Andrew Sullivan <ajs@shinkuro.com>
References: <20100212195141.GR14996@shinkuro.com>	<201002130013.o1D0DGEN046772@drugs.dv.isc.org>	<20100215150544.GG25973@shinkuro.com>	<201002152242.o1FMgZnl097630@drugs.dv.isc.org>	<20100216140039.GF36083@shinkuro.com>	<201002161452.o1GEqju0086328@drugs.dv.isc.org> <20100216191315.GL36083@shinkuro.com>
In-Reply-To: <20100216191315.GL36083@shinkuro.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 16 Feb 2010 19:57:18 -0000

On 2010-02-17 08:13, Andrew Sullivan wrote:
> On Wed, Feb 17, 2010 at 01:52:45AM +1100, Mark Andrews wrote:
>> Dual stack will ask for both.  getaddrinfo() will sort non-mapped
>> AAAA records to the start of the list, using default sorting rules,
>> but will return both to the application.  Single stack will ask for
>> the appropriate record for the stack.
> 
> Ah, I see where we're missing each other.  I think the idea that we're
> going to have many applications properly sensitive to this is
> optimistic at best.

It's certainly optimistic today. Hopefully the apps community will
slowly get better at this as they confront dual-stack or IPv6-only
in the wild, but for many years we will see a variety of app
behaviours even on a single host. An interesting case would be an app
that only knows about gethostbyname() running on a dual stack host
whose DNS server is a DNS64. We can't say that's not our problem.

    Brian

> 
>> It will work without being touched.   It will work *better* if it
>> is touched or upgraded to support automated methods of passing
>> configuration around.
> 
> Ok.  Note that that does not seem to be the goal of the I-D we started
> talking about, however.  It's pretty hard to tell to tell from the
> sketchy draft as it stands, but it seems to be aiming at supporting
> unmodified dual-stack hosts behind a NAT64+DNS64, and doing that
> without having them use the NAT when they could use native v4 transit.
> At least, that's the only sense I can make of it.  Otherwise, there's
> no need for a draft: dual-stack hosts behind a NAT64 will just use the
> NAT, and who cares; applications that do care can behave how they need
> to do.
> 
> If you were going to modify the end points to deal with this
> condition, why not teach them about v4 _and_ v6, teach them to do
> their own resolution, and teach them to prefer native v6 when
> available and native v4 when available, preferring native v6 over all
> things.  This is not hard to teach an end host; but we've been
> operating on the assumption that the end hosts are too numerous and
> cumbersome to upgrade. 
> 
> A
> 

From marka@isc.org  Tue Feb 16 14:48:09 2010
Return-Path: <marka@isc.org>
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 780D528C1E4 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 14:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  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 y5iOocY6mYL1 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 14:48:08 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 3116828C0F8 for <behave@ietf.org>; Tue, 16 Feb 2010 14:48:08 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 4630AE60A9; Tue, 16 Feb 2010 22:49:42 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1GMncpF003528; Wed, 17 Feb 2010 09:49:39 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002162249.o1GMncpF003528@drugs.dv.isc.org>
To: Andrew Sullivan <ajs@shinkuro.com>
From: Mark Andrews <marka@isc.org>
References: <20100212195141.GR14996@shinkuro.com> <201002130013.o1D0DGEN046772@drugs.dv.isc.org> <20100215150544.GG25973@shinkuro.com> <201002152242.o1FMgZnl097630@drugs.dv.isc.org> <20100216140039.GF36083@shinkuro.com> <201002161452.o1GEqju0086328@drugs.dv.isc.org> <20100216191315.GL36083@shinkuro.com> 
In-reply-to: Your message of "Tue, 16 Feb 2010 14:13:15 CDT." <20100216191315.GL36083@shinkuro.com> 
Date: Wed, 17 Feb 2010 09:49:38 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 16 Feb 2010 22:48:09 -0000

In message <20100216191315.GL36083@shinkuro.com>, Andrew Sullivan writes:
> On Wed, Feb 17, 2010 at 01:52:45AM +1100, Mark Andrews wrote:
> > Dual stack will ask for both.  getaddrinfo() will sort non-mapped
> > AAAA records to the start of the list, using default sorting rules,
> > but will return both to the application.  Single stack will ask for
> > the appropriate record for the stack.
> 
> Ah, I see where we're missing each other.  I think the idea that we're
> going to have many applications properly sensitive to this is
> optimistic at best.

The point of NAT64+DNS64 was to allow IPv6 aware applications reach
IPv4 only services on the presumption that this will work for most
applications.  This was driven by the assumption that there will
be IPv6 only networks in the future and that the servers on the
Internet won't be upgraded to support IPv6 soon enough for these
networks.  All the clients need NAT64+DNS64 (or some other bridging
solution while the world catches up) in this senario.

The someone said what happens if a DNS64 is deployed where it is
not strictly needed.  The answer to that is non optimal traffic
flows and some applications breaking that wouldn't if DNS64 is not
deployed.

It was then asked if this can fixed and the answer is yes but it
requires some configuration to be performed and it would be better
if this could be automated.

> > It will work without being touched.   It will work *better* if it
> > is touched or upgraded to support automated methods of passing
> > configuration around.
> 
> Ok.  Note that that does not seem to be the goal of the I-D we started
> talking about, however.  It's pretty hard to tell to tell from the
> sketchy draft as it stands, but it seems to be aiming at supporting
> unmodified dual-stack hosts behind a NAT64+DNS64, and doing that
> without having them use the NAT when they could use native v4 transit.
> At least, that's the only sense I can make of it.  Otherwise, there's
> no need for a draft: dual-stack hosts behind a NAT64 will just use the
> NAT, and who cares; applications that do care can behave how they need
> to do.

draft-cao-behave-dsdns64-00 addresses a perceived issue which as
far as I can tell does not exist.  Dual stack client will ask for
A records and there is nothing in DNS64 to say don't answer these
queries.

That being said there will be operators that will want nameservers
to block A responses.  We have operators that want nameservers to
block AAAA responses unless the queries are made over IPv6 today.
This is mainly due to applications that are not multi-home aware
despite it been a RFC1123 host requirement for 20+ years.  A
multi-home aware application will try all addresses so it works
when one path is broken.

> If you were going to modify the end points to deal with this
> condition, why not teach them about v4 _and_ v6, teach them to do
> their own resolution, and teach them to prefer native v6 when
> available and native v4 when available, preferring native v6 over all
> things.  This is not hard to teach an end host; but we've been
> operating on the assumption that the end hosts are too numerous and
> cumbersome to upgrade. 
>
> A
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From xing@cernet.edu.cn  Tue Feb 16 15:38:07 2010
Return-Path: <xing@cernet.edu.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 196903A7E12 for <behave@core3.amsl.com>; Tue, 16 Feb 2010 15:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.312
X-Spam-Level: 
X-Spam-Status: No, score=0.312 tagged_above=-999 required=5 tests=[AWL=0.215,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 ygwnF1wsXG1a for <behave@core3.amsl.com>; Tue, 16 Feb 2010 15:38:06 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id C8D7028C0F3 for <behave@ietf.org>; Tue, 16 Feb 2010 15:38:05 -0800 (PST)
Received: from [192.168.1.100]([119.41.128.67]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b7b6c75; Wed, 17 Feb 2010 07:39:40 +0800
Message-ID: <4B7B2CBB.1000304@cernet.edu.cn>
Date: Wed, 17 Feb 2010 07:39:39 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <139a01caac18$2a031c80$c4f0200a@cisco.com> <9B57C850BB53634CACEC56EF4853FF650CE3C0AF@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <4B7A877B.1030406@cernet.edu.cn> <9B57C850BB53634CACEC56EF4853FF650CE3C994@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF650CE3C994@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: H3CB7hXB
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Tue, 16 Feb 2010 23:38:07 -0000

Hi, Dave,

Dave Thaler 写道:
> Maybe something like:
>    In this case, the translator can do stateful translation.
>    A mechanism by which the translator can instead do 
>    stateless translation is left for future work.
>
>   

Agree. We will use this sentence in version 10. Thanks!

Regards,

xing



From rpenno@juniper.net  Tue Feb 16 18:51:03 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 249E228C14B for <behave@core3.amsl.com>; Tue, 16 Feb 2010 18:51:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.958
X-Spam-Level: 
X-Spam-Status: No, score=-5.958 tagged_above=-999 required=5 tests=[AWL=0.641,  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 U1-V1f-GD9xc for <behave@core3.amsl.com>; Tue, 16 Feb 2010 18:51:02 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 42A3D28C141 for <behave@ietf.org>; Tue, 16 Feb 2010 18:51:01 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKS3tZ8u+C9dP+HvnjZ8SSahnEFGNxeyI3@postini.com; Tue, 16 Feb 2010 18:52:39 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.1.393.1; Tue, 16 Feb 2010 18:50:26 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 16 Feb 2010 21:50:26 -0500
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, "behave@ietf.org" <behave@ietf.org>
Date: Tue, 16 Feb 2010 21:50:21 -0500
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-09
Thread-Index: AcqsGCm956AMvKnwQVi8+qsuuj5YFQDY8hMc
Message-ID: <C7A0996D.136CD%rpenno@juniper.net>
In-Reply-To: <139a01caac18$2a031c80$c4f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.3.0.091002
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-behave-v6v4-xlate@tools.ietf.org" <draft-ietf-behave-v6v4-xlate@tools.ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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, 17 Feb 2010 02:51:03 -0000

I have a few comments as I review this draft again...others follow later

I'm assuming the purpose of this document is to update (and improve) on
RFC2765 in two dimensions: applicability and translation algorithm itself.

The latter is very clear but the first is not. For example:

* The third paragraph is basically a copy of what is already written in
RFC2765. In the end I thought I was expecting to see a sentence like ...'an=
d
in section Z we discuss how this document solves these issues...'. But it
seems the issues discussed in RFC2765 (and here) are very much still
present. Or does this spec advances anything specific to solve the long-ter=
m
scenario of when all Internet is v6 and you need a translator box 'far
away'?=20

In section 1.2 "Applicability and Limitations" there is also no discussion
on SIIT 'distant boxes' or whether this is a limitation or not.

But in general I think section 1 is confusing. Maybe due to the many
interactions of the draft. The paragraphs seem disconnected and not really
seems to advance the 'introduction and motivation' in a cohesive fashion.

* The third paragraph under section 1 seems out of place and not actually
adding to the discussion. I think this can be removed without any loss to
the document. Actually I would suggest it makes the introduction clearer.

The motivation IMO seems clear: we need to interoperate v6 and v4. Whether
'distant boxes' are  issue or not seems at best something you could discuss
in some applicability section.

In summary I would suggest similarly to what we did for SFNAT64 an analysis
on how this document improves or not RFC2765 in the applicability section.

Thanks,

Reinaldo


On 2/12/10 11:18 AM, "Dan Wing" <dwing@cisco.com> wrote:

> ** We need at least 5 reviewers to tell us this document is ready
> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
> ** with a subject line containing the document name, and "ready
> ** to submit to IESG" or "not ready to submit to IESG" in the
> ** message body.  If not ready to submit, please propose new text.
>=20
>=20
> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-09, endin=
g in
> one week (Friday, February 19).  For reference, the first WGLC was for
> draft-ietf-behave-v6v4-xlate-05.
>=20
> draft-ietf-behave-v6v4-xlate-09 contains all feedback from the working gr=
oup
> to date, including the feedback based on Ben Stasiewicz's analysis of ICM=
Pv6
> behavior on the Internet and the resulting discussion on the mailing list=
,
> which resulted in a new sentence and a new paragraph between -07 and -09.
> Differences between 07 and 09 are:
>=20
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-behave-v6v4-xlate-07.txt&=
url2=3Ddr
> aft-ietf-behave-v6v4-xlate-09.txt
>=20
>=20
> Differences between 05 (first WGLC) and 09 (2nd WGLC) are:
>=20
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-behave-v6v4-xlate-05.txt&=
url2=3Ddr
> aft-ietf-behave-v6v4-xlate-09.txt
>=20
> -d
>=20
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From denghui02@gmail.com  Wed Feb 17 00:08:33 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 897BD28C1C7 for <behave@core3.amsl.com>; Wed, 17 Feb 2010 00:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.221
X-Spam-Level: 
X-Spam-Status: No, score=-2.221 tagged_above=-999 required=5 tests=[AWL=0.378,  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 BkMtT+44i3fO for <behave@core3.amsl.com>; Wed, 17 Feb 2010 00:08:32 -0800 (PST)
Received: from mail-pz0-f190.google.com (mail-pz0-f190.google.com [209.85.222.190]) by core3.amsl.com (Postfix) with ESMTP id 537C628C11B for <behave@ietf.org>; Wed, 17 Feb 2010 00:08:32 -0800 (PST)
Received: by pzk28 with SMTP id 28so8701296pzk.31 for <behave@ietf.org>; Wed, 17 Feb 2010 00:10:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6mciqDKbHNBgfzxQ0eyNeG0h3HwCKLwc0iHqrM4NIFY=; b=eC6it8D5mY2WwuO6wKy9KW6zIR/biyZEbYYTiTjWqpug5tw6kiZOryuhvBI/5B4hmi eiHT6tzM9c/FGYUHinQHb53UFSJNINnNV6eC3Da/nnVHiV7Y0GwmtQEZfTLk8d/0t1Bm /CiAKqmTogIzQNu6Q4AQRsH0KOGgdG+eaNUUk=
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 :cc:content-type:content-transfer-encoding; b=PQ7HwMBGkZrCiw/U6Crq0S2TEAAPQjoDbzQN7mP7v//UkfJaD5kRSEQeWbkU7CmUZU HdyGJrM2d26M+ttFgk2ND806UlPzSraxBhRnI1mDRhpIjE89zGDhjb9lTUMHxMo1htP5 a8edEP7EGEQ5USmip4dgUyEPk/F5LK4s6LBvE=
MIME-Version: 1.0
Received: by 10.141.89.10 with SMTP id r10mr2114650rvl.69.1266394196159; Wed,  17 Feb 2010 00:09:56 -0800 (PST)
In-Reply-To: <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com>
Date: Wed, 17 Feb 2010 16:09:56 +0800
Message-ID: <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 17 Feb 2010 08:08:33 -0000

if we could prefer NAT64 than NAT44, it really benefit for IPv6,
IETF should prefer IPv6 friend solution other than IPv4 friend solution

I also don't think that assigning unlimited IPv4 address to UE and
encouraging them continue to use NAT44 is not a good way to go, when
will IPv6 come?

if we prefer 6 to 4, than I believe NAT64 could also be used for dual
stack connection.

thanks

-Hui

2010/2/13 Cameron Byrne <cb.list6@gmail.com>:
> On Fri, Feb 12, 2010 at 12:27 PM, Dan Wing <dwing@cisco.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: behave-bounces@ietf.org
>>> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
>>> Sent: Friday, February 12, 2010 11:52 AM
>>> To: behave@ietf.org
>>> Subject: [BEHAVE] draft-cao-behave-dsdns64-00
>>>
>>> Dear colleagues,
>>>
>>> I just read draft-cao-behave-dsdns64-00. =A0I confess that I am
>>> completely mystified by it.
>
> I don't agree with the premise of the draft -- that traffic going via
> a NAT64 is entirely bad. =A0In some environments maybe it is bad, but in
> my environment 99% of the mobile phone / device traffic goes via NAT44
> today. =A0NAT64 and NAT44 are very similar in function and cost to the
> service provider. =A0If the flow goes via NAT44 or NAT64 it does not
> matter to me, either way the user can access the content they want and
> the service provider has to support / scale =A0"state" in the network
> for that session(s). =A0If the user receives a natural AAAA record, i
> have less NAT state since a natural (non-DNS64 synthesized) record
> will bypass the NAT64 completely, thus saving me money since i don't
> have to grow the NAT capacity for any native IPv6 content (keep in
> mind Google and Youtube are the largest content sources in the USA ..
> and they service native IPv6)
>
> So, using today's model, if all my users were IPv6-only with NAT64
> instead of IPv4 with NAT44, i would have much less cost in the network
> since native AAAA flows would not go via the NAT.
>
>
>>>
>>> The central point of the draft appears to be that the DNS64 should
>>> handle A queries normally.
>>>
>>> There is no explanation of how that would even possibly work. =A0The
>>> DNS64 works by synthesizing AAAA out of A records. =A0It _can't_ return
>>> an A record because it will return the AAAA first.
>>>
>>> If that assumption is violated, actually, the entire DNS64 project is
>>> doomed as near as I can tell.
>>>
>>> Have I missed something?
>>
>> It should work if the policy table IPv6/IPv4 preference is inverted
>> from the default. =A0That is, the host's RFC3484 policy table could be
>> changed to prefer IPv4.
>>
>
> And this is exactly what we DO NOT want to happen. =A0Since it means
> that only IPv6-only systems will go to IPv6 content, thus perpetuating
> the "chicken and egg" problem to new unforeseen levels of stale-mate.
>
>> That would have significant implications, though: =A0if a server
>> is dual-stacked, the dual-stack client will always use IPv4. =A0That
>> IPv4 traffic is likely to be NATted (due to impending IPv4
>> exhaustion and the need for the ISP to conserve IPv4 addresses),
>> which will harm the user's experience if they need more TCP
>> ports than available on the NAT. =A0Some applications need a lot
>> of TCP ports, as we know -- the canonical example is Google Maps
>> but there are other applications that also use a lot of TCP
>
> This is a very important point and a powerful trend with AJAX
> webpages, here is the citation for NTT's work on this topic of MANY
> MANY session consuming a great deal of NAT resources.
>
> http://www.nttv6.jp/~miyakawa/IETF72/IETF-IAB-TECH-PLENARY-NTT-miyakawa.p=
df
>
>> ports. =A0To avoid the poor user experience of running out of
>> TCP ports on the NAT, the content provider has an incentive to
>> enable IPv6. =A0However, if the dual-stack client continues to
>> prefer IPv4, the IPv6 path isn't used, and the user experience
>> continues to be poor. =A0With such an address preference, the
>> user experience only improves when the A record is no longer
>> in the DNS. =A0That also means thousands, or millions, of
>
> Right, this leads to the proverbial flag-day that the IETF said would
> never exists, because it will also invariably partition portions of
> the Internet on the flag day
>
>> clients would suddenly switch from using IPv4 to using IPv6
>> which would be a difficult adjustment for the content provider.
>>
>> -d
>>
>>
>>> Best regards,
>>>
>>> A
>>>
>>> --
>>> Andrew Sullivan
>>> ajs@shinkuro.com
>>> Shinkuro, Inc.
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From dwing@cisco.com  Wed Feb 17 09:16:40 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 350B43A7D4F for <behave@core3.amsl.com>; Wed, 17 Feb 2010 09:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 RwvYgFUjeTlp for <behave@core3.amsl.com>; Wed, 17 Feb 2010 09:16:39 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 47DC23A71BD for <behave@ietf.org>; Wed, 17 Feb 2010 09:16:39 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgIANKze0urR7Ht/2dsb2JhbACHTYESkiN0phaYBoRdBIMV
X-IronPort-AV: E=Sophos;i="4.49,492,1262563200"; d="scan'208";a="484439924"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 17 Feb 2010 17:18:18 +0000
Received: from dwingwxp01 ([10.32.240.197]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o1HHIIeo017838; Wed, 17 Feb 2010 17:18:18 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <20100212195141.GR14996@shinkuro.com>	<201002130013.o1D0DGEN046772@drugs.dv.isc.org>	<20100215150544.GG25973@shinkuro.com>	<201002152242.o1FMgZnl097630@drugs.dv.isc.org>	<20100216140039.GF36083@shinkuro.com>	<201002161452.o1GEqju0086328@drugs.dv.isc.org><20100216191315.GL36083@shinkuro.com> <4B7AF8F6.2050103@gmail.com>
Date: Wed, 17 Feb 2010 09:18:20 -0800
Message-ID: <040d01caaff5$33cbe810$cf4a150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4B7AF8F6.2050103@gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcqvQn1lskN84TlDRFatn3RKI2NsfQAsoQPQ
Cc: 'Andrew Sullivan' <ajs@shinkuro.com>, behave@ietf.org
Subject: [BEHAVE] gethostbyname() on dual stack host with DNS64 server [was RE: draft-cao-behave-dsdns64-00]
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, 17 Feb 2010 17:16:40 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Tuesday, February 16, 2010 11:59 AM
> To: Andrew Sullivan
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
> 
> On 2010-02-17 08:13, Andrew Sullivan wrote:
> > On Wed, Feb 17, 2010 at 01:52:45AM +1100, Mark Andrews wrote:
> >> Dual stack will ask for both.  getaddrinfo() will sort non-mapped
> >> AAAA records to the start of the list, using default sorting rules,
> >> but will return both to the application.  Single stack will ask for
> >> the appropriate record for the stack.
> > 
> > Ah, I see where we're missing each other.  I think the idea 
> that we're
> > going to have many applications properly sensitive to this is
> > optimistic at best.
> 
> It's certainly optimistic today. Hopefully the apps community will
> slowly get better at this as they confront dual-stack or IPv6-only
> in the wild, but for many years we will see a variety of app
> behaviours even on a single host. An interesting case would be an app
> that only knows about gethostbyname() running on a dual stack host
> whose DNS server is a DNS64. We can't say that's not our problem.

What is your feeling of 
http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.1
to resolve that situation.  Or the other 5 mechanisms described in
that draft.

-d


>     Brian
> 
> > 
> >> It will work without being touched.   It will work *better* if it
> >> is touched or upgraded to support automated methods of passing
> >> configuration around.
> > 
> > Ok.  Note that that does not seem to be the goal of the I-D 
> we started
> > talking about, however.  It's pretty hard to tell to tell from the
> > sketchy draft as it stands, but it seems to be aiming at supporting
> > unmodified dual-stack hosts behind a NAT64+DNS64, and doing that
> > without having them use the NAT when they could use native 
> v4 transit.
> > At least, that's the only sense I can make of it.  
> Otherwise, there's
> > no need for a draft: dual-stack hosts behind a NAT64 will 
> just use the
> > NAT, and who cares; applications that do care can behave 
> how they need
> > to do.
> > 
> > If you were going to modify the end points to deal with this
> > condition, why not teach them about v4 _and_ v6, teach them to do
> > their own resolution, and teach them to prefer native v6 when
> > available and native v4 when available, preferring native 
> v6 over all
> > things.  This is not hard to teach an end host; but we've been
> > operating on the assumption that the end hosts are too numerous and
> > cumbersome to upgrade. 
> > 
> > A
> > 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From dwing@cisco.com  Wed Feb 17 09:43:05 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 343273A7D1B for <behave@core3.amsl.com>; Wed, 17 Feb 2010 09:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.499
X-Spam-Level: 
X-Spam-Status: No, score=-10.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 GCGQarqzTGa1 for <behave@core3.amsl.com>; Wed, 17 Feb 2010 09:43:04 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 549083A7D4F for <behave@ietf.org>; Wed, 17 Feb 2010 09:43:04 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgIAHO5e0urR7H+/2dsb2JhbACHTYESkiN0ph+YAYRdBIMV
X-IronPort-AV: E=Sophos;i="4.49,492,1262563200"; d="scan'208";a="212912607"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 17 Feb 2010 17:44:43 +0000
Received: from dwingwxp01 ([10.32.240.197]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o1HHig8i004813; Wed, 17 Feb 2010 17:44:43 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Andrew Sullivan'" <ajs@shinkuro.com>, <behave@ietf.org>
References: <13cd01caac1e$0cd62e80$c4f0200a@cisco.com> <20100212223947.GY14996@shinkuro.com>
Date: Wed, 17 Feb 2010 09:44:45 -0800
Message-ID: <043501caaff8$e47b8190$cf4a150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20100212223947.GY14996@shinkuro.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcqsNGsvbn6yROV/RlesrqLWCOU7PgDxHN3w
Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 resolversfor	dual-stack/IPv6-only hosts
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, 17 Feb 2010 17:43:05 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
> Sent: Friday, February 12, 2010 2:40 PM
> To: behave@ietf.org
> Subject: Re: [BEHAVE] using IPv4-mapped DNS/DNS64 
> resolversfor dual-stack/IPv6-only hosts
> 
> On Fri, Feb 12, 2010 at 12:00:39PM -0800, Dan Wing wrote:
> > While writing them down, I came up with another approach 
> which uses an
> > IPv4-mapped address in the list of IPv6 DNS servers.  An 
> IPv6-only host cannot
> > use that address, so it would use the next DNS server on the list; a
> > dual-stack host can use such a DNS server.  Details are in:
> > 
> > 
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#s
> ection-3.1
> > 
> > Please comment on this approach.  For whatever it's worth, 
> the idea seems to
> > work.
> 
> This is _before_ any DNS64 is happening, right? 

Correct.

-d

> That is, it's a way
> to convince the dual-homed host to use the "plain" DNS for v4 queries
> and the DNS64 for v6 queries, without a lot of complicated
> co-ordination?  If I've read it right, it seems like a good idea to
> me.
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From dwing@cisco.com  Wed Feb 17 10:26:24 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 C170928C0DF for <behave@core3.amsl.com>; Wed, 17 Feb 2010 10:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 bq23S8rq+NTa for <behave@core3.amsl.com>; Wed, 17 Feb 2010 10:26:24 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 0F8BA28C186 for <behave@ietf.org>; Wed, 17 Feb 2010 10:26:24 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgIAHfEe0urR7H+/2dsb2JhbACHTYESkiN0piuXf4RdBIMV
X-IronPort-AV: E=Sophos;i="4.49,492,1262563200"; d="scan'208";a="240684030"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 17 Feb 2010 18:27:59 +0000
Received: from dwingwxp01 ([10.32.240.197]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o1HIRxax020205; Wed, 17 Feb 2010 18:27:59 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Wed, 17 Feb 2010 10:28:01 -0800
Message-ID: <047501caaffe$f01f5660$cf4a150a@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: Acqv/u/cXiNWhOEBT4eja+K338Bj8Q==
Cc: draft-ietf-behave-dns64@tools.ietf.org
Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
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, 17 Feb 2010 18:26:24 -0000

** We need at least 5 reviewers to tell us this document is ready 
** for submission to IESG.  Please email behave-chairs@tools.ietf.org 
** with a subject line containing the document name, and "ready 
** to submit to IESG" or "not ready to submit to IESG" in the 
** message body.  If not ready to submit, please propose new text.

This email starts the 2nd WGLC for draft-ietf-behave-dns64-06, ending
in one week (Wednesday, February 24).  For reference, the first 
WGLC was for draft-ietf-behave-v6v4-framework-05.  

Differences from -05 (first WGLC) and -06 (2nd WGLC),
http://tools.ietf.org/rfcdiff?url2=draft-ietf-behave-dns64-06.txt

-d


From Fred.L.Templin@boeing.com  Wed Feb 17 17:04:38 2010
Return-Path: <Fred.L.Templin@boeing.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 14ED528C298 for <behave@core3.amsl.com>; Wed, 17 Feb 2010 17:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.564
X-Spam-Level: 
X-Spam-Status: No, score=-6.564 tagged_above=-999 required=5 tests=[AWL=0.035,  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 dJeFmHKlMGYe for <behave@core3.amsl.com>; Wed, 17 Feb 2010 17:04:37 -0800 (PST)
Received: from xxx-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 2915B28C257 for <behave@ietf.org>; Wed, 17 Feb 2010 17:04:36 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o1I164BP029139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 17 Feb 2010 19:06:05 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o1I1632P028115; Wed, 17 Feb 2010 17:06:03 -0800 (PST)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o1I1621B028081 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 17 Feb 2010 17:06:02 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Wed, 17 Feb 2010 17:06:01 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, "behave@ietf.org WG" <behave@ietf.org>
Date: Wed, 17 Feb 2010 17:05:55 -0800
Thread-Topic: [BEHAVE] General PMTUD black hole detection in translators
Thread-Index: AcqqIXnXzvlNaQa8THK2YAINRYbRmQGE5HIw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A649510C835A@XCH-NW-01V.nw.nos.boeing.com>
References: <FB6800D2-6304-42E8-82C2-17D2D016EB81@muada.com>
In-Reply-To: <FB6800D2-6304-42E8-82C2-17D2D016EB81@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BEHAVE] General PMTUD black hole detection in translators
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, 18 Feb 2010 01:04:38 -0000

Iljitsch,

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of Iljitsch van Beijnum
> Sent: Tuesday, February 09, 2010 11:20 PM
> To: behave@ietf.org WG
> Subject: [BEHAVE] General PMTUD black hole detection in translators
>=20
> If we want to avoid cases where there is a link with a reduced MTU betwee=
n the IPv6 hosts and a
> translator that triggers path MTU discovery black holes towards certain I=
Pv4 servers, we could add a
> form of PMTUD black hole detection to translators.
>=20
> It would work like this: the translator of course translates too big mess=
ages from the IPv6 side to
> IPv4. If it remembers that it did this and then sees that the IPv4 host d=
oesn't lower its packet
> sizes within a reasonable timeframe, it can then when new sessions are se=
t up from the same IPv6 host
> towards the same IPv4 host, adjust the MSS to the value that was present =
in the earlier too big
> message.
>=20
> So then the first TCP session would time out but subsequent ones would ha=
ve their MSS clamped and
> those would work. This would only kick in when there is an actual black h=
ole so there is no impact
> for well behaved systems. The initial session would still fail so there w=
ould still be good reason
> for PMTUD breakers to fix their systems, but after the initial failure, t=
he user would have something
> that works.

This sounds like the translator would be required
to do a lot of work, keep a lot of state, and would
present a non-deterministic service to end users.
And, it also only works for TCP.

Better would be to somehow ensure that all links on
the IPv6 side support a large enough MTU so that
1520 (*) or larger packets are delivered from the
translator to the IPv6 host without loss due to an
MTU restriction. Here, I include IPv6-over-IPv4
tunnels as "links".

Fred
fred.l.templin@boeing.com

(*) For TCP communications initiated on the IPv6 side,
    an IPv6 host attached to a 1500 link would use a
    TCP MSS of 1440. So, an IPv4 host would only send
    1480 packets (1440 plus IPv4 header plus TCP header)
    which would be turned into 1500 packets on the IPv6
    side. But for non-TCP protocols, the IPv4 host would
    not see an MSS and could send 1500 packets that would
    be turned into 1520 packets on the IPv6 side.=20
=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From brian.e.carpenter@gmail.com  Wed Feb 17 17:18: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 9F0E63A7A73 for <behave@core3.amsl.com>; Wed, 17 Feb 2010 17:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[AWL=-0.112, 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 P9KJTnZ5C0bZ for <behave@core3.amsl.com>; Wed, 17 Feb 2010 17:18:52 -0800 (PST)
Received: from mail-pz0-f190.google.com (mail-pz0-f190.google.com [209.85.222.190]) by core3.amsl.com (Postfix) with ESMTP id 6EB343A7A62 for <behave@ietf.org>; Wed, 17 Feb 2010 17:18:52 -0800 (PST)
Received: by pzk28 with SMTP id 28so9859228pzk.31 for <behave@ietf.org>; Wed, 17 Feb 2010 17:20:29 -0800 (PST)
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=ImEd+kWQgOWhDll75kWehMj/Hs0YSBH/9IF4knBzqIA=; b=LTcEBGA3ty8aPBYdrH8xrSN88HaFkUAhE84SL7YOhSynQi9PRDuvxpBE1u7jljV4lP eozxzoN2Si2i/vJCaNHZPEcJtSBso5dTaiSpmMOzx/MlCQ+vLZYgnegnxJEDUaVAOGFB K0NfQaIGX/CaLYPmDVh7QDpalzo9LnlU6Zv6c=
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=frtz3Lz483pScZUI72IIPF/EMEaAPoanih0JxOwqY4v1YCH1qPuiP0e2Js/+DOPOcB S74S7FlzFI8EiG2juJpmQmywqmOAzrWm87/6suDCXGUK/h/0OYJjLB1iA4RpjsNeKPl9 ZnyjxXXBEujWO063tZroGjLOcxQIOh51IQH4k=
Received: by 10.114.2.19 with SMTP id 19mr5860978wab.211.1266456029576; Wed, 17 Feb 2010 17:20:29 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 23sm3756297pzk.4.2010.02.17.17.20.27 (version=SSLv3 cipher=RC4-MD5); Wed, 17 Feb 2010 17:20:28 -0800 (PST)
Message-ID: <4B7C95D8.5030403@gmail.com>
Date: Thu, 18 Feb 2010 14:20:24 +1300
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: <20100212195141.GR14996@shinkuro.com>	<201002130013.o1D0DGEN046772@drugs.dv.isc.org>	<20100215150544.GG25973@shinkuro.com>	<201002152242.o1FMgZnl097630@drugs.dv.isc.org>	<20100216140039.GF36083@shinkuro.com>	<201002161452.o1GEqju0086328@drugs.dv.isc.org><20100216191315.GL36083@shinkuro.com> <4B7AF8F6.2050103@gmail.com> <040d01caaff5$33cbe810$cf4a150a@cisco.com>
In-Reply-To: <040d01caaff5$33cbe810$cf4a150a@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'Andrew Sullivan' <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] gethostbyname() on dual stack host with DNS64 server [was RE: draft-cao-behave-dsdns64-00]
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, 18 Feb 2010 01:18:53 -0000

Hi Dan,

On 2010-02-18 06:18, Dan Wing wrote:
>  
> 
>> -----Original Message-----
>> From: behave-bounces@ietf.org 
>> [mailto:behave-bounces@ietf.org] On Behalf Of Brian E Carpenter
>> Sent: Tuesday, February 16, 2010 11:59 AM
>> To: Andrew Sullivan
>> Cc: behave@ietf.org
>> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>>
>> On 2010-02-17 08:13, Andrew Sullivan wrote:
>>> On Wed, Feb 17, 2010 at 01:52:45AM +1100, Mark Andrews wrote:
>>>> Dual stack will ask for both.  getaddrinfo() will sort non-mapped
>>>> AAAA records to the start of the list, using default sorting rules,
>>>> but will return both to the application.  Single stack will ask for
>>>> the appropriate record for the stack.
>>> Ah, I see where we're missing each other.  I think the idea 
>> that we're
>>> going to have many applications properly sensitive to this is
>>> optimistic at best.
>> It's certainly optimistic today. Hopefully the apps community will
>> slowly get better at this as they confront dual-stack or IPv6-only
>> in the wild, but for many years we will see a variety of app
>> behaviours even on a single host. An interesting case would be an app
>> that only knows about gethostbyname() running on a dual stack host
>> whose DNS server is a DNS64. We can't say that's not our problem.
> 
> What is your feeling of 
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.1
> to resolve that situation.  Or the other 5 mechanisms described in
> that draft.

My understanding is that operating systems vary quite a bit in
their treatment of IPv4-mapped addresses. So I fear/suspect that
it will be hard to get consistent behaviour with that particular
mechanism. But in general, I think we need to discuss the alternatives
in your draft and choose one or two as Least Bad Current Practices,
so to speak.

   Brian

>>     Brian
>>
>>>> It will work without being touched.   It will work *better* if it
>>>> is touched or upgraded to support automated methods of passing
>>>> configuration around.
>>> Ok.  Note that that does not seem to be the goal of the I-D 
>> we started
>>> talking about, however.  It's pretty hard to tell to tell from the
>>> sketchy draft as it stands, but it seems to be aiming at supporting
>>> unmodified dual-stack hosts behind a NAT64+DNS64, and doing that
>>> without having them use the NAT when they could use native 
>> v4 transit.
>>> At least, that's the only sense I can make of it.  
>> Otherwise, there's
>>> no need for a draft: dual-stack hosts behind a NAT64 will 
>> just use the
>>> NAT, and who cares; applications that do care can behave 
>> how they need
>>> to do.
>>>
>>> If you were going to modify the end points to deal with this
>>> condition, why not teach them about v4 _and_ v6, teach them to do
>>> their own resolution, and teach them to prefer native v6 when
>>> available and native v4 when available, preferring native 
>> v6 over all
>>> things.  This is not hard to teach an end host; but we've been
>>> operating on the assumption that the end hosts are too numerous and
>>> cumbersome to upgrade. 
>>>
>>> A
>>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
> 
> 

From xing@cernet.edu.cn  Thu Feb 18 03:55:48 2010
Return-Path: <xing@cernet.edu.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 71B913A7855 for <behave@core3.amsl.com>; Thu, 18 Feb 2010 03:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.288
X-Spam-Level: 
X-Spam-Status: No, score=0.288 tagged_above=-999 required=5 tests=[AWL=0.191,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 3qPAPAPDX13W for <behave@core3.amsl.com>; Thu, 18 Feb 2010 03:55:47 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 0C0E23A7CBF for <behave@ietf.org>; Thu, 18 Feb 2010 03:55:46 -0800 (PST)
Received: from [192.168.1.100]([112.67.12.94]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jmb4b7d3984; Thu, 18 Feb 2010 19:57:03 +0800
Message-ID: <4B7D2AF7.3070706@cernet.edu.cn>
Date: Thu, 18 Feb 2010 19:56:39 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Reinaldo Penno <rpenno@juniper.net>
References: <C7A0996D.136CD%rpenno@juniper.net>
In-Reply-To: <C7A0996D.136CD%rpenno@juniper.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: hTLAFiXB
Cc: "draft-ietf-behave-v6v4-xlate@tools.ietf.org" <draft-ietf-behave-v6v4-xlate@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Thu, 18 Feb 2010 11:55:48 -0000

Hi, Reinaldo,

Thanks for your review and comments.

You are right, the current structure of IPv4/IPv6 translation involves 
several drafts and the
scenarios/solution analysis should not be discussed in xlate, which
is for translation algorithm itself. We will delete the unnecessary part 
in section 1 and section 1.2
in the next upload (version 10) after 2nd WGLC.

Regards,

xing



Reinaldo Penno 写道:
> I have a few comments as I review this draft again...others follow later
>
> I'm assuming the purpose of this document is to update (and improve) on
> RFC2765 in two dimensions: applicability and translation algorithm itself.
>
> The latter is very clear but the first is not. For example:
>
> * The third paragraph is basically a copy of what is already written in
> RFC2765. In the end I thought I was expecting to see a sentence like ...'and
> in section Z we discuss how this document solves these issues...'. But it
> seems the issues discussed in RFC2765 (and here) are very much still
> present. Or does this spec advances anything specific to solve the long-term
> scenario of when all Internet is v6 and you need a translator box 'far
> away'? 
>
> In section 1.2 "Applicability and Limitations" there is also no discussion
> on SIIT 'distant boxes' or whether this is a limitation or not.
>
> But in general I think section 1 is confusing. Maybe due to the many
> interactions of the draft. The paragraphs seem disconnected and not really
> seems to advance the 'introduction and motivation' in a cohesive fashion.
>
> * The third paragraph under section 1 seems out of place and not actually
> adding to the discussion. I think this can be removed without any loss to
> the document. Actually I would suggest it makes the introduction clearer.
>
> The motivation IMO seems clear: we need to interoperate v6 and v4. Whether
> 'distant boxes' are  issue or not seems at best something you could discuss
> in some applicability section.
>
> In summary I would suggest similarly to what we did for SFNAT64 an analysis
> on how this document improves or not RFC2765 in the applicability section.
>
> Thanks,
>
> Reinaldo
>
>
> On 2/12/10 11:18 AM, "Dan Wing" <dwing@cisco.com> wrote:
>
>   
>> ** We need at least 5 reviewers to tell us this document is ready
>> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
>> ** with a subject line containing the document name, and "ready
>> ** to submit to IESG" or "not ready to submit to IESG" in the
>> ** message body.  If not ready to submit, please propose new text.
>>
>>
>> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-09, ending in
>> one week (Friday, February 19).  For reference, the first WGLC was for
>> draft-ietf-behave-v6v4-xlate-05.
>>
>> draft-ietf-behave-v6v4-xlate-09 contains all feedback from the working group
>> to date, including the feedback based on Ben Stasiewicz's analysis of ICMPv6
>> behavior on the Internet and the resulting discussion on the mailing list,
>> which resulted in a new sentence and a new paragraph between -07 and -09.
>> Differences between 07 and 09 are:
>>
>> http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-07.txt&url2=dr
>> aft-ietf-behave-v6v4-xlate-09.txt
>>
>>
>> Differences between 05 (first WGLC) and 09 (2nd WGLC) are:
>>
>> http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-05.txt&url2=dr
>> aft-ietf-behave-v6v4-xlate-09.txt
>>
>> -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 matthijs@nlnetlabs.nl  Thu Feb 18 05:07:17 2010
Return-Path: <matthijs@nlnetlabs.nl>
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 97E4E3A7CE3 for <behave@core3.amsl.com>; Thu, 18 Feb 2010 05:07:17 -0800 (PST)
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 imY5uZf7AVdc for <behave@core3.amsl.com>; Thu, 18 Feb 2010 05:07:16 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id 1B6BB3A7CD5 for <behave@ietf.org>; Thu, 18 Feb 2010 05:07:15 -0800 (PST)
Received: from [IPv6:2001:7b8:206:1:215:afff:fed2:e121] ([IPv6:2001:7b8:206:1:215:afff:fed2:e121]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.3/8.14.3) with ESMTP id o1ID8sF4032403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Feb 2010 14:08:56 +0100 (CET) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4B7D3C29.2000109@nlnetlabs.nl>
Date: Thu, 18 Feb 2010 14:10:01 +0100
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
Organization: NLnet Labs
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Andrew Sullivan <ajs@shinkuro.com>
References: <20100215164502.935AB28C10C@core3.amsl.com> <20100215164837.GQ25973@shinkuro.com>
In-Reply-To: <20100215164837.GQ25973@shinkuro.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Thu, 18 Feb 2010 14:08:56 +0100 (CET)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Thu, 18 Feb 2010 13:07:17 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

I have read this version of the draft and I support it.

I am not too happy about the special error (RCODE) handling in section
5.1.2, but the reasons to still query for A records and try synthesis I
can understand.

In the same spirit, I miss text about how a DNS64 recursor would behave
on a timed out event when requesting AAAA records. We have seen servers
that are not responsive for AAAA RRs, but are responsive for other
RRtypes (presumably because of a firewall). I would classify these type
of servers the same as those that respond to SERVFAIL or REFUSED upon a
AAAA query.

Proposed text:

A query that results in a temporary error because the request was timed
out (and therefor terminated) is treated as though the RCODE were 0 and
the answer section were empty.


Best regards,

Matthijs

Andrew Sullivan wrote:
> Dear colleagues,
> 
> On Mon, Feb 15, 2010 at 08:45:02AM -0800, Internet-Drafts@ietf.org wrote:
>> 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           : DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
>> 	Author(s)       : M. Bagnulo, et al.
>> 	Filename        : draft-ietf-behave-dns64-06.txt
>> 	Pages           : 30
>> 	Date            : 2010-02-15
> 
> This version of the draft includes our responses to the comments
> received during and since the previous WGLC.  Follow-up comments are
> appreciated.
> 
> Best regards,
> 
> Andrew
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJLfTwnAAoJEA8yVCPsQCW5v9YH/R4ALeXX1+OwjeJ943N/LJ+6
EWFTHw3Npg/6unTG5q35N6kgaPeblMUlAVpqj0ndC6PVM6t3QgdT4+Hg9RqCT7RG
I0NR+k3c+RlUQJSqQ9qGgZQgF1f/PpXZnAqP14yjmLH9s2FoRf51tXxj83Gu3Til
pjiH+OspNbdjE8TlKJHJ88DKGVl4Ryu8HIOOanUdqyYrs/9KOA7wm2s94Y5fc5/U
yPOox6sVXJZIEFVxmYTAEWoGw0P1n3yohDRinC1D3UniXWSfU9HbjvOlhElKxCur
tvCDmxXVJvIyP2gQMDVEjIU/C6qrzbIcmsFuMzLQbvv/IGI3/qQDS7Y8F1i4Rlc=
=Vgyf
-----END PGP SIGNATURE-----

From simon.perreault@viagenie.ca  Thu Feb 18 05:23:37 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 A105C3A7AE3 for <behave@core3.amsl.com>; Thu, 18 Feb 2010 05:23:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[AWL=0.271,  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 KY8jWq6NUfzu for <behave@core3.amsl.com>; Thu, 18 Feb 2010 05:23:36 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id A658E3A722C for <behave@ietf.org>; Thu, 18 Feb 2010 05:23:36 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 7689620E54 for <behave@ietf.org>; Thu, 18 Feb 2010 08:25:18 -0500 (EST)
Message-ID: <4B7D3FBD.50905@viagenie.ca>
Date: Thu, 18 Feb 2010 08:25:17 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <20100215164502.935AB28C10C@core3.amsl.com>	<20100215164837.GQ25973@shinkuro.com> <4B7D3C29.2000109@nlnetlabs.nl>
In-Reply-To: <4B7D3C29.2000109@nlnetlabs.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Thu, 18 Feb 2010 13:23:37 -0000

On 2010-02-18 08:10, Matthijs Mekking wrote:
> In the same spirit, I miss text about how a DNS64 recursor would behave
> on a timed out event when requesting AAAA records. We have seen servers
> that are not responsive for AAAA RRs, but are responsive for other
> RRtypes (presumably because of a firewall). I would classify these type
> of servers the same as those that respond to SERVFAIL or REFUSED upon a
> AAAA query.
>
> Proposed text:
>
> A query that results in a temporary error because the request was timed
> out (and therefor terminated) is treated as though the RCODE were 0 and
> the answer section were empty.

+1

We've seen this in the wild, and this is how it should be handled.

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  Thu Feb 18 08:22:11 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 6C63E3A7FAB for <behave@core3.amsl.com>; Thu, 18 Feb 2010 08:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[AWL=0.590,  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 uMQKl7SYdPSD for <behave@core3.amsl.com>; Thu, 18 Feb 2010 08:22:10 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 9E68B3A7EEB for <behave@ietf.org>; Thu, 18 Feb 2010 08:22:10 -0800 (PST)
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 1C3C21ECBC22 for <behave@ietf.org>; Thu, 18 Feb 2010 16:23:53 +0000 (UTC)
Date: Thu, 18 Feb 2010 11:23:51 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100218162351.GC40337@shinkuro.com>
References: <20100215164502.935AB28C10C@core3.amsl.com> <20100215164837.GQ25973@shinkuro.com> <4B7D3C29.2000109@nlnetlabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B7D3C29.2000109@nlnetlabs.nl>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Thu, 18 Feb 2010 16:22:11 -0000

Thanks for the review!

On Thu, Feb 18, 2010 at 02:10:01PM +0100, Matthijs Mekking wrote:
> Proposed text:
> 
> A query that results in a temporary error because the request was timed
> out (and therefor terminated) is treated as though the RCODE were 0 and
> the answer section were empty.

This makes sense to me.  I see someone else has weighed in supporting
it as well.  Any objection?

A


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

From marka@isc.org  Thu Feb 18 14:44:17 2010
Return-Path: <marka@isc.org>
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 29EF23A7DB8 for <behave@core3.amsl.com>; Thu, 18 Feb 2010 14:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level: 
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.072,  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 OgstUl4Gpw-E for <behave@core3.amsl.com>; Thu, 18 Feb 2010 14:44:16 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 34C953A7375 for <behave@ietf.org>; Thu, 18 Feb 2010 14:44:16 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 913F6E60B1; Thu, 18 Feb 2010 22:45:58 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1IMjsO1028957; Fri, 19 Feb 2010 09:45:55 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002182245.o1IMjsO1028957@drugs.dv.isc.org>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
From: Mark Andrews <marka@isc.org>
References: <20100215164502.935AB28C10C@core3.amsl.com> <20100215164837.GQ25973@shinkuro.com> <4B7D3C29.2000109@nlnetlabs.nl> 
In-reply-to: Your message of "Thu, 18 Feb 2010 14:10:01 BST." <4B7D3C29.2000109@nlnetlabs.nl> 
Date: Fri, 19 Feb 2010 09:45:54 +1100
Sender: marka@isc.org
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Thu, 18 Feb 2010 22:44:17 -0000

In message <4B7D3C29.2000109@nlnetlabs.nl>, Matthijs Mekking writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi
> 
> I have read this version of the draft and I support it.
> 
> I am not too happy about the special error (RCODE) handling in section
> 5.1.2, but the reasons to still query for A records and try synthesis I
> can understand.
> 
> In the same spirit, I miss text about how a DNS64 recursor would behave
> on a timed out event when requesting AAAA records. We have seen servers
> that are not responsive for AAAA RRs, but are responsive for other
> RRtypes (presumably because of a firewall). I would classify these type
> of servers the same as those that respond to SERVFAIL or REFUSED upon a
> AAAA query.
> 
> Proposed text:
> 
> A query that results in a temporary error because the request was timed
> out (and therefor terminated) is treated as though the RCODE were 0 and
> the answer section were empty.

This senario is pretty rare these days.  Just SERVFAIL the client
on timeout.  It's time to get rid of the last of these broken load
balancers and if that means some pain for the clients so be it.
It's also the correct long term strategy.  Working around broken
boxes does not get the problems fixed.

This is really not different to not making a A query when the load
balancer incorrectly returns NXDOMAIN on AAAA.
 
Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From matthijs@nlnetlabs.nl  Fri Feb 19 00:27:29 2010
Return-Path: <matthijs@nlnetlabs.nl>
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 916A628C166 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 00:27:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 S7LNydQQpi+M for <behave@core3.amsl.com>; Fri, 19 Feb 2010 00:27:06 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id BCB1E28C0DE for <behave@ietf.org>; Fri, 19 Feb 2010 00:27:05 -0800 (PST)
Received: from [192.168.1.9] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.3/8.14.3) with ESMTP id o1J8SjQc019348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Feb 2010 09:28:47 +0100 (CET) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4B7E4C01.1040206@nlnetlabs.nl>
Date: Fri, 19 Feb 2010 09:29:53 +0100
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
Organization: NLnet Labs
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
References: <20100215164502.935AB28C10C@core3.amsl.com>	<20100215164837.GQ25973@shinkuro.com>	<4B7D3C29.2000109@nlnetlabs.nl> <201002182245.o1IMjsO1028957@drugs.dv.isc.org>
In-Reply-To: <201002182245.o1IMjsO1028957@drugs.dv.isc.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (open.nlnetlabs.nl [213.154.224.1]); Fri, 19 Feb 2010 09:28:48 +0100 (CET)
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Fri, 19 Feb 2010 08:27:29 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Or you handle a time out event as a SERVFAIL (and thus for DNS64 you may
query for A records).

Or you mention that this set up is broken, just like returning NXDOMAIN
is on AAAA query (but there are other records on that name).

Either way, additional text to clarify would be useful imo.
Than my preference is the first option, since you already got into
special error handling.

Also its not that hard to query for A records after a timed out event,
especially if the resolver already treats it as SERVFAIL. So its little
work to reduce the pain for clients.


Best regards,

Matthijs

Mark Andrews wrote:
> In message <4B7D3C29.2000109@nlnetlabs.nl>, Matthijs Mekking writes:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi
>>
>> I have read this version of the draft and I support it.
>>
>> I am not too happy about the special error (RCODE) handling in section
>> 5.1.2, but the reasons to still query for A records and try synthesis I
>> can understand.
>>
>> In the same spirit, I miss text about how a DNS64 recursor would behave
>> on a timed out event when requesting AAAA records. We have seen servers
>> that are not responsive for AAAA RRs, but are responsive for other
>> RRtypes (presumably because of a firewall). I would classify these type
>> of servers the same as those that respond to SERVFAIL or REFUSED upon a
>> AAAA query.
>>
>> Proposed text:
>>
>> A query that results in a temporary error because the request was timed
>> out (and therefor terminated) is treated as though the RCODE were 0 and
>> the answer section were empty.
> 
> This senario is pretty rare these days.  Just SERVFAIL the client
> on timeout.  It's time to get rid of the last of these broken load
> balancers and if that means some pain for the clients so be it.
> It's also the correct long term strategy.  Working around broken
> boxes does not get the problems fixed.
> 
> This is really not different to not making a A query when the load
> balancer incorrectly returns NXDOMAIN on AAAA.
>  
> Mark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJLfkv9AAoJEA8yVCPsQCW5sCUH/1ZcBxR8KYCaz0a8EJItWiWW
BWhes+tERdzyaj+k/yA2I53o5b17IGkASezdABPhANaSGUQA6acvLF9y0r4oZTZZ
J9hCVY8V/RluQaFbXic5OqDwvpqm4XJwQfOBrpt6WsxhNW/ZQDPw1qkzcDK2g0Rc
ENsOtinem/Ktua8teWtdFukJqQHN7eaedm1kAANphhMk7+lHAR/0Hj02MtqA3wWa
afY/Z6kcLldPsl3Gj9oheQM+mxnEPKY0IBON5K+uQ47ZHEgagRR2TZAmozMyLlyR
7wrXoy/mywF2fHLPmtKrPfhUEQDqRMJpFjL3cVKIJV9wa3bdrR9Pgz91mMY1Txg=
=ecgW
-----END PGP SIGNATURE-----

From ebisawa@sablenetworks.net  Fri Feb 19 01:09:10 2010
Return-Path: <ebisawa@sablenetworks.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 E0E4E28C149 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 01:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 MfYNjTQ5UELt for <behave@core3.amsl.com>; Fri, 19 Feb 2010 01:09:10 -0800 (PST)
Received: from sablenetworks.net (sablenetworks.net [202.229.133.90]) by core3.amsl.com (Postfix) with ESMTP id C7A4F28C113 for <behave@ietf.org>; Fri, 19 Feb 2010 01:09:09 -0800 (PST)
Received: (qmail 12643 invoked by SAV 20100218.073 by uid 0); 19 Feb 2010 18:10:54 +0900
Received: from unknown (HELO ?192.168.11.6?) (ebisawa@220.219.184.150) by dc12.etius.jp (202.229.133.90) with ESMTPA; 19 Feb 2010 18:10:54 +0900
Date: Fri, 19 Feb 2010 18:10:40 +0900
From: Kentaro Ebisawa <ebisawa@sablenetworks.net>
To: Xing Li <xing@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>
Message-Id: <20100219174313.58C9.B01659E3@sablenetworks.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.50 [ja]
Cc: "draft-ietf-behave-v6v4-xlate@tools.ietf.org" <draft-ietf-behave-v6v4-xlate@tools.ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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, 19 Feb 2010 09:09:11 -0000

Hi,

I've reviewed xlate-09 and here's some comments.

1. In "8. Appendix:", Address 166.111.1.2 is used as an example.
   Should't we use address from RFC5737 (198.51.100.0/24, 203.0.113.0/24) insted ?

2. In "3.3.  Translating ICMPv4 Error Messages into ICMPv6" :
>   There are some differences between the ICMPv4 and the ICMPv6 error
>   message formats as detailed above.  In addition, the ICMP error
>   messages contain for the packet in error, which needs to be

I think it should be ...

   message formats as detailed above.  In addition, the ICMP error
   messages contain packet in error, which needs to be

3. [Page 23]
>   addresses.  In this case, the translator can ether do stateful

ether -> either


Thanks,
-- 
Kentaro Ebisawa <ebisawa@sablenetworks.net>


From marka@isc.org  Fri Feb 19 02:08:35 2010
Return-Path: <marka@isc.org>
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 12A393A811C for <behave@core3.amsl.com>; Fri, 19 Feb 2010 02:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  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 ja4ajPDIa7VS for <behave@core3.amsl.com>; Fri, 19 Feb 2010 02:08:34 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 066BD3A8116 for <behave@ietf.org>; Fri, 19 Feb 2010 02:08:34 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 1E542E606C; Fri, 19 Feb 2010 10:10:17 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1JAAFJ1077149; Fri, 19 Feb 2010 21:10:15 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002191010.o1JAAFJ1077149@drugs.dv.isc.org>
To: Matthijs Mekking <matthijs@nlnetlabs.nl>
From: Mark Andrews <marka@isc.org>
References: <20100215164502.935AB28C10C@core3.amsl.com> <20100215164837.GQ25973@shinkuro.com> <4B7D3C29.2000109@nlnetlabs.nl> <201002182245.o1IMjsO1028957@drugs.dv.isc.org> <4B7E4C01.1040206@nlnetlabs.nl> 
In-reply-to: Your message of "Fri, 19 Feb 2010 09:29:53 BST." <4B7E4C01.1040206@nlnetlabs.nl> 
Date: Fri, 19 Feb 2010 21:10:15 +1100
Sender: marka@isc.org
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Fri, 19 Feb 2010 10:08:35 -0000

In message <4B7E4C01.1040206@nlnetlabs.nl>, Matthijs Mekking writes:
> 
> Or you handle a time out event as a SERVFAIL (and thus for DNS64 you may
> query for A records).
> 
> Or you mention that this set up is broken, just like returning NXDOMAIN
> is on AAAA query (but there are other records on that name).
> 
> Either way, additional text to clarify would be useful imo.
> Than my preference is the first option, since you already got into
> special error handling.
> 
> Also its not that hard to query for A records after a timed out event,
> especially if the resolver already treats it as SERVFAIL. So its little
> work to reduce the pain for clients.

Except for the 99.999 of RFC compliant servers out there trying a
A will not succeed after the AAAA times out.  Remember the recursive
server has already possibly made lots of queries in attempts to get
through broken firewalls and has most probably tried multiple
servers with the AAAA query.
 
> Best regards,
> 
> Matthijs
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From matthijs@nlnetlabs.nl  Fri Feb 19 02:24:13 2010
Return-Path: <matthijs@nlnetlabs.nl>
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 B2F973A811F for <behave@core3.amsl.com>; Fri, 19 Feb 2010 02:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 mP8YVpj57zWz for <behave@core3.amsl.com>; Fri, 19 Feb 2010 02:24:12 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id 179EE3A811E for <behave@ietf.org>; Fri, 19 Feb 2010 02:24:11 -0800 (PST)
Received: from [192.168.1.9] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.3/8.14.3) with ESMTP id o1JAPhZ2030115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Feb 2010 11:25:54 +0100 (CET) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4B7E676B.30102@nlnetlabs.nl>
Date: Fri, 19 Feb 2010 11:26:51 +0100
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
Organization: NLnet Labs
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
References: <20100215164502.935AB28C10C@core3.amsl.com>	<20100215164837.GQ25973@shinkuro.com>	<4B7D3C29.2000109@nlnetlabs.nl>	<201002182245.o1IMjsO1028957@drugs.dv.isc.org>	<4B7E4C01.1040206@nlnetlabs.nl> <201002191010.o1JAAFJ1077149@drugs.dv.isc.org>
In-Reply-To: <201002191010.o1JAAFJ1077149@drugs.dv.isc.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (open.nlnetlabs.nl [213.154.224.1]); Fri, 19 Feb 2010 11:25:55 +0100 (CET)
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Fri, 19 Feb 2010 10:24:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The same amount of name servers would also not return false RCODE
responses. Why make exceptions for those name servers?

Matthijs

Mark Andrews wrote:
> In message <4B7E4C01.1040206@nlnetlabs.nl>, Matthijs Mekking writes:
>> Or you handle a time out event as a SERVFAIL (and thus for DNS64 you may
>> query for A records).
>>
>> Or you mention that this set up is broken, just like returning NXDOMAIN
>> is on AAAA query (but there are other records on that name).
>>
>> Either way, additional text to clarify would be useful imo.
>> Than my preference is the first option, since you already got into
>> special error handling.
>>
>> Also its not that hard to query for A records after a timed out event,
>> especially if the resolver already treats it as SERVFAIL. So its little
>> work to reduce the pain for clients.
> 
> Except for the 99.999 of RFC compliant servers out there trying a
> A will not succeed after the AAAA times out.  Remember the recursive
> server has already possibly made lots of queries in attempts to get
> through broken firewalls and has most probably tried multiple
> servers with the AAAA query.
>  
>> Best regards,
>>
>> Matthijs
>>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJLfmdmAAoJEA8yVCPsQCW50lcIALH1OGRmiFIc0JpoFivQjD79
y5h9QVAW2Uk6CPSBeLK121ZTz5/RcFIeBQNp5fJVKmPNXcOOUZjRJwEvIIkpEzoo
Wn/59Iv+NKLFbwnNh5Mb8uIiwyHx/mBaMsaERBlsdZXX3JS9U1devWCnuJvtPEtQ
vbCLgZEovkXgcz6cdL/ZMlRSWVe5huMOWy3p3A5ZH94tsToBbj8VbXKqSgsbcvkO
IA+1ME3AoBNnfQK/TwD6w2TXEORFMhjaP+bdXq2xbPGWbIKOQqZ6Y86YsLS4eo+6
53PIPPKGMgADwtOonYqYUcOt08Gux+lIEb95fIZuvAVemvsRet64K0ic0tgrLPk=
=T/f6
-----END PGP SIGNATURE-----

From simon.perreault@viagenie.ca  Fri Feb 19 05:22:52 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 5FFDE3A815C for <behave@core3.amsl.com>; Fri, 19 Feb 2010 05:22:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 tagged_above=-999 required=5 tests=[AWL=0.238,  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 A8mqcgq0c--f for <behave@core3.amsl.com>; Fri, 19 Feb 2010 05:22:51 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id 5E6D33A815A for <behave@ietf.org>; Fri, 19 Feb 2010 05:22:51 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 45CAD21BC4 for <behave@ietf.org>; Fri, 19 Feb 2010 08:24:36 -0500 (EST)
Message-ID: <4B7E9113.2050205@viagenie.ca>
Date: Fri, 19 Feb 2010 08:24:35 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <20100215164502.935AB28C10C@core3.amsl.com>	<20100215164837.GQ25973@shinkuro.com>	<4B7D3C29.2000109@nlnetlabs.nl> <201002182245.o1IMjsO1028957@drugs.dv.isc.org>
In-Reply-To: <201002182245.o1IMjsO1028957@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Fri, 19 Feb 2010 13:22:52 -0000

On 2010-02-18 17:45, Mark Andrews wrote:
> This senario is pretty rare these days.  Just SERVFAIL the client
> on timeout.

 From an implementation point of view, in both Unbound and Bind, this 
would be hard. From where the DNS64 functionality is, we see a SERVFAIL 
on timeout. We have no way of knowing whether this was caused by a 
timeout or otherwise.

It would be the same situation if a DNS64 was using a forwarder which 
returned SERVFAIL on timeout from an authoritative server.

Handling timeout like SERVFAIL (not as NXDOMAIN) makes more sense.

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

From xing@cernet.edu.cn  Fri Feb 19 05:33:06 2010
Return-Path: <xing@cernet.edu.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 D5B833A814E for <behave@core3.amsl.com>; Fri, 19 Feb 2010 05:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.269
X-Spam-Level: 
X-Spam-Status: No, score=0.269 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 nhBy67bnK9MX for <behave@core3.amsl.com>; Fri, 19 Feb 2010 05:33:06 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 86FEA3A8126 for <behave@ietf.org>; Fri, 19 Feb 2010 05:33:04 -0800 (PST)
Received: from [192.168.1.101]([112.67.10.127]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm324b7ecb2b; Fri, 19 Feb 2010 21:34:14 +0800
Message-ID: <4B7E934C.5070706@cernet.edu.cn>
Date: Fri, 19 Feb 2010 21:34:04 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Kentaro Ebisawa <ebisawa@sablenetworks.net>
References: <20100219174313.58C9.B01659E3@sablenetworks.net>
In-Reply-To: <20100219174313.58C9.B01659E3@sablenetworks.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 7pmz2iXB
Cc: "draft-ietf-behave-v6v4-xlate@tools.ietf.org" <draft-ietf-behave-v6v4-xlate@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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, 19 Feb 2010 13:33:07 -0000

Kentaro Ebisawa 写道:
> Hi,
>
> I've reviewed xlate-09 and here's some comments.
>
> 1. In "8. Appendix:", Address 166.111.1.2 is used as an example.
>    Should't we use address from RFC5737 (198.51.100.0/24, 203.0.113.0/24) insted ?
>   

yes. we will use the document block in next version.
> 2. In "3.3.  Translating ICMPv4 Error Messages into ICMPv6" :
>   
>>   There are some differences between the ICMPv4 and the ICMPv6 error
>>   message formats as detailed above.  In addition, the ICMP error
>>   messages contain for the packet in error, which needs to be
>>     
>
> I think it should be ...
>
>    message formats as detailed above.  In addition, the ICMP error
>    messages contain packet in error, which needs to be
>   

yes, corrected.

> 3. [Page 23]
>   
>>   addresses.  In this case, the translator can ether do stateful
>>     
>
> ether -> either
>
>   
yes, corrected.

thanks.

regards,

xing

> Thanks,
>   


From simon.perreault@viagenie.ca  Fri Feb 19 06:31:43 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 1498B3A7CDD for <behave@core3.amsl.com>; Fri, 19 Feb 2010 06:31:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.388
X-Spam-Level: 
X-Spam-Status: No, score=-2.388 tagged_above=-999 required=5 tests=[AWL=0.211,  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 OWFbrkMfjQWw for <behave@core3.amsl.com>; Fri, 19 Feb 2010 06:31:41 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id CC54C3A6A3D for <behave@ietf.org>; Fri, 19 Feb 2010 06:31:41 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0FA36210F7 for <behave@ietf.org>; Fri, 19 Feb 2010 09:33:25 -0500 (EST)
Message-ID: <4B7EA135.4060703@viagenie.ca>
Date: Fri, 19 Feb 2010 09:33:25 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: "behave@ietf.org" <behave@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 14:31:43 -0000

Hello,

Two questions:

- Does NAT64's session handling work with packets arriving out of order? 
I'm not talking about fragments here.

- Is a NAT64 allowed to reorder packets?

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

From denghui02@gmail.com  Fri Feb 19 06:50:18 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 AD0B428C1F0; Fri, 19 Feb 2010 06:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level: 
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=0.233,  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 jyea1x61DlAR; Fri, 19 Feb 2010 06:50:17 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 4038F3A7EBD; Fri, 19 Feb 2010 06:50:16 -0800 (PST)
Received: by pwi3 with SMTP id 3so63750pwi.31 for <multiple recipients>; Fri, 19 Feb 2010 06:52:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=yLHz6VYlRFZDIhzDiex9OxwXa4B/P4psr2BeoJh3RAo=; b=nwld+9Tmes3aM+dcqcWlFVKM8JZO2EjVRVIBgUTvNhEycO0eC0Cx2WbCbcWNW3D8ZY PKz9gbPAWWP4vIY5Yh8TJH+xG1F1n4nyiZ0jgZsLFP3D6ONxsRJgIfB7Y51oKU7aNpwC /sJ31UbCIcWWm2Cp32FqbscLrWlj7jvMH98o4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=UA9WLlCkIsaebPiA0URZuXWid6MdVzv9hl9L7fMOP8trH0/9kaRckdCZKj96XtXw2v iN7B3SEpI3Qiw8oVYDhhlt3sZLruO0E+GqpnDgRZByEikHxeRIuKjHqDjmZWkOqPzZjs Ui8VBfbnR1zGrwl5bIjcGpltcq6ctalXnbNlA=
MIME-Version: 1.0
Received: by 10.140.180.6 with SMTP id c6mr7377523rvf.73.1266591119906; Fri,  19 Feb 2010 06:51:59 -0800 (PST)
Date: Fri, 19 Feb 2010 22:51:59 +0800
Message-ID: <1d38a3351002190651s7b9b516ey6a2c42eea309c771@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: 3gv6@ietf.org, behave@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [BEHAVE] PNAT drafts updated
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, 19 Feb 2010 14:50:18 -0000

Dear all,

We have published the updated PNAT based on sufficient review comments
the newest drafts have many scenarios clarification and usage example scena=
rio.

Please feel free to have comments on it
http://tools.ietf.org/html/draft-huang-behave-rfc2767bis-01
http://tools.ietf.org/html/draft-huang-behave-rfc3338bis-01
http://www.ietf.org/internet-drafts/draft-huang-behave-pnat-01.txt

Wish you have a good trip to SF and see u in the workshop
thanks again.

-Hui


---------- Forwarded message ----------
From:  <Internet-Drafts@ietf.org>
Date: 2010/2/19
Subject: I-D Action:draft-huang-behave-pnat-01.txt
To: i-d-announce@ietf.org


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

=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Prefix NAT: Host based IPv6 tran=
slation
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : B. Huang, H. Deng
=A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-huang-behave-pnat-01.txt
=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 26
=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-02-19

IPv4 migrating to IPv6 is a network layer's issue, it is not easy to
mandate all the applications in the host to change in the first
place, the network layer may have to have a solution to support the
conventional IPv4 appliations during the IPv6 migration such as in
the dual stack or IPv6 only network, especially when multiple
applications need to be supported. =A0This document describes a
mechanism for providing a host-based IPv6 translation technology
which could guarantee IPv4 application backward compatibility.
Applications need not necessarily to understand what the network
connection and the destination's IP family type are. =A0A well-known
prefix could be used when the destination is public IPv4 Internet's
address.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-huang-behave-pnat-01.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.


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From marcelo@it.uc3m.es  Fri Feb 19 07:19:46 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 9C7DB3A7CD6 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 07:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.535
X-Spam-Level: 
X-Spam-Status: No, score=-106.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, 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 FCqawuFOzzEo for <behave@core3.amsl.com>; Fri, 19 Feb 2010 07:19:45 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 8B9BB3A797E for <behave@ietf.org>; Fri, 19 Feb 2010 07:19:45 -0800 (PST)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id 99B1B7F7D87 for <behave@ietf.org>; Fri, 19 Feb 2010 16:21:30 +0100 (CET)
Message-ID: <4B7EAC75.4020002@it.uc3m.es>
Date: Fri, 19 Feb 2010 16:21:25 +0100
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.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <4B7EA135.4060703@viagenie.ca>
In-Reply-To: <4B7EA135.4060703@viagenie.ca>
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-17162.002
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 15:19:46 -0000

El 19/02/10 15:33, Simon Perreault escribió:
> Hello,
>
> Two questions:
>
> - Does NAT64's session handling work with packets arriving out of 
> order? I'm not talking about fragments here.
>
you mean TCP 3 way handshake arriving in the wrong order?
or soemthing else?

> - Is a NAT64 allowed to reorder packets?
>
Not sure why it would do that... the draft doesn't explicitly frbids 
that, but it probably should i guess

Regards, marcelo


> Thanks,
> Simon


From simon.perreault@viagenie.ca  Fri Feb 19 07:41:54 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 CC6703A816A for <behave@core3.amsl.com>; Fri, 19 Feb 2010 07:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.426
X-Spam-Level: 
X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=0.173,  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 YKzvXjidCOvs for <behave@core3.amsl.com>; Fri, 19 Feb 2010 07:41:53 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id C17DB3A7F71 for <behave@ietf.org>; Fri, 19 Feb 2010 07:41:53 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 18C14210F7 for <behave@ietf.org>; Fri, 19 Feb 2010 10:43:40 -0500 (EST)
Message-ID: <4B7EB1AB.4020103@viagenie.ca>
Date: Fri, 19 Feb 2010 10:43:39 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <4B7EA135.4060703@viagenie.ca> <4B7EAC75.4020002@it.uc3m.es>
In-Reply-To: <4B7EAC75.4020002@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 15:41:54 -0000

On 2010-02-19 10:21, marcelo bagnulo braun wrote:
>> - Does NAT64's session handling work with packets arriving out of
>> order? I'm not talking about fragments here.
>
> you mean TCP 3 way handshake arriving in the wrong order?
> or soemthing else?

Any kind of reordering. I haven't studied the possible cases in detail. 
I mean, take a look at RFC 793:

   Reliability:

     The TCP must recover from data that is damaged, lost, duplicated, or
     delivered out of order by the internet communication system.  This
     is achieved by assigning a sequence number to each octet
     transmitted, and requiring a positive acknowledgment (ACK) from the
     receiving TCP.  If the ACK is not received within a timeout
     interval, the data is retransmitted.  At the receiver, the sequence
     numbers are used to correctly order segments that may be received
     out of order and to eliminate duplicates.

Since our state machine is not exactly that of a real TCP endpoint, do 
we have the same reliability with regard to reordering or not? Has 
thought been given to this?

>> - Is a NAT64 allowed to reorder packets?
>
> Not sure why it would do that... the draft doesn't explicitly frbids
> that, but it probably should i guess

Here's a hint: multi-threading

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

From marcelo@it.uc3m.es  Fri Feb 19 08:22:46 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 4D42828C1F0 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 08:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.541
X-Spam-Level: 
X-Spam-Status: No, score=-106.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, 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 RYoh5mgYbJjG for <behave@core3.amsl.com>; Fri, 19 Feb 2010 08:22:44 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id 9158928C23A for <behave@ietf.org>; Fri, 19 Feb 2010 08:22:44 -0800 (PST)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id E7600BAAE54 for <behave@ietf.org>; Fri, 19 Feb 2010 17:24:29 +0100 (CET)
Message-ID: <4B7EBB3D.70205@it.uc3m.es>
Date: Fri, 19 Feb 2010 17:24:29 +0100
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.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <4B7EA135.4060703@viagenie.ca> <4B7EAC75.4020002@it.uc3m.es> <4B7EB1AB.4020103@viagenie.ca>
In-Reply-To: <4B7EB1AB.4020103@viagenie.ca>
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-17162.002
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 16:22:46 -0000

El 19/02/10 16:43, Simon Perreault escribió:
> On 2010-02-19 10:21, marcelo bagnulo braun wrote:
>>> - Does NAT64's session handling work with packets arriving out of
>>> order? I'm not talking about fragments here.
>>
>> you mean TCP 3 way handshake arriving in the wrong order?
>> or soemthing else?
>
> Any kind of reordering. I haven't studied the possible cases in 
> detail. I mean, take a look at RFC 793:
>
>   Reliability:
>
>     The TCP must recover from data that is damaged, lost, duplicated, or
>     delivered out of order by the internet communication system.  This
>     is achieved by assigning a sequence number to each octet
>     transmitted, and requiring a positive acknowledgment (ACK) from the
>     receiving TCP.  If the ACK is not received within a timeout
>     interval, the data is retransmitted.  At the receiver, the sequence
>     numbers are used to correctly order segments that may be received
>     out of order and to eliminate duplicates.
>
> Since our state machine is not exactly that of a real TCP endpoint, do 
> we have the same reliability with regard to reordering or not? Has 
> thought been given to this?
yes, i did some thought on this (not sure if that is enough though)

So, afaict, the order of packets is irrelevant (meaning that don't 
affect nat64 behaviour) for all cases except for the 3 way handshake.
in the 3 way handshake case, we probably need to understand it more, but 
reordering of the 3 way handshake would only happen with retrial, so it 
is not really reordering, but handling duplicates, which i think are 
properly handled (we do support TCP SO)

So, do you have any scenario in mind where there can be problem?
>
>>> - Is a NAT64 allowed to reorder packets?
>>
>> Not sure why it would do that... the draft doesn't explicitly frbids
>> that, but it probably should i guess
>
> Here's a hint: multi-threading
>
do you think we should mention something?

Regards, marcelo

> Simon


From simon.perreault@viagenie.ca  Fri Feb 19 08:36:43 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 6F9B628C2D8 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 08:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.158,  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 r8KjfiNFtVfw for <behave@core3.amsl.com>; Fri, 19 Feb 2010 08:36:42 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id 5FC3328C2BA for <behave@ietf.org>; Fri, 19 Feb 2010 08:36:42 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id A91D321CC5 for <behave@ietf.org>; Fri, 19 Feb 2010 11:38:28 -0500 (EST)
Message-ID: <4B7EBE84.8040301@viagenie.ca>
Date: Fri, 19 Feb 2010 11:38:28 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <4B7EA135.4060703@viagenie.ca> <4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca> <4B7EBB3D.70205@it.uc3m.es>
In-Reply-To: <4B7EBB3D.70205@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 16:36:43 -0000

On 2010-02-19 11:24, marcelo bagnulo braun wrote:
> So, afaict, the order of packets is irrelevant (meaning that don't
> affect nat64 behaviour) for all cases except for the 3 way handshake.
> in the 3 way handshake case, we probably need to understand it more, but
> reordering of the 3 way handshake would only happen with retrial, so it
> is not really reordering, but handling duplicates, which i think are
> properly handled (we do support TCP SO)

Thanks.

> So, do you have any scenario in mind where there can be problem?

No, nothing specific at this point.

>>>> - Is a NAT64 allowed to reorder packets?
>>
>> Here's a hint: multi-threading
>>
> do you think we should mention something?

First, I don't know if it should go into the stateful or stateless 
document, or both.

Second, how about "Translation MAY reorder packets."?

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

From brian.e.carpenter@gmail.com  Fri Feb 19 13:01:44 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 E4C8D28C0FB for <behave@core3.amsl.com>; Fri, 19 Feb 2010 13:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level: 
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[AWL=-0.023, 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 mf10KBVW9qZu for <behave@core3.amsl.com>; Fri, 19 Feb 2010 13:01:44 -0800 (PST)
Received: from mail-qy0-f177.google.com (mail-qy0-f177.google.com [209.85.221.177]) by core3.amsl.com (Postfix) with ESMTP id 0CD563A6A10 for <behave@ietf.org>; Fri, 19 Feb 2010 13:01:43 -0800 (PST)
Received: by qyk8 with SMTP id 8so290721qyk.14 for <behave@ietf.org>; Fri, 19 Feb 2010 13:03:27 -0800 (PST)
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=Snwd6V7yqCtV731DKzMMr4oqMWO991P7YQVlV8EBiW8=; b=fjEOnOZ1+fpvJh8mFDQRePrydrUnWs1AYW6Yycw4wBJigsjU/Wggp23HYJ+bhVeNxR W7OSi2BRU14/3jwVyRY1i5q+tLvHMhy6weRRaDF6J5sELqtioqtX0fkuvZIJI7T2b+GH xpEqFmOjb3aHldyrFoeR0jzuVEYgaBxSwcFn0=
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=PTQAUYQV2IjhtjZ+/oN+WfETMDc8rCnYePdfvm7ZkUlh8lBBytNhLXyECMKXBgtU25 hSlOwoi3DuWBAgLUSBtqAMFt3i9uE6oVVfOSW/u5fnoXmNNDLPVUVQgBM3KEdFRYIzoL l8goPxZZRHanPvn/V9i6lZgq3Tzh8nkWNo5lc=
Received: by 10.224.73.35 with SMTP id o35mr3815690qaj.386.1266613407445; Fri, 19 Feb 2010 13:03:27 -0800 (PST)
Received: from ?10.1.1.5? ([121.98.142.15]) by mx.google.com with ESMTPS id 5sm1466616qwg.28.2010.02.19.13.03.24 (version=SSLv3 cipher=RC4-MD5); Fri, 19 Feb 2010 13:03:26 -0800 (PST)
Message-ID: <4B7EFC98.7050602@gmail.com>
Date: Sat, 20 Feb 2010 10:03:20 +1300
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: Simon Perreault <simon.perreault@viagenie.ca>
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es> <4B7EBE84.8040301@viagenie.ca>
In-Reply-To: <4B7EBE84.8040301@viagenie.ca>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 21:01:45 -0000

On 2010-02-20 05:38, Simon Perreault wrote:
...
> First, I don't know if it should go into the stateful or stateless
> document, or both.

imho, stateless (and if I am not mistaken about the normative
dependency, it then also automatically applies to stateful).

Reason: we really need the same behaviour in all translators.

> 
> Second, how about "Translation MAY reorder packets."?

Disagree. Reordering is generally evil and should be avoided as
much as possible, because it damages TCP performance and can do even
worse things to UDP streams. So I think we should invert this and
say

Translators SHOULD be designed to avoid packet reordering as much
as possible.

If you want to multithread, that means selecting a thread
according to some sort of hash of the 5-tuple (IPv4) or
6-tuple (including flow label) for IPv6. I don't see it as
different from any other load balancing mechanism.

    Brian


From ssenthil@cisco.com  Fri Feb 19 13:22:14 2010
Return-Path: <ssenthil@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 565463A7D8D for <behave@core3.amsl.com>; Fri, 19 Feb 2010 13:22:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.339
X-Spam-Level: 
X-Spam-Status: No, score=-10.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 6XUjKKkpZbB0 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 13:22:13 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 7604328C15B for <behave@ietf.org>; Fri, 19 Feb 2010 13:22:13 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHuQfkurRN+K/2dsb2JhbACbCXOmEJduhGcEgxU
X-IronPort-AV: E=Sophos;i="4.49,505,1262563200"; d="scan'208";a="301010643"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 19 Feb 2010 21:24:01 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1JLO18O000352; Fri, 19 Feb 2010 21:24:01 GMT
Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Feb 2010 13:24:01 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Feb 2010 13:24:02 -0800
Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <4B7EFC98.7050602@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] NAT64: Out of order session handling
Thread-Index: AcqxpwTRQozB0GbtT/e8leULIJVR/gAAenAg
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca> <4B7EFC98.7050602@gmail.com>
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Simon Perreault" <simon.perreault@viagenie.ca>
X-OriginalArrivalTime: 19 Feb 2010 21:24:01.0377 (UTC) FILETIME=[DAE8F510:01CAB1A9]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 19 Feb 2010 21:22:14 -0000

With stateless, theoriticaly two packets of the same flow can go through
two different translators and make it to the end point, can it not? How
can the translator keep track of the ordering of the packets?=20
Stateless is a little different, but even there, except for the initial
handshake the packets can come through in different order and you cant
hold on to a packet in the translator and order them. I think this is
best left undefined and left to the end point application and translator
implementation. Do we know of any application that would fail if the
translator doesn't send the packets in the right order?=20

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of Brian E Carpenter
Sent: Friday, February 19, 2010 4:03 PM
To: Simon Perreault
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling

On 2010-02-20 05:38, Simon Perreault wrote:
...
> First, I don't know if it should go into the stateful or stateless=20
> document, or both.

imho, stateless (and if I am not mistaken about the normative
dependency, it then also automatically applies to stateful).

Reason: we really need the same behaviour in all translators.

>=20
> Second, how about "Translation MAY reorder packets."?

Disagree. Reordering is generally evil and should be avoided as much as
possible, because it damages TCP performance and can do even worse
things to UDP streams. So I think we should invert this and say

Translators SHOULD be designed to avoid packet reordering as much as
possible.

If you want to multithread, that means selecting a thread according to
some sort of hash of the 5-tuple (IPv4) or 6-tuple (including flow
label) for IPv6. I don't see it as different from any other load
balancing mechanism.

    Brian

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

From marka@isc.org  Fri Feb 19 14:14:49 2010
Return-Path: <marka@isc.org>
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 719E73A7B99 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 14:14:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level: 
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.072,  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 OH4Rnx6GMkV3 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 14:14:47 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 03F553A6F85 for <behave@ietf.org>; Fri, 19 Feb 2010 14:14:46 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 0F4B6E606C; Fri, 19 Feb 2010 22:16:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id o1JMGT7q089538; Sat, 20 Feb 2010 09:16:29 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <201002192216.o1JMGT7q089538@drugs.dv.isc.org>
To: Simon Perreault <simon.perreault@viagenie.ca>
From: Mark Andrews <marka@isc.org>
References: <20100215164502.935AB28C10C@core3.amsl.com> <20100215164837.GQ25973@shinkuro.com> <4B7D3C29.2000109@nlnetlabs.nl> <201002182245.o1IMjsO1028957@drugs.dv.isc.org> <4B7E9113.2050205@viagenie.ca> 
In-reply-to: Your message of "Fri, 19 Feb 2010 08:24:35 CDT." <4B7E9113.2050205@viagenie.ca> 
Date: Sat, 20 Feb 2010 09:16:29 +1100
Sender: marka@isc.org
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Fri, 19 Feb 2010 22:14:49 -0000

In message <4B7E9113.2050205@viagenie.ca>, Simon Perreault writes:
> On 2010-02-18 17:45, Mark Andrews wrote:
> > This senario is pretty rare these days.  Just SERVFAIL the client
> > on timeout.
> 
> From an implementation point of view, in both Unbound and Bind, this 
> would be hard. From where the DNS64 functionality is, we see a SERVFAIL 
> on timeout. We have no way of knowing whether this was caused by a 
> timeout or otherwise.
> 
> It would be the same situation if a DNS64 was using a forwarder which 
> returned SERVFAIL on timeout from an authoritative server.
> 
> Handling timeout like SERVFAIL (not as NXDOMAIN) makes more sense.

Handling NOTIMP/REFUSED/SERVFAIL as SERVFAIL to the client would
actually make more sense.  The survey of the top 3000(?) sites
showed that error responses to A and AAAA responses were basically
consistent.  They will also only get more consistent as time goes
on.  Lets not code workarounds for broken servers into DNS64.

If a site has a load balance that returns NOTIMP to a AAAA query a
decade after the introduction of AAAA records rather than a
NOERROR/NODATA response they don't deserve to have a A query made.
If you don't implement AAAA they you definitely can't return AAAA
but you can say you have no AAAA records.  The only record type
where NOTIMP is correct are the reserved meta types.

If a site incorrectly returns REFUSED to AAAA query they don't
deserve a A query.  "I won't tell you I don't any AAAA records but
I'll tell you I have A records." is what that response is saying.

>From a implemention point of view you have success (NOERROR or
NXDOMAIN) and failure of the AAAA query.  Requerying for A after
failure made some sense 10 years ago but should have been removed
about 5 years ago.  All it is doing now is causing extra work to
be done for almost no benefit.

Mark

> Simon
> -- 
> NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
> STUN/TURN server        --> http://numb.viagenie.ca
> vCard 4.0               --> http://www.vcarddav.org
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From xing@cernet.edu.cn  Fri Feb 19 18:37:19 2010
Return-Path: <xing@cernet.edu.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 A444A3A7E09 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 18:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.253
X-Spam-Level: 
X-Spam-Status: No, score=0.253 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 8mEDbIhDQDdS for <behave@core3.amsl.com>; Fri, 19 Feb 2010 18:37:18 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 4422A3A7E08 for <behave@ietf.org>; Fri, 19 Feb 2010 18:37:17 -0800 (PST)
Received: from [192.168.1.101]([124.225.139.33]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b7f5517; Sat, 20 Feb 2010 10:39:05 +0800
Message-ID: <4B7F4B3F.9050607@cernet.edu.cn>
Date: Sat, 20 Feb 2010 10:38:55 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com> <85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 5XTPfiXB
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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: Sat, 20 Feb 2010 02:37:19 -0000

Senthil Sivakumar (ssenthil) 写道:
> With stateless, theoriticaly two packets of the same flow can go through
> two different translators and make it to the end point, can it not? How
> can the translator keep track of the ordering of the packets? 
> Stateless (stateful?) is a little different, but even there, except for the initial
> handshake the packets can come through in different order and you cant
> hold on to a packet in the translator and order them. I think this is
> best left undefined and left to the end point application and translator
> implementation. Do we know of any application that would fail if the
> translator doesn't send the packets in the right order? 
>   

Agree. Stateless translator should behave like a router when dealing 
with L4 and above. xing
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Brian E Carpenter
> Sent: Friday, February 19, 2010 4:03 PM
> To: Simon Perreault
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] NAT64: Out of order session handling
>
> On 2010-02-20 05:38, Simon Perreault wrote:
> ...
>   
>> First, I don't know if it should go into the stateful or stateless 
>> document, or both.
>>     
>
> imho, stateless (and if I am not mistaken about the normative
> dependency, it then also automatically applies to stateful).
>
> Reason: we really need the same behaviour in all translators.
>
>   
>> Second, how about "Translation MAY reorder packets."?
>>     
>
> Disagree. Reordering is generally evil and should be avoided as much as
> possible, because it damages TCP performance and can do even worse
> things to UDP streams. So I think we should invert this and say
>
> Translators SHOULD be designed to avoid packet reordering as much as
> possible.
>
> If you want to multithread, that means selecting a thread according to
> some sort of hash of the 5-tuple (IPv4) or 6-tuple (including flow
> label) for IPv6. I don't see it as different from any other load
> balancing mechanism.
>
>     Brian
>
> _______________________________________________
> 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 xing@cernet.edu.cn  Fri Feb 19 19:11:29 2010
Return-Path: <xing@cernet.edu.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 D15743A72E7 for <behave@core3.amsl.com>; Fri, 19 Feb 2010 19:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.24
X-Spam-Level: 
X-Spam-Status: No, score=0.24 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 0SjqDtDGJmqF for <behave@core3.amsl.com>; Fri, 19 Feb 2010 19:11:27 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 263AF3A7D93 for <behave@ietf.org>; Fri, 19 Feb 2010 19:11:24 -0800 (PST)
Received: from [192.168.1.101]([124.225.139.33]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm164b7f5d09; Sat, 20 Feb 2010 11:13:01 +0800
Message-ID: <4B7F5335.8020900@cernet.edu.cn>
Date: Sat, 20 Feb 2010 11:12:53 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: 'Behave WG' <behave@ietf.org>,  Behave Chairs <behave-chairs@tools.ietf.org>
Content-Type: multipart/mixed; boundary="------------010003000803020706050108"
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 5DJmfiXB
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-address-format-04
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: Sat, 20 Feb 2010 03:11:29 -0000

This is a multi-part message in MIME format.
--------------010003000803020706050108
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit

Hi, All,

Recently, we have discussed the address format document with people who
wrote the code and did the testing for IPv4/IPv6 translator. Attached,
please find a file containing parts of section 3.3 and 3.5 with
modifications and comments.

(1) Some modifications are editorial for easier understanding.

(2) We suggest add a paragraph related the IPv4 and IPv6 address
architectures. It reads

Finally the usage of IPv4-Translatable IPv6 addresses SHOULD follow
both IPv6 address architecture as well as IPv4 address architecture.
The first IPv4-translatable address is the subnet-router anycast
address in IPv6 and network identifier in IPv4, the last IPv4-
translatable address is the subnet broadcast addresses in IPv4.
Both of them SHOULD NOT be used for IPv6 nodes. In addition,
to accommodate the IPv4 network address and broadcast address,
the minimum IPv4 subnet prefix length for hosts is /30 and this rule
SHOULD also be applied to the corresponding subnet of the IPv4-
translatable addresses. We will use this rule in section 3.5 for
selecting the Suffix.

We suggest including these changes in the next version of addres-format
document. If you have any questions, please let us know.

Regards,

xing, congxiao

--------------010003000803020706050108
Content-Type: application/pdf;
 name="address-format-comments-20100218-v5.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="address-format-comments-20100218-v5.pdf"

JVBERi0xLjQNJeLjz9MNCjE1IDAgb2JqIDw8L0xpbmVhcml6ZWQgMS9MIDczNzA5L08gMTcv
RSA1Nzc3MS9OIDQvVCA3MzM2Mi9IIFsgODk2IDI4MV0+Pg1lbmRvYmoNICAgICAgICAgICAg
ICAgICAgDQp4cmVmDQoxNSAzMA0KMDAwMDAwMDAxNiAwMDAwMCBuDQowMDAwMDAxMTc3IDAw
MDAwIG4NCjAwMDAwMDEyNTcgMDAwMDAgbg0KMDAwMDAwMTQ0MiAwMDAwMCBuDQowMDAwMDAx
NTg1IDAwMDAwIG4NCjAwMDAwMDE3MTYgMDAwMDAgbg0KMDAwMDAwMTc1MCAwMDAwMCBuDQow
MDAwMDAyMTUwIDAwMDAwIG4NCjAwMDAwMDIyMjYgMDAwMDAgbg0KMDAwMDAwMzIwOSAwMDAw
MCBuDQowMDAwMDA0MTUwIDAwMDAwIG4NCjAwMDAwMDUwOTAgMDAwMDAgbg0KMDAwMDAwNjEw
NiAwMDAwMCBuDQowMDAwMDA2OTg0IDAwMDAwIG4NCjAwMDAwMDgwNDIgMDAwMDAgbg0KMDAw
MDAwODE3MCAwMDAwMCBuDQowMDAwMDA4NTM4IDAwMDAwIG4NCjAwMDAwMDkwMjcgMDAwMDAg
bg0KMDAwMDAwOTMyOCAwMDAwMCBuDQowMDAwMDA5NTc2IDAwMDAwIG4NCjAwMDAwMDk4MTgg
MDAwMDAgbg0KMDAwMDAxMDk5NSAwMDAwMCBuDQowMDAwMDExODQyIDAwMDAwIG4NCjAwMDAw
MTQ1MTEgMDAwMDAgbg0KMDAwMDAzOTYwOCAwMDAwMCBuDQowMDAwMDM5OTAzIDAwMDAwIG4N
CjAwMDAwNDAyMDggMDAwMDAgbg0KMDAwMDA1NzM2NiAwMDAwMCBuDQowMDAwMDU3NjAxIDAw
MDAwIG4NCjAwMDAwMDA4OTYgMDAwMDAgbg0KdHJhaWxlcg0KPDwvU2l6ZSA0NS9QcmV2IDcz
MzUxL1Jvb3QgMTYgMCBSL0luZm8gMTQgMCBSL0lEWzw5QjU4QTEyMkQ3RkY0QkZDMUE5MDFB
Mzc2RkI4NDJEQT48QjQyNTg4QUY5NEEzNUU0NkFGNTFGODIwQUMzNThCQTk+XT4+DQpzdGFy
dHhyZWYNCjANCiUlRU9GDQogICAgICAgICAgICAgDQo0NCAwIG9iajw8L0xlbmd0aCAxOTQv
RmlsdGVyL0ZsYXRlRGVjb2RlL0kgMjMwL0wgMjE0L1MgMTM1Pj5zdHJlYW0NCnjaYmBgYAai
CwysDAzscxkEGBBAACjGysDCwHGAgeGqKvcertkMDD3JSCoYWQL3TsiJ9br141ybo+ib5qRX
YdePlRhxrE+RFg/ats94AQNDWlpaR0dHA4NYWloGkIEQYIMIwMxFAtJQzMCgxMDPqMe4hZmD
gUH3AFfjreZudhH+CKkEBwbuA8ENjxu5GdcwOyjvMLroWVF5oKmRv/UEswqLA9QYLgZGXqDD
GZiA2BqI+RgYZSpAjgbibwABBgC7VTc1DQplbmRzdHJlYW0NZW5kb2JqDTE2IDAgb2JqPDwv
TWV0YWRhdGEgMTMgMCBSL1BhZ2VzIDEyIDAgUi9UeXBlL0NhdGFsb2cvUGFnZUxhYmVscyAx
MCAwIFI+Pg1lbmRvYmoNMTcgMCBvYmo8PC9Dcm9wQm94WzAgMCA1OTUuMjIgODQyXS9QYXJl
bnQgMTIgMCBSL0NvbnRlbnRzWzIzIDAgUiAyNCAwIFIgMjUgMCBSIDI2IDAgUiAyNyAwIFIg
MjggMCBSIDM1IDAgUiAzNiAwIFJdL1JvdGF0ZSAwL01lZGlhQm94WzAgMCA1OTUuMjIgODQy
XS9SZXNvdXJjZXMgMTggMCBSL1R5cGUvUGFnZT4+DWVuZG9iag0xOCAwIG9iajw8L0NvbG9y
U3BhY2U8PC9DczYgMjAgMCBSPj4vRm9udDw8L1RUMSAxOSAwIFIvVFQyIDI5IDAgUi9UVDQg
MzAgMCBSL1RUNiAzMSAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0vRXh0R1N0YXRlPDwvR1Mx
IDIyIDAgUj4+Pj4NZW5kb2JqDTE5IDAgb2JqPDwvU3VidHlwZS9UeXBlMC9EZXNjZW5kYW50
Rm9udHNbNDAgMCBSXS9CYXNlRm9udC9ITEZHQkwrTVMtR290aGljL1RvVW5pY29kZSAyMSAw
IFIvRW5jb2RpbmcvSWRlbnRpdHktSC9UeXBlL0ZvbnQ+Pg1lbmRvYmoNMjAgMCBvYmpbL0lD
Q0Jhc2VkIDM3IDAgUl0NZW5kb2JqDTIxIDAgb2JqPDwvTGVuZ3RoIDMzMS9GaWx0ZXIvRmxh
dGVEZWNvZGU+PnN0cmVhbQ0KSIlUkj9vgzAQxXc+xY2tOmCMSxoJMSRZMvSPmrS7Y44UqRjL
kCHfvrYfTdUBrN/57r07jny73+1tP1P+5kdz4Jm63raep/HiDdOJz72lQlLbm3mh9DaDdpSH
4sN1mnnY226kus7y93A5zf5Kd8dj8SDuKX/1LfvenkNEyY/PEDlcnPvmge1MgpqGWu6yfPus
3YsemPJU+Bc8Xh2TTFws3mPLk9OGvbZnploIIZtwlEXVENv2/322QtWpM1/aZ7dsIUWTSIFk
IvmUSFWJynWixxWoBW1AHWgXKVnXUshQFzpYvNa/zmgkmkFQnOAJXcGJCljLbQoWGkGTjvIJ
3ZVIqdBkgSAyJTTVkgnNEqMqaJYYtVyhc0ysoKlQXkFTLaPCvdosU2GO+Inj+m8rMxfvwzbT
P5J2FrfVW779Rm50cTHxyX4EGAAK36rWCg0KZW5kc3RyZWFtDWVuZG9iag0yMiAwIG9iajw8
L09QTSAxL09QIGZhbHNlL29wIGZhbHNlL1R5cGUvRXh0R1N0YXRlL1NBIGZhbHNlL1NNIDAu
MDI+Pg1lbmRvYmoNMjMgMCBvYmo8PC9MZW5ndGggOTE0L0ZpbHRlci9GbGF0ZURlY29kZT4+
c3RyZWFtDQpIiZxXzW4bIRC+71PwAiH8DCwrWT40rSpFai/em5WD17WjRnEP9SGvX1hgGAxu
pcra7MIwAzPfN8Pk8etOstfr8GkeHudZMsnm8+C4c6CY8L/0OU7csdE6LpzQbL4Mgr0OD4IL
IRSbj344fwz7jRDS+EdsLXc4CGvCkyaV2T5YPvovOGyFfxmZJLCgxOSpMU+hvl8etMClsRek
JdpvY6DRxJWwePkhHgdcsBTWE9Maj2Zs1tFhEMz559TYNiY+waTOOsHmqieCMOuc8Dw6um0b
tzESRjRuKxvdHvMSdBtOVLPE8IynTUex+azbl/nZQ/YguTHaw/k54Hcc4nbzWxJZIYOIoLzf
3GC5up2iCBOGDP0R8cxLPtyRxCBNWZxaaoBNZpExJRjUrbLNQo4DCSyjcmSqBQ3A/wQr4b9U
8MS9QjQLIIC2Xe02FMaPHZ/y1BjdNi0tBIkuccFgDG95mkJgVqC15KCl9Mns0dwgBzzOD1lE
mNDFeKUOUNgEOYXY0NzQbQ51CR60sFIUr8J2armfB6uTh+xgfEfc2+RUCGfmQZUWNL6YHCfK
pSULWx2oSVrchlPjE/qjVdTKFUk66nZhvERjZedSaFasIbveYryvz4MmbFEr3CHcjEuSxYob
qRT0uZGBaEHzpBVVDUMiaIQTIyDzOcV51SLltErGtiwQ7pVkACiJ8PcDBBhyYDFUJXrdoBFA
WrhNdNtfb/fvtUNDbBjvMgq6d083JeBMMla23AjF3BpazAG2UnOTq1OyHBS/+J7g6WrZ8erb
AsGdNmrC9/X4a9Bg+OiYnSxXlsmRj/6v4qNiv0/DOfQUdzoJOzk+2W4n0eXYCqjp9gWp/phW
gsQvyEDuDvyNcJeZND9tG2wRawneM9jjtP0IZt6B1Kn/4RjpfUpTI2oOkK6qE6OKY5Rzecnh
Xpkrbq8onJAehBv+F/igJj5pZ0oVUksb0Nh7vA6ST9NEKtadCPebAKyAJeiUsU+7lbF+80mp
8rF7+j5I9uxlb2HSsg8mBfvG9i+C/fCSn2yl9LQyWit2oQwHYO83Y5SPYgysf78ZX5K5MHSr
utXc50Ax78cGiPlqjPJivhpfsj20v/tbzjnDfVTXnLt7yUem9m5fQdnQuWNJlSaY1S1raRoo
tNAmWb54YzOQOVTfEfluxYSRiTqu35Tl5shWaU9st/9QpE6d3KBNXnSSrHEbqZvqxAv7I8AA
PHvI0A0KZW5kc3RyZWFtDWVuZG9iag0yNCAwIG9iajw8L0xlbmd0aCA4NzIvRmlsdGVyL0Zs
YXRlRGVjb2RlPj5zdHJlYW0NCkiJtFbJjtswDL37K/wDUbVRloFBDl0uc61vxRySNClQTHro
/D9QURIp2ZInPbQYBGNtlPj4HsnleZDjQQkAY8blcxgsl+FJSqmPy8+85KTCpYMUOI8bvsUd
cZcTPg+MkhKslHbOk9YcD05M4QvkUeLEOa/AhVbCnjzleIp3qXgqHM5joC14nXV0zcTX0HPs
FU+H3xnNoQl8VvXeYgrYjMEBmsPzrW1IP7xa0wtNGICXUoVzSuXJsJrPGJ0c8HlF+eJA4zbY
AtuO2+jW+4AlV2M0woc+paiY6fiyPA9GCWuUGiVGE0Oor2RCuyqQEYnoLr2IPUIQ0w3R4oFM
VgzqcgNNxlfJFliX3J1L1BtEvjNuN0Ie0ind2LNQIWJ9A5LNQYyxsznevkbx1IlSAhfPFcLw
vmjinMzxGX2u+UEMYOcCS2SiSL6CX6o8A9eQNEAiV6qRNT8LbU1L7/OaH3H/FC12uQF95PCI
2iFAzhNdAhQ0CAlXxTQiUfnYJIfKTZb4Bokih8A1a8s2DtKW4pgUXP28NhQsi1vYA4Rgsy8B
SfmDrn5g20cHGKUSs5LZOslhSrwnGKrkMFXThTqaFTOlpGDys2zmfo6kfKzhxn/YapheCZUa
2/gUgPYQSIm2vaaonXRO2s1zrvG/yLpKjOUJlQu1Riq3lWXGN9jua7gQh4vBP9CwyWG7UuiY
XY2GsVg7oGIdk5A/KiPgiUP+ZRk+fHpz4+VtDIeEN6Bn/v92+TUEqIR1I8yzsH6cJ+H0qLSY
9Pj7OtyGj8vghfdWhxvlmD+nWfjRSS2UloFL90CsHw9bh+iYq+JX5YB3CN/tC/QtFjwqE4Xw
MLVJZOKcTkZP1eyKKW0iiYLo0ZprXfPSd2pdLHMNadhtvcP6VvGlsO0XQTgxqUutQ05UhAh/
kQTIATBV12CzSkoh5LaoND6kiNQcYf7EOMR3mZ3mZtuIrdi+eWfgLrITfGQn2PFes9WNr+sh
rzoVCO7Lch7fyZoL+nkdvg59QURygwcUgjHhufbv9ADeC+2SHgqyEczzFi1PkmiKgN1kWdsS
uq+OvSwruxmz290+LIAs3KqL7tmuzPr/kgHWDaI+0ZilhoVQE9m0a07CVLqjlBwoLfQ7papN
g4rC9sb1lSS8EnvbdqIkC2Iv4x8BBgBUddIMDQplbmRzdHJlYW0NZW5kb2JqDTI1IDAgb2Jq
PDwvTGVuZ3RoIDg3MS9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSImcV01v2zAMvftX
+A/EkC1RkoEgh2G79Drfih2SNhlQLP//On2SlKlk7VAEsGWKIh8fn9jtZfixDWa2E/gRPEzW
j/f0bk169+Of9pW+rm5S/HN+v6O38L6Ezz+Hb9vgJ+/NMqrwVx7dGpyBM5OxSo/bfVDj7/Db
3oajUmo5bR/h7TBPYNU8bt+Hg5riejR4TRbJyk6+vGinFIBS5lIWQZ0OdnLhyawndWTmYPHL
uSwZV5fICtIuo6vJDXc5brbUZTDoLPx8DCUsnnN4cS1EhK7rHleXTLGBB4HGSOIK+7wE/zr4
hnDW7BEL9K1SAjDXsMibE4Gg04CfOvJYLU8bc2ToIkDXnGqMEWZ6DiD/2l4GPU9Gz3NgQKgm
oRjqfKifYrlB62jQrXH0moBa65F6lyxV/03ExzJBq7lNloG3MjNzxZ1XHk6lnGuSfcgocysp
QApmfyTSxvOjIfOo5Y9lvlUmoQCkHhAiqktAZypuEmBAfw2PZY0hc5HSxUKKGr82NGE0bJge
tzUEKP3eJwDsaegZp1UmucAVjS+iJEtmu16Evzl22q0sayubPHajKiFdqTsJKiNIU4mSG1ce
6YtWaJZHhIvEQfRtSRu/zErkSEho3J8JgDpgyF/kWtUSg4AZYGmndK8Rz+C8NH0w7RLAeNkG
uhRTPRKnotaCGs+0IQXleLubvRCCAKTTJIhJaZKldqKmXVFvOzzTnOFN2fa6jv1mPE+hAoNR
UTcn1SvuLN9zKUDiHseo2ogbeWMqxjBqJNFIfym0VVCDYVjkzdV7Kqy9J9d9bUAUmNecTUz1
y9pQ5Ujq/V7vWLUvoqP47dsMAESoXIneMSwNaAuUnr0sBbakJR5TV1BfVnlxjcZFmSmLZ1kZ
9UgSP8F7ABnrrTXbO0sk7criPwlgnhfy63JAl9P/zEW9pr62sOzuTDlRsSGLZBIsh0nuwZui
lvvCAgXVHGlyqzW3S2Vdp09LAp3ep0jptsY0y/0iZ4JWqc4CsErodkxIgirYEGd7C3W2zzPt
adYTHMtk6x7cCJ/85yDfqKwVWC/vLtDeSEzjOitFu4sNCIwNbKdlVTIVmrVUmA+O3S4l+LQS
lUikWov4YqHe4/wS73w+HjqmO828TPc0Gz2lJC6P2NAMrXB+Kon7wXH8K8AAPzMCcg0KZW5k
c3RyZWFtDWVuZG9iag0yNiAwIG9iajw8L0xlbmd0aCA5NDcvRmlsdGVyL0ZsYXRlRGVjb2Rl
Pj5zdHJlYW0NCkiJhFfJbtwwDL37K/wDo0rWYhsI5tDlkmvnVuQQpzMFikwPzf8DFSWSoix5
isDImBZpLo+P9OV5sEY5a8yox8vX4ceT1t6fT0HN8Zez56AW+HGL16y1noTQexCcXy7Pw4mM
nIzy3loyBefjkXwebnyIBl7BGAvpZdN21vGfpeN+oScm0OEbiSyJvEtaxSlNR8A9d6UALIsD
i+Ll4EyJbdr6DiwihKQHYQgXKF9zfi1mpryHhG4j4cr+6BwAJSSaxSdswbPIm5I2XQXzKn3o
aJYEQcgr+hrDMJrLBJVs0GB9N3MQYcqCbbMQkm9o8Ntl+PTlI4xvH2O0qhbrp5X/f7z9Gcwc
lF9G52Zlp3Gxyk+jmdQ8jX+vw234fBkWtSxuii7pEX/OqwKNVa1BR7DdBz3+OgCcg6zFa25T
kgEXC7CvSbQA3sBDNAHZcoSCWCtKiWMRpsRzBSB4EXn8S9HG0FfrS371K/dYqXJlueOVz54l
rzwd3DgwdnTLHoGmVgE01+Y0x6+35DOkclVOCwyIN68ie2jpmi/xEm7ynJSiTpIUwEyp7QRI
Fmz+LW0fIR5VsYUpOEqFWfrFTd0MRfvZFpcb3Le6glAcNfDJRPBWyAdszxnay3iXUHdufN/d
l+d+Afi/7+7vZC7eLqA++dgASzE/Ba1MsV7d8lOyXd3e2RbZ/v6o8WxQBhuv23SJGGZJv5so
SEV3kjyPGRAphTFXUy63gOhterOPcNBX5II1t0RGFx0w7FqhiMIdxdFS8BnNOOmRzrSacuFa
jNqjAOJMQ9HUtBbOhsJQomkTX2HKXZswK8IQ7YjQ1GlQh9jjjwZ1CrA3WHMsD2arSCrlwmg5
FbTcFCLPvA352eV37dtJK5DDga6b9nif2NO7mKKu8ZyrgEjjQVtYOTHF1mSjzFqeNJjybV+m
wkqNTpCvLBPXELUmR1CHlowg6y3bSNdI4Ccc9rXpuf0+UQqY+7khR9Ha0NRI7Q7Bk9fE7j5R
ohOUixmQa1O19AjkVKvm/xB8AA3qK1OKvk9IxfksOqCuHP8D+nJIRLxiZp3Hi21ZtLxvK4cN
nrdYOYp5lUVhNQz1U7XNtot+ycR+w24zkzbaVmy0qELVpFv10VBBA/o8eOrz9L1hzzhPPYQy
H0AAOeR/REFLnGc+m/dE0d24mlKbol9v4AfcPLWauHGnJjZafFwdsyd/eFxF60nbsPUR7nn6
FDQUdN4EHRx8ePTaPZR3glYXXRLQPWjliytRPpRexn8CDADkYgKHDQplbmRzdHJlYW0NZW5k
b2JqDTI3IDAgb2JqPDwvTGVuZ3RoIDgwOS9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0K
SImUVktu4zAM3ecUuUAMyaJkGyiymlXX2Q26cNpkMfc/wOjDn0zHQQsYSCWREh8fH3n7PAU/
QPD+7M63P6e/H84BXC9pmMqv+zUNc/4RU/6ic97lv/H6dfs8Xcju4oe87cnajfVIsyv/hGwH
U/4iOZvIf4Sr66/hnTt74Mewva9W0dH/Ud6bv4TLoK/BpdBCKeeiLy5aWPxe4Adkawm92FXf
D+MbUouyunSHYScFq2tx4I6jHX6IT2aJwOKHBY5v0hiCCaE8p4axCgR1DWomDQHyw9izRmEq
JhVvzo1hQgzhJRMg4hvIK0jmfmpwEqyAtRrM5dTcIAl05LHPhDvHQ0vxjhBkFsCsIXp925ht
Qjk31/xgXE86F1KDpyIs3CyvItiZhvxMzKnllbqVL9iE7WdTI+U6odVOASApazZCYy+k10xQ
NRR1RBPWzeOACUeaENGBsJZLAJYNE5gjHBg8dyjegCRIFIWhGhik2BllHzCumZhu5aUrqHGb
1VVyt8v1wvJOQp2umIz596k98fYPtxDCixvKejmwr7Bpc5cSzWdfIQpnLprFxEdWk7Fq0mFA
hlkjE0U1STd2GN4xSghplJgTEzvpwaYEu8Hlc31dBaMAShSUDnfUU/Kka1qhy3VFNXXHcn8Q
x18obLKlqdFKctWvFDYu2In2SNkzQYuGrSulqB2QKvYS3mrw5VKr9fFo5xrnkazLgZ4vGsKd
CUC3bc4jypiuWWUT+mFBdkbSniBIEI39vBEh14XNXWSxHIJW5n02aiIME0pZp6jLOnv2YYgf
2IiwKHHpQGTfKURkgWPV2w4jqwHIE5pelng+abD6b+pSTOgxX+PJWd4nS2KUB/y+8fOlm2ob
Ow29EbnCh5aXmhISJ50My9PUiP1kGok3u6RmONcXrRZGRQITAs9eUUQShfFN51UDJKnDi0GJ
dOh3mhHcEav7cH84LsItSHvmUKcGbTQ4ll7LLV/UVYJRfbidLcTUYzFYJo6FXI1LI4UwyrkV
aRY0oYl/UU1yMnJn1nbk9tzneOTamc9h3kz1igSaaMESrTQ+0grXfjeOXL/O/wUYAJ3i1d4N
CmVuZHN0cmVhbQ1lbmRvYmoNMjggMCBvYmo8PC9MZW5ndGggOTg5L0ZpbHRlci9GbGF0ZURl
Y29kZT4+c3RyZWFtDQpIiYxXyW4kNwy911foB1ohqaVUgOFDJrnM1X0LfHB37AEG0zmM/x8I
tZBSLW0bjUIVRYmi+B5J9fn75NB6h2jAnP+a/nkACPHxFO3MX949RpvKEAszP6/5LYNB5vEX
8Avo8fn8ffr7PP3x7T2a67thqza5QIu+36//Tc6R9dGQW2zyhsiSQbIzmd+v09v053lKNiVP
7BGY9jnzVEOe1yVw5nybwPwozgKVfatHWaALgON3SG0Q9TiIxU26NI0jPYBOTjKkRjkceVXw
TeagyCooR2/Dr8dRY3cC1rn8En9znIYg8S8HBh3HJcYOhetQvMg+83hO2UndRt4T3vLKlcvi
bPFzd456QvXbe91VJ8+7uPD0siqKrL4Gf48lHSbvK5tybHx269/R9OVwTedXZlBIhUGLuY2E
WqL5tZG7PqAlP+irfFNzLLuyPngbfDfPYhzNr+SuV/Mr+abmxPzTdJwXi7NInA/BLslgiln6
LDFkTbKxZUanU2YQCgeQClwoMUaFH68cWUGRFHsUxmU9umyqPVkOJbF2GXYVM1lPba66cB23
REYeLyXlBlo0piqrgLYsffmIJEpc39OyZC+KrHRcMa5TKweUqUDRQsZO4stgZOhWomrdbL3v
2irexBSL4QuwM9J5NjgG9quwo7eJjmD3l55+sKpmWilKZQq7YA6R68WmzAUpPB+UzzjAuEel
FMQXMase8jPXihBgV28a7HDAW3EEO2dhw3Y4mDImAeqwH47QC/XIDFqiXXwBqqQ1LXMRHGPb
v9s4uVxRfo3CTS2wPH9ACORsDpz6S7KOvtYfGx8ALVBvkCewALM5XwsnqICYDyzZljs995xQ
0+qkVIBWt5vubr9yXKh8a1dlL6C82cNReX88/yw+ceVdmODa4uB13Wvv9bvMG83ioak0xpFb
9Y9Kq0rFe9cVzRG/9I6+499YiaC62Ka86JSRzqSZNHRn6ctDE22kylhHX7HOFBmwD0yRlaha
gsXOqaubfBNrWV6yOoCNg20W58H2KKq2217Jt2ZMTD99cE/DNHN5rDQ8vKPVy8mIDWyxObyl
bIe2VV4vHb3k3LsmbZuOj/Wpd5ehenXa9BLkW3OjUo62zY1ibqO5gQ4Ncd1AZVBtY61yvaV2
a6GXtG2X5aIFG1mmuLHKHay8SubxCZdWlS+lPWZirv4TPFQ1H59T+CSqE3JXA9Q03mKcs75c
fAWj0G+Vs1SYpukNAneE0PzbdbJ+38SvlZD+10A61Z5R/Tb7CRdajC9j64DGCVgNavDrATDs
NOM1RGAX5wNughVHH0joB8uQQZ9S+9n8L8AAu3LgUQ0KZW5kc3RyZWFtDWVuZG9iag0yOSAw
IG9iajw8L1N1YnR5cGUvVHlwZTAvRGVzY2VuZGFudEZvbnRzWzQzIDAgUl0vQmFzZUZvbnQv
SExGR0pKK1NpbVN1bi9Ub1VuaWNvZGUgMzIgMCBSL0VuY29kaW5nL0lkZW50aXR5LUgvVHlw
ZS9Gb250Pj4NZW5kb2JqDTMwIDAgb2JqPDwvU3VidHlwZS9UcnVlVHlwZS9Gb250RGVzY3Jp
cHRvciAzMyAwIFIvTGFzdENoYXIgMTIwL1dpZHRoc1syNTAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDMz
MyAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgMzMzIDAgMzMzIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgMCAwIDAgMCA1MDBdL0Jhc2VGb250L1RpbWVzTmV3Um9tYW5QUy1Cb2xk
TVQvRmlyc3RDaGFyIDMyL0VuY29kaW5nL1dpbkFuc2lFbmNvZGluZy9UeXBlL0ZvbnQ+Pg1l
bmRvYmoNMzEgMCBvYmo8PC9TdWJ0eXBlL1RydWVUeXBlL0ZvbnREZXNjcmlwdG9yIDM0IDAg
Ui9MYXN0Q2hhciAxNDgvV2lkdGhzWzI1MCAwIDAgMCAwIDAgMCAwIDMzMyAzMzMgMCAwIDI1
MCAzMzMgMjUwIDI3OCA1MDAgNTAwIDUwMCA1MDAgNTAwIDAgNTAwIDAgNTAwIDUwMCAyNzgg
MCAwIDAgMCAwIDAgMCA2NjcgNjY3IDcyMiA2MTEgMCAwIDAgMzMzIDAgMCAwIDg4OSAwIDAg
NTU2IDAgMCA1NTYgNjExIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDQ0NCA1MDAgNDQ0IDUw
MCA0NDQgMzMzIDUwMCA1MDAgMjc4IDAgNTAwIDI3OCA3NzggNTAwIDUwMCA1MDAgMCAzMzMg
Mzg5IDI3OCA1MDAgNTAwIDcyMiA1MDAgNTAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgNDQ0IDQ0NF0vQmFzZUZvbnQvVGltZXNOZXdSb21h
blBTTVQvRmlyc3RDaGFyIDMyL0VuY29kaW5nL1dpbkFuc2lFbmNvZGluZy9UeXBlL0ZvbnQ+
Pg1lbmRvYmoNMzIgMCBvYmo8PC9MZW5ndGggMjMyL0ZpbHRlci9GbGF0ZURlY29kZT4+c3Ry
ZWFtDQpIiVSQPU/EMAyG9/wKjyCGXKPTcUhVlsLQgQ/Rwp4mbi8STSI3HfrvSUI5xGBLfu0n
fmPetI+tsxH4G3ndYYTROkO4+JU0woCTdVAJMFbHvSpZzyoAT3C3LRHn1o0e6prx99RcIm1w
0/fi7nAL/JUMknVTUo7i4zMp3RrCF87oIhxASjA4Mt48q/CiZgRewD+x3wKCKHW17/YGl6A0
knITQl2dj0ZCLcSgJaAz//tM/FDDqC+K2O/0Sdw/SLZD9al5OkuW2H0qv5J/eHWlV6JkuJyh
2MqGrMPrpYIPeXcO9i3AALFIbpgKDQplbmRzdHJlYW0NZW5kb2JqDTMzIDAgb2JqPDwvU3Rl
bVYgMTM2L0ZvbnROYW1lL1RpbWVzTmV3Um9tYW5QUy1Cb2xkTVQvRm9udFN0cmV0Y2gvTm9y
bWFsL0ZvbnRXZWlnaHQgNzAwL0ZsYWdzIDM0L0Rlc2NlbnQgLTIxNi9Gb250QkJveFstNTU4
IC0zMDcgMjAwMCAxMDI2XS9Bc2NlbnQgODkxL0ZvbnRGYW1pbHkoVGltZXMgTmV3IFJvbWFu
KS9DYXBIZWlnaHQgNjU2L1hIZWlnaHQgLTU0Ni9UeXBlL0ZvbnREZXNjcmlwdG9yL0l0YWxp
Y0FuZ2xlIDA+Pg1lbmRvYmoNMzQgMCBvYmo8PC9TdGVtViA4Mi9Gb250TmFtZS9UaW1lc05l
d1JvbWFuUFNNVC9Gb250U3RyZXRjaC9Ob3JtYWwvRm9udFdlaWdodCA0MDAvRmxhZ3MgMzQv
RGVzY2VudCAtMjE2L0ZvbnRCQm94Wy01NjggLTMwNyAyMDAwIDEwMDddL0FzY2VudCA4OTEv
Rm9udEZhbWlseShUaW1lcyBOZXcgUm9tYW4pL0NhcEhlaWdodCA2NTYvWEhlaWdodCAtNTQ2
L1R5cGUvRm9udERlc2NyaXB0b3IvSXRhbGljQW5nbGUgMD4+DWVuZG9iag0zNSAwIG9iajw8
L0xlbmd0aCAxMTA3L0ZpbHRlci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIibSXTW8bNxCG7/sr
eNwtIIbfyy0CH/qBogYKFPDeBB9iWXGcSkphqU3y7/sOOZyVk7ow6vaQSO+SemfmGZJLz5ed
tzp4a5VR8w+d0cakqOZNt35tTIzGGHdhvY5Q4eYi6bE8bo8weD1fdj/O3drpnNUz/rs26rYL
Y9QhqNEEnYPadyE6bYJKU9Leqd0Xet/5hHhn41fdq++PSW2OCnnr7KOb5PO4OaCM4IL6qNYl
WsxeTw7RRjLZL3qiIDE7PUJZo22GstqJ2iDTrE1uGpmNSUfRUkdxElXibFqViSxT+W3V46TH
pNgpIUAkVeKw2nScB+tdx1my5grYqakaZ9PdfEN9TFT/v+lKnIJ2S1NijjrlpSmsMW6xHJbh
q7+nHtGzaYEep6yFeZwmIsW1shLmrIU5a8mSjERQECEeR6OTW4jHNGnrGvGYRsqkRalKiLMW
4qxb+tWpqRrnxcRDjIUREw5h1P6MOOt955KhFGX8CeQh5kcLPeBny0IPyZ4tdFYCnbVAZ90S
rU6Sdn600IN3vH2bxp4U7MFNBKvFqUqwsxbsrFsF1UlUifNi7H702uWFu/MT2rB7LHH4xKBT
ktEnoHt4Tm6B7scR0xp03/ZtKda3Xc4wfNvljMq3M4HTLE6iYl2vTZvcGsY60X5sTgYPc4PO
SqCzFuisWwXVSVSuC+WF0B12sT2Hbp124Yx61Vjs07gMPgXdWPJfoBtPO0PKCTo6gV7VAr3q
BXrVgrE4iSpxBLrzQduwQHdYkSk06I5eqaFBZyXQWQt01lwBO4kqcV4O3cXzI93i7Dw/YFjv
OxsNpSTjT2B3bjw/0x32qhwvDlt1OdNZCXTWAp21pDnpMzGen+kWR49diFucPfIOtXHUwrsK
wV2l0K6SE68mTZQABfV3c/dqnvFIzW87ZJFxOTKqfAl45YaEmwgIJePVjIWq5ofOqJ/w7xLT
3uMmYqlTVv2i8OyuXKrGcql6bXO4de5mczG/pxChhjDk4OosuYaFiX6xKjeyrOaP3bpX609D
1mNvr78dRm17NdDtCz6p+jgdJhyaYgEabGGNqxbzu+2wArRebT+dtg8D7jGxPwyr8vlmpw4f
brfHYZVpRnFfYVcYLIaVBT5sXFiXnGLxpm9+qtb3ZOzIDEd3r07v4EpZ3sNvpCfIOfa3/PRh
WHk8fDOscH/o3+IpXjT9qXoo+kXs9wP2f+q3dQ6m4tppJcDPv2Jy/2dgw2p/+FBHb+sH/5Qz
0I0Xt5Y7t0IUixdOw1Z7Zaiq/6hh7pkNs7FBDbY6XP0xRO37u7vt8aTAA+8ggEAv+t+owowK
SdTi70//3DPc8luGhjPcD2QCaAHGD1vqfOjVZsffwNzQwA7B+s+0WtCc33k29SogAVwDiTAG
mzrUGaeqqOWoFPjxFl8YfNkENMrS3x7/VxP8c3fNYuGydCHAoXbhiKLKaqTqP9MSdbzaC4Cv
W2CDJ2/1lwADAC47uDsNCmVuZHN0cmVhbQ1lbmRvYmoNMzYgMCBvYmo8PC9MZW5ndGggNzc4
L0ZpbHRlci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIiexVy3LTMBTd5yu0lBis6GXZyjAseCxg
xQzetV24idOEFIdJUsp/NB/MfchuymMGFkAXbKJI955zdR9HNtoYY0UznxjR3E7O5K5r96rU
tdz26/5KC3XRvJ1Mm8YJ8FpOnGh24FrUOnobRfNqYoChKpHhma3DwrnL+fPmA0ICQwxCHHuZ
ARESIgr8G2uOLM6+qFpXMlzMVKWtHEPHHFqHFB1TMJCiEltkiveqiMBwowoHy5UqrNF+XDu0
erlXcHsvD7hLUsxXYK4g4bYf/MHRejjhGxRBl8bXorC6ssHnDKwphwysCxz+TgG+Ambgq+Sq
462AbErZd6PRQHK3ytY6yK3C++6UxftulA0Q/qi8dlJkxy0firu8X/G+Y6dL3l1jxCi3c2T1
cnPkWE+RN+Q0DCXgsdrcglSNCSTLCezhqkmulcXK9HNkLWVHsfFklS3sJi6vcQuTAvOS5Fwl
+IUcPGCEKhB6LpW1cDpVFvwS2yJUFy57rth2JFwGrGHjB366dvME7rWgCDn6UjleCN7t8ko0
PTkeiEUsVYDss337UbmapooC3bHPivwZK7BFaDvc5nICNAHD5rSALg0TYJw70Q2kitE40xgg
O9weNSwno/yNipz20aQ/oqLyF1SEOD9OgSmzimyiiXUa+2WlwYpFqaFU8f5w6sgpqAKnUqz3
osVCQ+v772XjbH2vWjuq1nG8N6rwUP93LM/PQEnt2MGcWKghdAXy+UQqxXaScwcqtiVa+2w4
tKrg5gMNTpIl9RQ8FkxJV94uAVGPA/agrXTDcNJWR9nX0liK5+Xs1QuF4HrYW3ZwjteZD/wn
LzPKIsmXhMpsMzegZ9MU+Uzjo2V/Jlb8l9tUV8NjZ3G2bhS+cKD3iA9dQMGiIYKKYJQFjH0J
L0WLfSrlpuMa7LJPu2AkqgirhhjRtfcEaxSrBUp8pRK+SpGeLf+j6pEoypPq3SjsaL8A+gA9
3Ct6AVtFz2y/0KSRfyCO+Ig/MVkr/z8xf+0T82CGH9XH5qSUv/uxed1MxFcBBgDbNyFRDQpl
bmRzdHJlYW0NZW5kb2JqDTM3IDAgb2JqPDwvTGVuZ3RoIDI1NzUvRmlsdGVyL0ZsYXRlRGVj
b2RlL04gMy9BbHRlcm5hdGUvRGV2aWNlUkdCPj5zdHJlYW0NCkiJnJZ5VFN3Fsd/b8mekJWw
w2MNW4CwBpA1bGGRHQRRCEkIARJCSNgFQUQFFEVEhKqVMtZtdEZPRZ0urmOtDtZ96tID9TDq
6Di0FteOnRc4R51OZ6bT7x/v9zn3d+/v3d+9953zAKAnpaq11TALAI3WoM9KjMUWFRRipAkA
AwogAhEAMnmtLi07IQfgksZLsFrcCfyLnl4HkGm9IkzKwDDw/4kt1+kNAEAZOAcolLVynDtx
rqo36Ez2GZx5pZUmhlET6/EEcbY0sWqeved85jnaxAqNVoGzKWedQqMw8WmcV9cZlTgjqTh3
1amV9ThfxdmlyqhR4/zcFKtRymoBQOkmu0EpL8fZD2e6PidLgvMCAMh01Ttc+g4blA0G06Uk
1bpGvVpVbsDc5R6YKDRUjCUp66uUBoMwQyavlOkVmKRao5NpGwGYv/OcOKbaYniRg0WhwcFC
fx/RO4X6r5u/UKbeztOTzLmeQfwLb20/51c9CoB4Fq/N+re20i0AjK8EwPLmW5vL+wAw8b4d
vvjOffimeSk3GHRhvr719fU+aqXcx1TQN/qfDr9A77zPx3Tcm/JgccoymbHKgJnqJq+uqjbq
sVqdTK7EhD8d4l8d+PN5eGcpy5R6pRaPyMOnTK1V4e3WKtQGdbUWU2v/UxN/ZdhPND/XuLhj
rwGv2AewLvIA8rcLAOXSAFK0Dd+B3vQtlZIHMvA13+He/NzPCfr3U+E+06NWrZqLk2TlYHKj
vm5+z/RZAgKgAibgAStgD5yBOxACfxACwkE0iAfJIB3kgAKwFMhBOdAAPagHLaAddIEesB5s
AsNgOxgDu8F+cBCMg4/BCfBHcB58Ca6BW2ASTIOHYAY8Ba8gCCJBDIgLWUEOkCvkBflDYigS
iodSoSyoACqBVJAWMkIt0AqoB+qHhqEd0G7o99BR6AR0DroEfQVNQQ+g76CXMALTYR5sB7vB
vrAYjoFT4Bx4CayCa+AmuBNeBw/Bo/A++DB8Aj4PX4Mn4YfwLAIQGsJHHBEhIkYkSDpSiJQh
eqQV6UYGkVFkP3IMOYtcQSaRR8gLlIhyUQwVouFoEpqLytEatBXtRYfRXehh9DR6BZ1CZ9DX
BAbBluBFCCNICYsIKkI9oYswSNhJ+IhwhnCNME14SiQS+UQBMYSYRCwgVhCbib3ErcQDxOPE
S8S7xFkSiWRF8iJFkNJJMpKB1EXaQtpH+ox0mTRNek6mkR3I/uQEciFZS+4gD5L3kD8lXybf
I7+isCiulDBKOkVBaaT0UcYoxygXKdOUV1Q2VUCNoOZQK6jt1CHqfuoZ6m3qExqN5kQLpWXS
1LTltCHa72if06ZoL+gcuiddQi+iG+nr6B/Sj9O/oj9hMBhujGhGIcPAWMfYzTjF+Jrx3Ixr
5mMmNVOYtZmNmB02u2z2mElhujJjmEuZTcxB5iHmReYjFoXlxpKwZKxW1gjrKOsGa5bNZYvY
6WwNu5e9h32OfZ9D4rhx4jkKTifnA84pzl0uwnXmSrhy7gruGPcMd5pH5Al4Ul4Fr4f3W94E
b8acYx5onmfeYD5i/on5JB/hu/Gl/Cp+H/8g/zr/pYWdRYyF0mKNxX6LyxbPLG0soy2Vlt2W
ByyvWb60wqzirSqtNliNW92xRq09rTOt6623WZ+xfmTDswm3kdt02xy0uWkL23raZtk2235g
e8F21s7eLtFOZ7fF7pTdI3u+fbR9hf2A/af2Dxy4DpEOaocBh88c/oqZYzFYFTaEncZmHG0d
kxyNjjscJxxfOQmccp06nA443XGmOoudy5wHnE86z7g4uKS5tLjsdbnpSnEVu5a7bnY96/rM
TeCW77bKbdztvsBSIBU0CfYKbrsz3KPca9xH3a96ED3EHpUeWz2+9IQ9gzzLPUc8L3rBXsFe
aq+tXpe8Cd6h3lrvUe8bQrowRlgn3Cuc8uH7pPp0+Iz7PPZ18S303eB71ve1X5Bfld+Y3y0R
R5Qs6hAdE33n7+kv9x/xvxrACEgIaAs4EvBtoFegMnBb4J+DuEFpQauCTgb9IzgkWB+8P/hB
iEtISch7ITfEPHGGuFf8eSghNDa0LfTj0BdhwWGGsINhfw8XhleG7wm/v0CwQLlgbMHdCKcI
WcSOiMlILLIk8v3IySjHKFnUaNQ30c7Riuid0fdiPGIqYvbFPI71i9XHfhT7TBImWSY5HofE
JcZ1x03Ec+Jz44fjv05wSlAl7E2YSQxKbE48nkRISknakHRDaieVS3dLZ5JDkpcln06hp2Sn
DKd8k+qZqk89lganJadtTLu90HWhduF4OkiXpm9Mv5MhyKjJ+EMmMTMjcyTzL1mirJass9nc
7OLsPdlPc2Jz+nJu5brnGnNP5jHzivJ25z3Lj8vvz59c5Lto2aLzBdYF6oIjhaTCvMKdhbOL
4xdvWjxdFFTUVXR9iWBJw5JzS62XVi39pJhZLCs+VEIoyS/ZU/KDLF02KpstlZa+Vzojl8g3
yx8qohUDigfKCGW/8l5ZRFl/2X1VhGqj6kF5VPlg+SO1RD2s/rYiqWJ7xbPK9MoPK3+syq86
oCFrSjRHtRxtpfZ0tX11Q/UlnZeuSzdZE1azqWZGn6LfWQvVLqk9YuDhP1MXjO7Glcapusi6
kbrn9Xn1hxrYDdqGC42ejWsa7zUlNP2mGW2WN59scWxpb5laFrNsRyvUWtp6ss25rbNtenni
8l3t1PbK9j91+HX0d3y/In/FsU67zuWdd1cmrtzbZdal77qxKnzV9tXoavXqiTUBa7ased2t
6P6ix69nsOeHXnnvF2tFa4fW/riubN1EX3DftvXE9dr11zdEbdjVz+5v6r+7MW3j4QFsoHvg
+03Fm84NBg5u30zdbNw8OZT6TwCkAVv+mLiZJJmQmfyaaJrVm0Kbr5wcnImc951kndKeQJ6u
nx2fi5/6oGmg2KFHobaiJqKWowajdqPmpFakx6U4pammGqaLpv2nbqfgqFKoxKk3qamqHKqP
qwKrdavprFys0K1ErbiuLa6hrxavi7AAsHWw6rFgsdayS7LCszizrrQltJy1E7WKtgG2ebbw
t2i34LhZuNG5SrnCuju6tbsuu6e8IbybvRW9j74KvoS+/796v/XAcMDswWfB48JfwtvDWMPU
xFHEzsVLxcjGRsbDx0HHv8g9yLzJOsm5yjjKt8s2y7bMNcy1zTXNtc42zrbPN8+40DnQutE8
0b7SP9LB00TTxtRJ1MvVTtXR1lXW2Ndc1+DYZNjo2WzZ8dp22vvbgNwF3IrdEN2W3hzeot8p
36/gNuC94UThzOJT4tvjY+Pr5HPk/OWE5g3mlucf56noMui86Ubp0Opb6uXrcOv77IbtEe2c
7ijutO9A78zwWPDl8XLx//KM8xnzp/Q09ML1UPXe9m32+/eK+Bn4qPk4+cf6V/rn+3f8B/yY
/Sn9uv5L/tz/bf//AgwA94Tz+woNCmVuZHN0cmVhbQ1lbmRvYmoNMzggMCBvYmo8PC9MZW5n
dGggMjUwMTEvRmlsdGVyL0ZsYXRlRGVjb2RlL0xlbmd0aDEgMTcyNTA0Pj5zdHJlYW0NCkiJ
vFdLbJxJEa5/3uN5e96e2B7HE9uJZ/z2bOy8nPgRJ9nEYbNhE7RAzG4eEgmYVbSEPUVcOCGt
BNrbkiBx4ADSLFxyQIC47IoLRy5Bi8QF7QFxRFokUzX/V/krP3biQGCkr6v/6u7q6up69JBD
RAm6T0Ga2rg0OXPpH+9/izm/YnzxrXfv1ukv9CmRU+Dvn9zYunnnF2f+cJW/HxEFvn7z9ndu
bNz+PEbO6kWiSv3W9c23f/e9wBsU+PFDnt++xQznTxc/IQo1+Ltx687de5+MrP2cv9fJOfHT
2998azP63XN/JefLW/z9szub97Zevxqs8vr7PL/+jc0719+b+PUvKfDhPl7zta13rm/9/p25
z8hZ/jvrcI0cuu+8T2Gee59kxZugjylFp2JOIBGJRwPhWCD0kAK/ufXxPz/nsSyDXjuzvEFL
VN/+Gz3eftxd0VgievDpH2WUHPrPfnkSOxWoyG2JytyWqdLdM8dtjnq5TbJuRGnKcBulGLdx
6nnSGgnb212ZCV6Bvm071Byqr3bq127UO/T6laHOiVrH2bx6faXVcZqPKLA6vHZtvdUJcD+4
erjVCXInBmaI+3FhhrkTBjPC/Ygwo9xJgBnjflKYce6UwezhfkWYCe4UwExyvyjMFHf6wExz
vybMDHfSYGa5nxFmjjs5MHu53yvMfLPjlHLzrU6h6WR/2+oUmySk1HTqueF679rw2uUrC7Wh
q61OuUl+VqVZXxOTdOqbLLPqft10v/qa9U5lvFPnPWrcrY4/2v4z9/c167TgLLQ6/c2hVmeg
+ZGzb3Xlo0A/N8EBbkKD3ITr3ESGuInu5yY2zE28wU3PAW4SI9wkR7lJjXGTPshN5hA32XFu
ck1uelvc5Ce4KUxyU5zipjTNTXmGm8osN9U5bvrmuam1V/kWB1mVV0SVw6LKgqiyKKocEVWO
iirHRJXjosoJUWVJVDkpqpwSVZZFlRVRZVVUWRNVTosq66LKGVHlrKhyTlR5VVQ5L6pcEFU2
RJWLosoXWBU3Hrpx4rjRse2PkI3PmPF2t3u/ixlGihEBjQIlxhH0wxgvgRbBizGqjCQjgW+h
aUYWfZE5C8SxPmb2DGF9D2gGY/o9B3lJw9e90qB2fRK6BUDDGJsFL4U95OxDRm4C81LmPCJ/
HueW87Shb8bMlTPVDC8NGgCNY94i1mfN/tPG3qpzge/nAuM18PvMHIVcaoqxn/vDjEPc/5LI
ZbomMoCDjHGsUT3i0Cu0C4IYz/gg8iYYeUa/mRfzg3U4Zu7FImzucjeEyfMbixrOo/vrPfb4
wfsP48xpH6wN1O/8VP1rN5qEbGun1B7oXuSmIVd9J4/7F2TxLfEwb2gPbJPGeBJzs9h3ArS9
A5V9BrF/ZgcaNfcfM/dtqfpuEnpY2mtstBu1sWupxlJyjzRAXszHyYv71A5U5jvsJyOMUxJr
jDcYo4zjjDnG8jPoPOgx4zdB8nJi1NgnQ14uDJEXw+rvwssZGSnD1/yhedLGY53Rwj2KnSVH
TeFsmvdkH8fco8a96pgDZI/9BnHy8lQGeqlfBsnLcUHMVV/RmAhjH52n50iSl390f435jJmn
OU/XhIxMzVGCPM6u8SHxMEpu3RJZFXL9fwK8WfT7IUfmax2Mmr6MSR6ewj2/ymgyzuJ7kTHJ
eJexhL740oL4BL4nMHcZfPGdMVAZm4IeWltz0EHybJTHD0POEmSeYLThrycZVzCnDXlHGbOY
J1R8I4bx85Alex9kjAvVvcjLabLvadyzjokd56Brmry8StC5e8+Qr+c9C3sIDWNsERDdD2B8
0Ywtw95iq1eMrXRNETWvn3EI8+WcZZzxDGMFtfMS4nhNagHoWWADNj1u1ujYCnirjEEzdhH6
jCH2F7DHaXzL/DXYpA92ycC/+hGbUfiozNEapLGqsRM0sRnCnBh59UpjV2PM8m1d1/XqWxHy
8qrup1TrTwT6ybwi4kprjMZiBjEVhq4OPf1mS4MGcU7NyVnIy4BqfVc5tgYq377hdI7mzixs
nDa2TuPMAUNHjH1y5L0leo0Mf/3XPK5nsvGRNPL07HofachVulu91Pv0U3smW8/80Ht3H/aG
vgh4zVeZDuDeaz55H0u8keu3Je5/gG95VxURT+LvksMmyX13SuyK77ees2/XBxG3ZZxpyJw5
Czv18ngFOmrcaO7XejgAe0guK0O/QdAR8A+gb+vbGHh1zD2I78YLro+QF3daQ9Q/rA9rfMeM
DaLmTm2Mp8irs37fU3laeyW/J8x4gry4c8iLKUGE51r99D1k/1d06y3PGyWv3gu/aO4nDiq+
qjVC37n67tqJqq203631vNdXkIuHGAXUBfGnhNiJkUfOzzHiyLmzqH11xl3Hfbu1kYul/kmt
7oO8Gcetn1Lzao5bs9dQA/Zhj8OgcvbL2P8ybFAg712id60+GCEvP1XxXTXjyo+CFsy9Bs1a
oXnI7wWtGH/S92QUcv1UYnDA8KbNd8ynq5WpcfRUzUCsh5j2kufH1q91vp6lCn31/MrTvf36
i60l1uTO5W1yBL7atQd/D0iNx3y5kyb6MqcBX5Q7ktjUuNOaloD9JI6n5U51HD5Rwv0OGnsc
FR9m3lXsdwBoo9bLO6AK3U6RFxslyCjgnSF5Q3Jiync/3f9ysKvyZ3DnL4KIH7CjyozuNGeX
dSPGxk/WIw6H9W4RY4Pk+be++Z9F7Rtda5z1+6iR32BMm/3ljTVuzrPTuVLk05s8X38e/HLT
Zm+xxzwg/KyhDnzNAew5E/R0TrB6lXy+IPvYONI3mti3DZ7/XP6+jd+wb47aXOcFDf7N/r61
dr2dZ8/X3sF+8v4XGy2QmzciLxnRlwz5rzSBOiH/JVqA1JVJ9LN7ROx/oN9u2IutQi8BL/v+
ngUC3mNsIdYES4zDJm673zIPfOlvOfTU25L2Mu6f45/vX+Nb/1K/d+rvBt8ctQ8hXx0lL3fZ
eS/K3wuO+fr63owa3RQEPa2+fvrfQORqnguBd89x67f+rxBorffn0iag74g6oDWhwpDaq36p
7+kKIHk7aeZlAPXbpIHkCvn/9NT7wHHfBd13luO+WfXttxPSOLP/bRA1Nt9traDxnHHNM/L+
lrwuZ5O30SiovJ3WHTdHCq/quO/zC4yTGBfsx1n2YzwFefKGP4f+OdhN/gvWQeWdJO+tVcfN
x0rz2EvecPI+lPeLvBVKQHmXvv98sv8ZyBWdm/huQOac4/4vkP8K09iviO8h7JkDvx+0jH4R
a6vQuQ9+uI71Mm8efNnnNHxW/weqDz/hiTymRcztzuH+m0xlnwnYOg37JmDvYZxFatmS2bsA
e+sdHYS+I9BzAXqPgTcCWedVX8ibAb+B/RQN3KPFgKElyK5Dtq6b8u03grMJWjjHENYdwJwW
1s2ADgPjpi/6jPogsr/NuMG45Lj/HS9DzhzOvw5b5LG3+sb/sy5a5HFXdehYAq+E+5R+H8b7
gLyBnLN/h7uZA+R8VdyN+kURtq6BV4OMKmT2ghJ4glOO64P9uDvxrR84rt99H3Ie4vsDx/XZ
H+Fb9l5kfIjvH0L+A+z1wJxTZEkca26SN8tJYAk4CV1COKP1jRPgiQ8NOq7/CM0B6ovHIWcU
66aAJrAM6FswDag9ysAgMI77qpg56uea14rQuwg7KvoM0gYpAzt/ADzNh2M4Rx7jUovaOFcb
55RY7MHcQbNe9mnANnNG9xXYegx6NcGfhtxJx/O7jOP5XdHxcuU+x8vVY//ivVx6JDmKAKyQ
Z6a7uvr9mumdnV3G2BZehOSbJQuJg4+IKxcOwJUr/1/CqY1P+VW41jLI+JCqrMzIeD+j++Au
ehyfc+HP6B+93vJ9o/uaCx7/+cP6e3z0oedc1+TDuvtO6/dal0+sW8IeU2/Npl/m/1fJ5/fR
46vpqflI872WY75NWbdp7xZzH5L3b/LuVffNnv9KHK1Xbfnp15o7fsn5hN7iU+u/zY33/8Ob
n1rNtuvkZRm9D9rnfhN95lv+wrR/7dXk3En35LHHlLP58CHhiD3yvnMP+jrkf8MxSFfrfLdN
3Ls8WwsXOm7/zf//kLBvE9cqcS3zfTtrMfGathgT5prfY/KDzY75DjvWHHpKfng7JO3XPKcP
3Cce5Gr3X+R/e9tyAXmGfv/n+NPPWXczayPdYAN0e9DZXcrV6N7L1nvZkEX+vU/dYifX3Iek
eS/dbxOOtxud4yuv0WvlJvXFP7zikw8JM+TCXvfidS9aJ9Fp55+J3432C/E2JJ1Btrnl93f5
hjre/KHl6eZj3ySOS3SfRIZjroek8Rj/Xx/4qUXdfIre35zy/JJfzrD9IeGZazd5ZjsSX+xZ
Dc+/U7ZWP1udfU7Yc/6/pg6/lb3P+f1j9F6IM2aXm/jFxvg7+aWdNZ/6LvfwtY8ei2vZGNnq
HLVOff8tPvYgxD53J+G+RPc/9ym7mPoj8cie97bJXvDIytrGNG/C4yq6Hx3yDFnWZY98jmVw
jtID/yxi7yl6vEO3wo6F1mLmbi084K8wxj/M3PMlfhfRa8scP+Z7mMG9mYGva6U3wwycz9AZ
76x7v7kr/5tCx3qqvCwL7bnzXcG9KPbb6N29zshLq3LmHm5RdElfNOTXOp3jv+6rrwwx1Rex
UWGhZzjrcixf7ERvsdC59bPUm0X59zlxPWffhejc6Z1pWM/UOttoKbzAIx/x5Hr2KZ2bl6o3
18Fqh+pTtvOcPUfBL8q/aVcb2y41toz/s3JnmcFFLpiLnarvKgs9cju7n9HLstCyTfbCuSx3
1qF5gP9VkcXn1Qbmy2dzvHFnnbb7u/I/JyNzln3Ecq30fSgwhvWd9yxmyDpf0VfQr7b/1j9Q
a+nZiT96dBb95TFxHvI9eZEaTF8IjncJc40fzwvUe2httIjHl/jY+7B/F70uPgvXm/x/Hx97
l/fR6/Yt6ZumZ6Vr9DnN9+39X0TDOnGtpxfZlfWgPbS3+nfvUN/uChy+tcpzeqO18NB3DDpf
Cw5emw6fUme31NvboqsG89foPZZrF3o6Sx56CHQF//SUK53xT9+J/lbCbTj7w0n7Q3S/bP/0
kPuiW/b4Hv4InTGmtWIVvYdEXve6C+E6S9/2e/cs5GJmnJ3owBf1kvxCHQLuWTock3/nIfsW
MQoPN+lrLTyu77focwj2RHZ4WCcfO/GL3uhT0N1FdmH+JE8fRXuQvrbR/XoZU3s4Px5Fayl4
ZhjmDHKS5wHbfF9oI5fz1Flw2LrFykva4CnpXfK/6fGNzl9yXfL8ov+L8Lzkm2vy/CbP3iZf
l/w+5fkpbXGW7R2XyN/272PqG85F9tt/5P2H/L6LPkN+Hz2H4AsvMZ2NrDfqt/MQ9KgxruGu
CVvB48PsiY9FOcevic+l7qlXZ+kL/TwVPplJybHoddR7+wQ2WUWvddTix+jx0WC/jh5bj7lO
qcdG85Znrkft+yZ6HL4kzJj0gP1N8uV6/WWevSuy3GRX15HHvAP2IhjO2BM36OIcPfYeUyfo
nJr6ld7yjhy9jR5Pp+h+fJLOH/O7Lv/AEet+gx0v0X3/LNnOOj/G1MYX0SJvAXMoNNiTg/bl
/iA8pnESLfqxbYF5U2Db/XNMYxy77Mpb6F4T/hrT3g/594KtX2hgR+uPmnueWVWvNQbpvexD
tmXVk/2G2DsUetaX7QHf6J9+zbSNi3y7mbnDz9bl7SamfvUpneCj9hVivcpL3V7N2MBxYvnn
/Mw+gp/YlsSH9XwRPH6H3m0LZLbvOVYsD3MD8q5jmlPIv/UM3HP2No+nsqrs6GsjWnP64Zzc
zdrM4IYveIPXo86JVet/L7ovMZWd/rfaeyc4z2L0Usxo7r3d79hnB+GiTg3RfZK+8Dl6X8O+
nrfvW9219VT+3wr2qv2t4LmWtxft7a8n3V9nYMkt/sdXbRv8jN5wiOksanjmK3yXnuNY3mA7
+/la92u9oa5y5z70EL1HJt951gSG2Byj5wzeDtF7f8fwIFjPbRu9oY+jZ9oLhtnB8xV3C8mM
T3nWYjZCpqHQ8dzqXnDQe/h0L+l+tu3dB26FzzMkMQF+YniIqYzgOeh/Jbih6I+35s363gmH
ed6L1jmmuhp1hh7ck0PzEPM6sizonBwMLsP7zr40Rq95o3Cyv+jNSnfsyT+eG9DPSt+V7uEd
njcxnUF3wg8Me9PHzvA2zNActHftIH7oo8iz1EL0MkbP18xvl5jWIPzoGH2egkZ7/77olrxD
zianO6dcotdM5xTvWfuU7yhZsadnOnhATs9s1A5iuP0/yJ5j2RPXtik22+gOW+FjzjO8cd6l
HlbcfmsfQncH7StP1Oiqt6pD66vqufJhPdlvvZCp1gvrZox5vWyEx/7KnvxDbh30X/O+ZYSn
g+A2Bc52PsSP5R9iWifJZ45j+yW5kC/nm4ITnVe+B9FBT1VXrvWu586l+Ib9k/zxqDNiZxfT
/FTrB3pZCY/rn3M2586R0F+Ue9dh28T5jbzomuoc03hvue1D9L7T8w59hfsby4+fOq5G4VhG
7w8u0fucjfaX1OtT9Nn1MboPuBcD7yn/gd3KNry9Rp896Lluwouf7PPNo/53wuu+fy/4a9E7
c0btS9AX+Qr8J+Fjf42pT1E3yV3V5jvBYl/ng41ssNY98Qov1Df0fUy71HzGv33U/SnyYMuG
5zWmvn6QLgZ9qTOH/ML3Mu+XqSd8zf2nZUdHNX86rzgnrQVXY9g625YFzNcxrem3vLtFnwfq
bHvKd551zb91+qbYjfxHf3GJqS4qTvg8irb15L6lvXmfOD3HrgVz0hlx1WCfo+cL9/T0EJ6N
7Adt/xTTeDF/R52RR6glht/FNN5cX2sfzvzomaPiukT3EWTclzc1/hwDtS+5RI8rz3O7T/x7
D133/dUW1onnCvu5ezJwrVP/++g5Dtz4Dfsv8x0wLbZ/88P6Ktcy4R5Fb5tw1ket3TW2oI8P
N1yfR/f3d2lDeDaf7mGQ9Sh88F5rG/oC30rybHXPHhqjcJ71Bvnc15DTzzHNBa5Dzv3Vp+AB
f3YN3ujcs1/tYT1PuRdwHNT8uC74PDvM9cmL8o+vkdftp+5R6JEWul/EtIa1/UMubHuIqQz4
AzZC586TrpOP0esVMYrP/zY++vjbfN/yxrXgPiQO50zy3UH/1HFiwP0TudB9AfXVb+1/2AAY
8gb9NTnh8/hxbiGusEF780X0uFmKB3px7Og4gt6HmPr5vnxH7R0Xcz7sftjy2kc9G+A75CbP
dbW/r/SJc2Ch02g3H1tEn1npxf4s/R3yfhHd52yPMbo/H6LnF8fHOXrMODZG0V7ozvej3q10
tpBOfQa/9N6rmMYrtcU9GXMrMtK3oT/rgV7NeWpR5PMcgt3gzznMMwXyugd0PzOKDnMtNnVf
tRJd+4BpjSmneWvrLrpfgZOZbJyB99zmuvspm+I7zq/gtZ+RL8B11X5V3q20X0r31C7msEXS
d/7dal+/q+j5Ev6YPx8ks/sM7AgP2BEfY++Z0jgsF3ZAJ9ap/4l1eiV8dBtT/xt0D28Pom06
dTmHL3W+jamd0C/xwVxEfQNXrYPQ3iVPtaba1oPwIgs8uP/i7hzTOWqZ8Nbhofx7Wb5tgak9
mH3RuluXM3TjM96fpI9BcNWW+C7LeWiv94uy3MMwe+4LbteQnd4SD55PqV/kS/ehrsPUBmTd
6M55/i6meQT5sTcxTr9Te9zaa7tPgI8/iee68B/3Ua6zc32h5zL3/LUer3XH2ouWF3KhB8tJ
HjIeaICz4ttF793xScfySTgszxjT2Kn9smXwrOi4t57ce61iqhP2nnXZnwoM8QDto96chBM5
6M1r/aAndY7iix+4l5vT51LvD9qTW9AJbzjb6N+6qbMuZ+BZC5drjv2j1lf3B85vps1b8rx5
5N+9t+3BOfjoNdz34mvAO7e5bzKfleay4HMuRU/2v/8wXi5LjhtHFI2MGbJJACRIkOyeUdiS
LMljRWgn7/QD3vn/P8eDEE7g4LJ6rEUFCvXIzMrnTfdf/NtezNFfF/u2b+qja6z7vP/7epbJ
Oa1r8CRGnJ8PMY4NnsnbPSm69Dq+An/w8aHBM2uE9YgdX2org+1jTOB8afsYK3VB2zo6igaY
3djBciYWdZ0eRd/+2Ys2+0fdhyf1Gj9zjDmnuodxLOQdnycujKm461wNRvtUa04jlr6rNUfA
E7mxNbITY5bT/eop1tO27v1SxwzXfTCB8So4ApxA7nWPMf/vvo630MWwrPWiRS6nt6NWnJaz
WYNcE6/ijV5d+3hrp/kp7tivTJ8YAbfMb/t9+f/ydfxT+nKNHhe9fVnkuy3jbVmnbs3jIX3O
89fl/4ev43P96Rtgs8cyhuXco1Y/whY+96gtvp75f9L6TXNkIrc/aq011KaH3mt535Zz5nsS
Da99r7uP2soAjuAdzMG1N9HJd+Ibk3gP0h+6noI/MnAPPxzEn3fCs9c9xj1owQN6yAi9TncH
nWWfuJpqq89J74HvWTSnWv1pFA/TBI+RD5D5l1r9A7mReVx0APb5sbZYlXwzx8vnWuv1fHZf
a/0wZh0W+e/ac/2715rDyCuXWv3xUts86T4SDP5ej+d+EZqZPznjvO6aQxy4R+xrm8fJ2+hz
FH3XQOMp9xWZ54+NdeMw71FXjXHN+xL0JvHBP41frGd619SpdTdooGNi+Rr3jDWNEbxv3Oqa
yP71/+jnqDV0wVuM4YwzTe+9N+ea8azrKzYxRttLRtvJPnGuZ93mGxPn2f89diFD+pr1SVza
94/1LEvf2O+CxynWHZOj7qfNrMOraA614thp0WPL9sxfautXH8N+xC50GMZKjj/75m65l30s
Z21j/MAYKzGj8a19v2Uny+D38ua8Az9kwr6MjLmWv/O+F90bxcN43Pc+xv+xtv71+s5beU+r
Z+nE37LiH/ugk3HtWLCvXZb7H6TfR8hnO7P2Qf+OXc6exSvzAf6xqzWebctjbeMaf3XOwQfd
19L7OB7Zc55xbGFX3v9Szzr0nfQX5j7XBY9R//hk5hjyFTpDj/j7KBk78TRdxjn+P4oucW99
knPQfb7V8YK/efCGg/h0DR4vQdv6mmqr59b7xnqWDRsdgg9v7aW3Q+gTPtC5BM2WPpwLnCtf
Yg7ORm5wa+YX+hpsQP/lHEp+HnSPmKaeQscxbzkdO8TcbXkzeAK8jX7O+jpXv9W2hiMbMXjW
QGbXRdYcw+QQ18ZWPLI/aH6sFfu36g19rWPLOAi8Zhx3jnuXWvuDeYD9E7fYnsg3350xBvnO
tce26WrtE2Ydv9bqF9gGbD3W2he0xkzvv7XFv+xh99da+yjb232XaRrT+h9ZwP6nxj3ueO+i
tUFr57jbki3f7p7PtrrWs25uCz3vneOLzS+11cUteOFvpj3Vs2yWkX8w0L1hA2T3+XOsMwcv
DuLDnUuDf1/Pcp2C9rm277TNiCnblDhwv4G89I5X0eTuEPx7rffB+ywayDrovN960dpFtOF1
i3uT9tER/MmHJw3OWk/Ow95jnzzu2Pc7yRWcOdU2phwv5Cf0N0g35j3U6rM33edNlvcmfSIL
POFjncCnr60djX+62uZJ25C3IwN0sqb47qm2siDvVFv7WC/29Vut9WKq1UfBgugUftaZ49C9
Teoi/cQ2vlTbl3rtud64/kOLWoU+0reZP6Rfzve19UvbLe2X++d6fme+Jd/U8s1J6+hwCH7O
K8SmsUjKBZZoydN6o3XgfEju7uM+PkKttz1afMByx3qODfinz7o2Wlf4zynWW295ke6tL+Oq
9/SCHTJHcI+3M2/ZzfMuvhmX7guHoPEt3Os96+dFNI7Bdwz+9s1WXnE+Mk3sOdds8Ca2JldQ
P6daazt75BswdOIS6prjjDXnO3K67z+Cd/q06yhyTLHO9y6eLbx1k/z3oHkK3kODBnr3O+xn
Ka9j0LnkJBqccR9wEz1jH/K96ykyTLX2pG+StYW9+8YXTOZ3GMsgJ71Ipz3rwvFIzaU+dZLN
/u7+wjkAWtQEhv3KOcL5O3PYRfeIHcfAWTaAP7UWG/xbe5kDeRdvN5bwoNfF52c//EPvv9ea
W5iDX8llo+gNQT/ziPfoncC1yOg8j+9jk6N0/h/pCj90LnKOzLzo3OTc6T370TnOZP6zHd2T
8m3hVefle+x1OnOKdctrffvcRTSge6g1n5D/Tcfy8B7HEHfO9W39HeKea73f/SK78rb9su5a
cZceyE33hh7zLca7WZ9tP+LJ2AwMSZ681rNfJe3sxZzDEze1zjKcf87x5UzmE9b8Ltsn+SeW
cJ/b2kv9nWO0sNB7I2Mx8cMUvPI+eZB8kFjH+TpjyLnlKv3sl8H+vp7fbL1zp5V7fW/fGLbP
Xvy64L0XT3zUMTQP8BoxeNLcOIg9coBz+Hs5hPx7rTVnOHcQE/tlTg0BTzyku71kYvxUq2/9
tJyfvz9/Hf/6On5Z/l8lJ/hsHnMO+PvypRf9UmsdAzciW18r5pzPfq4VC9xE03jROeXHZZ89
sOkg+uj2FnSgDZ9pmd81XkUTHAA+JG6xJ/5r//P8PVyQ+dzrzkmJ27+V99wTHeOsadjfWvki
+7PkP4pH62wftPMM8WJefzVnIb/7l5TZb+/jTvJxTiY2fKaFW/JexjzxjRzOVdRk7yGnsZVz
ALb+tf70td8WG7wuZ+b4wVdPtcbG7N9vtdZtr5MbuAuuJBaIV2JiijViHzmJX/oAckyrPmVs
gGNc94nllq+ftWb7H2Lvd8lPvSKv3GPvtdb+z+OqM59rqw/nC+e6T7Xmnovu33Q++VgW5g/d
4Z1X0Zi+QYeRuY21lNk8T3+BdtYf66o1PjXO0JO+J2uLHnqlH7HvXuIffZ61T683z8EB0MNe
jmWwseszPn6tba/qXm6+N8Z5Yp/8AAaBD5ibHLBbaPjubjl3EJ+XWjEMNA61xTmmv1/o53no
8I6j6ICVd5LFdA4h20775IMXjf1CD/ksb2scxMs8GV2DBjw/6m1+t+e7esaJvKHXHl9w56Hx
xV+8Pp//sMjxkB44n/bg7gedpR9E9kF3Z//+o7a1zjWk08h+tRPt+eu8Dh5x7+NaSo+AnX3f
NI/xb1mIUddA2/SjbJf0oU3egscQPDq9w+dm+jN2/b7+xLlvtebZUbyQj3tgbPMzXj9quFcw
/+wT0anj1nFin+30j2/gT6x5nTW/Ie+Sdw7xZWCPU6zlW933ZD7Je3z37+y35HiPN+/xHrji
sdh0/n5e5vRG8/60zKkT8/xV967L/6veRs2ipkzL+q22eOdTbTEPdeaw0LvV6j/IcxUfsBYY
DD+7aIz6nrVuTEVdp3dBN6N40csw3CtwjlgY4v9UW5nMb5Jc2UcYK/k9yIO8yDSKht93CZro
0dhxqq2eTkEbfwU7jLFvXDqK3lRbPHvV+ewjyC3Q8rvOOoN+se2w6OkW/K6ibcwMb+R7Dz+n
D1ivlgH6zMFo3EeeTnTBacb73O9kW2jzb91nf2gfGGMfffbiY97MyU2Mo+iMup95u6+tnd3/
GSMaR5qn86R9wjXGNrFc57jjGO5rm+968b7oLP59q/dz9yX24GtcPI9dvIO12/L1XccPeZq8
vou3sT8sezvRP+qfeadzu+XuTvexKfunWnEsdRKcjXxH0e1EN+sKvQX1wT56rGcf5o2Ox8wP
g+4zP8We6yr8HjoDNsM3Z/k+19bf7J+nxnqeSVv7y7rrf+JNsA05wb6dOuA71vadfW31ZH59
8EoZcr+l99Rr0mrxYM94Ls9lzbRcR/33Db6cf2juvIyPEU+ZI2717Xcbz1sP7lXBfcboOcCF
j3r2EY+8nz7k/HmIu+jLuRsa5GWv2W8vy/xN8kLfuRsevNn+7DyUvnOoNS8da63VmTtdU7BZ
r/9zbXOQsfl87q65+zz7uYd9Et1nTrctHO+Zn1ibdfiPZXxXK0671poPwVu3ZY07U21tBv5D
pnutce/1zC9gZezkOgcOIAfCE+yEf03ihQ6of+TVTvfsi8ZJrrVgBOMyx+OkLz0Z+rJvneM8
sbzXGTAoejD+6rSOnyCX4zx9YRTdR604DTlaPRz+bz89NuaOEepg6p0534vOZI5yXM/fV50f
37njmD3pHHZznBuXOzdj/7/V6nf47W+yl3GPcSl6RH720M992btKb/j5r1/HD7XFo5mLpnr2
vcz3fZz1/WNjTl4yNkQnxqD/Y7zMWixJyjDcQfc5J8+WZ63q6u6BmYFBRZRxGxdwVNz1ckAR
vBC88UpQQa/9QeJvNJOKh3zyPVFlXwSRGRHfvjMTkLvwsVPQ3QlPnttHzP9ecM5x5mkj+HfS
0zpgTZO7feMs5X2qbrve9EELfxy/L7Jx9nLEmuMqa2Pyw9teZ67X2ZNsylx3q3Jrk9St364F
49qAzB+Vx17zdT0b5f20no0yk1culU9ysGm6N/xY+EcY4o2Yo54zL+10fyrzeZM75HCNI+cd
y5RTs581TOsue97n+sXsjVv9xDpgOHP/sdb5qI93sgU1YVt1To66qzu1Gj0h90k2OpWp/p3K
lJOBHd/f6+0ucF5Er9cb7Hcukw/YDtQ77H0WDWLn2MBLrjLuY5nLR407NRb9yEUwV+G3nOAg
z28D90Uw+D2ykPddW/f6944ukYO6gX7OQZf7hHO/Zd04zoEhr0ODurovczvvgi4wnB319tCA
4x0xD13e2bbURfjh3j5gX3Kfl35gm2Mn6B5Ezzq5io75cl7fi45zkO2GjrLPRg73fYcyryvu
WeyjyGIdWpe2k2OJHgx5qEHWw0m4eONcgcz03M5jvDEuaLqvJSeiG8dS0qI23EkPvc6hQe+O
7VIHpzL3XfjY6d548SHnsKNw4B+ZZ5CR2txrOaY9Y9mGjs1dA4Z+Etqt+DAf4EAu75lPncus
D2Q/Bx1sT95wj+gYc7/tPAA+z0yZc8i18Ol5kznkKll3wpnzBLDwhg7wc/TaC8em3MaXc6z9
mTfu07Clc/9JO7byDGobHcs0K6DHa0M2bOL5A726XsKLe9X0U+sIv0UO3nLvOTbnJnjKHshz
G7JbX9wdG3hdHzLfpR9gC/t/9mDjm5XO8Cnk4m78ftDdm8Az4n9Z5v2i+zf3pd7d+/dx5pxA
XugasP5PHPSM7omJn/sG/k2Z8mdf5nY0j7YZPkosOZ6TV+Oz7XmfPpTwntvsL641qWd47spc
Pzn/mZZnwE3QtA72em+6liHnq33gxz+3QdN48zzj5qBzvznGu4twOr628e3ai7wHwR2EE5ij
vp0TnAc9mxq2NbcmPuhaT/tqV/dN6zKXh/+u3MrpGa8lB9/kVmrEpszrsvnOeuFekZzgvOkz
6972Jk8jA77WNd56fiT2vyXd2e7EFLZJO9D/WS54X1T8i7paOrXPjG+W4itnWugtytxu4CFu
iNWl1qLeez/UO/wMX/F5V7874RnzOHkfmJXONsKB/bDdK73NuoJOzPOruhvHUjbEb9GR80qn
tZKuVtI19WKvf3xiJdh14EvaSWsp+Fdxt9M3el2XuR6p767hzufoOPOZzzz3Ok7wT/zlIl6y
nuBjV/2TM4/CQe+zCT2OeO9018U9MbIvc5utq95e1mVZ3Ee7B2fWyHv36u4DPcclPveXnkk9
3/F2q3vPF743n8jqf9vXuMy34zz5Nd/2Dc8Xnn8OpS2v5UmeUy+bciuzV9qnpY/sFVz7dgHX
i3bSMv2H0GW+MV7PT4knYax/53D3ma6V6Ns63gX+TZnbIvnImrcut/yZLnpzP9rSoWluy62t
bFPX6Kd8Ivu6tLf17V7V/mT92AfyzP6UsZU29ztqVd+gn7U5Z0f3xa1ZAh5ODZqea0d85Hje
rMvUQ9Dr0M94RqJOnPR2fPNW775a5j5MvdjFd8rnOSvnHa+xVlzFw12ZZtazaF7qG+oF/a3z
5wj3rky5ZKM3u4rvHO/z7SX4c33M99RdaIxnD+L5TZl6UPRyFqx7DnqQ0xO6gy/nenpv12J4
Mpx7GeLwItla88hWurI/24ecO3yWb/IO/pdxdxW+9Jf0v7znzPrYCpftlTHd8kviImc84zQv
mbsN5//WnIt/JB3eWabk57nlWdA0E5/9bh/v3AOv464rbd1BL+27F6zzhWc85/6kZ5unXNv4
vy/t3NTy83X85xn0en2zeyZNn8ra5jy60xvXJfuVY31f5nUm62X2qa5d9ttWPTPOQwP+KbqG
fere8En7KFivhKXOOsdl/SEHw79z5LhGX7wPGlmzOLsKjpzt3sv9+lFy9LF2jfeHuDPcVufM
a4fAtw/4vtz23ubhGG+z38kzfJ65Lnu1pJO6wwbuWXO5l81e0fgcM46RlLsVB+iSvOOZJXvG
jL88B861wzHi3tK2or7bH+khnPOzJ3S8tPzpS8P6RPp5HTYZ/fWuTHXeunV/35V5n7ipcAud
jbAnwViPrgmvy+Qz0FjWhRxZk/oyz/29cHRl7k/oA7ncyyzr/UvxtxY++wW9sP3cOs5aRr9N
/9xXOuikK1MOIF6dh3I2TB9uxenuiXPLg+zHBq7E38LtPXNS8rort7y36k/+O3fYBs7ftoP/
8/2y6ty52DVgVW77QePZ1zed/rNfydXF/yrO/J3y5L37PupVH29bOJ7jr7VaOFaxE7dP9T8b
neVdJ93xn3oyz/vAsSxtvg+it3zinfsq8mfSzh7O8276HT1F1ovn8KUtW/v/48d2WpTJv5+z
o2eFzRM4W2/38Y66lLw+JZu/PVeid8dhV9o8bkV73FdlPjO15Ot073r0nG43pe3X5msX9znH
PBdDlqul9xZP4O7i23LfieYmaJFzWr5pHszXKvbUne3Xl1t7+T5jfx1w4ObffuY9fTDpGBbf
MP8rwWZ+sl96bt3G22W5tdsuzrv4dj1ZxV2L76TbCU/G4lgD3OO/KY991LjGvm2cV0bfeCiP
M8lDPbvX3bg+qP/XCsduPNe6P4jG27qDh3dXwbHG/3PdoQHMWbiBP+u7dXYJOne6g6Zh7wJu
1OXvGjT8/r7q+Cp8D42391X30EAnD3VHj/CK/lp83uv9VfhOurPOzC99e/LQ0s9VsuX5g+SE
x1PFYX+409lB52edW+fm96zzs+gyf5zL1PfS6xD3/Ge/6p7P+WRfYZyH9mWeg3J22wofffKu
TH58rG/uytSvMyuha3g5CRfx6rNeOM76P2nflckvkAMdwi/0T2Xq760PZGB3D2TdWk/gzPnm
UOY50301vk4OQ6/u5/f69s7KGdZ3nh3o+3aNM3J2H7CtWtvrLnuLhG31/jn35XKPQc/Dcl+a
57tnFnGArZHf+k4exvv7ut+Vue9B3/0utdn9oPsN9/PuF4kVFraAx07vXEvxseyniI2N3q3L
XF5wnuoZPrso83qcM+lKsrpXOkgXzD6Lhu237/Hv2c99EHjXVb5FmWK+q/crwfO9qfqkB9ro
nDfkv+wHN3G/E8yyQXcT/2u9XTbOu3LL6yrWsrRlynfvA7cQ344dw3l26MqU5/Ah4F7qG9+7
1zvnQuL4oLPx/228y9jmO/30HDQcf86j61jmgfhzv7sOOOLduA8NnNmX7nXWh91511f5sQHv
euElNnqdo+ujYDot13bPNJ5ZHAtr0X2Q7p0XvTvfOr/vG+euNa3VuqcuoiNsBm3k7svcH6nV
vutFI+shdjqWuQ2M8yk+W/L6jXOu/Xk8c3/pns//H5apLrhvsC2IgbVouAe0j/IO+JxpiTHe
kK/87dyIz4x28ezm3NQJ1rlvr3cb3bkH6vRtf3X/CQ+WBR6Xwu+ZdCkY14ZOsO5ROOuq3ZBr
HTTN+7LM+fZd1qOEQ5ddueU/c8gi+GOBZx0w5H/qctoqa+er0Au5KOsQOMkhp6D5qt53gY9/
++G+zHm33laik/TR113cP1ebrUtiZIw/8g3nJ92P61KmeQM7Zn4gfzPbZP97rjQWZd7X0bsB
e9X9UTy536M2Zt9GnuKMuHP9zFx/CdyOt6xpzHX0DM45yOL+FL75XpapnlqP5h0d5wxK73EV
vlWZ6xnczGbgo8fGVgvBIdsH5XGGxE7umfCz7A+cG7Ejay36xzLlQWyGbEfZbB3viPnx7Ydl
8hPq4VEyAee+2f7vGct56iCYPt67bpyr7l0PM295edZBZ+7njGMlvNRM/J9edCs8B9Gg77Ef
QCPnDMdjV+a+ytpV2z/IlsQkNA+NdarLZ+5jkM21630XPuJe4Knl2Haf8z6LemtbENf4CbkM
WR0PB50Zzvaw/bc6Q+/45My/Xvz7xWpc5TEerI9t5edS5jHbCRfv3Rdkbj2Kfl/m/c/rCkdd
W4ifvw3rD8P6eFjfLY954uvD+sew/lsefeenw/pkWG+0j/L/YFhfDOvHw/ph/f881nj+92H9
dVgfVfiR1ncqnq8M67NhfXtY368wvx7W1yo/f6k4xrtfVRyfVbjP6z7efaO+H9eXq5yfDuub
w/resP5Tpnr522G9GNbvq2wjvV8O6yd1/9OwfjasXwzrn8P647B+M6x/lcc8+/Nh/Ugwf/4f
71UWI9V1RF9PL697uqd7pmdhhnXYYzCLYRjBGMJqgwd7MELgYByUDcdGhuAEQ2ywMywhLAZC
YrYh2BgIkaal/ET+iSyyiM/IUcSPpcgfsWKjRCgRVkI++EjOqXtu96OZMSDhSO+o7lK3blXd
unXrqf0VrVksPRepvUy+9Ovb4PsCMAvIAnlgqmg90BgBx2rFPxxoANJCnZAB4uJLSmYo3oR4
2U9JXl5jGY1P0lxGMtLiqQHa1E4I5GnSPgXx1mh9s8bapE+rdChIT+6Vl//GKC4D+YX2d0n3
Ju1JWjSdesA4u6x7KD+FwSno0wH5PaA9Nu5iu8P29NTbNqzKZ3WSRx1z1ia/W+PvbDrYinYJ
OA+bLoC3H3yXQI8Bh6HjL6HLReg5HzIPge802gcxfhmU4+9B3tvgIT0HH/WBnoRszp2HTy/D
f33Q8SToMchYg7W7sNca9DfCHtq+EWtew9wPTOdcmXJum51BIeiEPrP/+xf066z9vtlRCHbD
p+Qn1kL3bVj3LNb1msw4bElgLIV2TfAK9J+L/lzoMBdzGzFW8X0IP2SDPdCJunbZXeqxMyph
bp35iXaF0D+0dsnOl/duTDAPes4znw7FfMHOqsN8nsd4zua4Zg/s9Ngqvw+EEsCzOKaz8FgD
Gd3AdwC2L8nXJexZBeYQa1+EnCho3yGc2SG06feBUDK/5+7Acuy3HHpz/+dA95jv3DlUAfuP
BU3rjlTAs+B5kdJW7ucp7f4RaL/JzQ1KGaNnIOMSZBwAPaY4vxulPxhTg9GLdifps7jd/a04
x5dg61ctBpzfXwSWIIYWQOZ8UMZjCfR5rOMdeQkxxXvCWCV4XxYjBknn446QrsIa0jVGg2AF
9rpo974Q0aEon4XBj+W7knwdpfuMMr4Sdgd5DxzNGN2MuT6zLzco5Z3lvSH9luizplNxQJ2i
dF+5T//W2J1jjPF8/b3n3aumjJ13Fe/+7Es6C8bNq+WcXUDb5YQdJjsdnLV+1tCP/hboS/QD
r2LNBtDToDtNRgbrmN9St8XhErNxOF6qBpxdHO0w+FowCvmsADkVXIA/zmjNLtsvDI6gfcD4
HXYYzQMZxEce4J71hleg9wXbP45z5JnETb/1kLvfckIt+AqQmYbsVLAXYwfRPoHxbQDt2Ws0
az4h3YH+bvBtx17bzdaM6fddyH4da7+N9tnImn7zTcLk98tP7PMciG+IdkLfxZbL8rijtZAX
Bk8Ij+oN6bYYYS6psT4pz32z0cDyKPvI8apdWCc8qbqnW/0u1TDbVGewPSFSZ7E/VbyLNd6h
mqhDc9MtBzHGdsGuF6DXG3ZPa+DTULXTNMmfp1quU7XLQtU0szU2VbXYTPGRTuH5aP4pyeLe
DwGTSXHHEtwLvguNvms16lK0a+z9PAn9+hCr83E/mK8P2TvCOM8jz8UxVwzewvhZq9mnRezt
lj+6I/Vel0Ddx2u+KzK3WP6eo7rQ+8qvadZ7NQKYJP6ZqlU6VQeyfukBVkXqwLGi3cIK+fTL
kTV+bonGWCuOisw9LX18TTxHeyxVn/yPW221Ab7ZBJ9ss3gsmN+eQVwdh0+PW46sQYy79+OH
4OX9P2O1SRx3hu8m71vOcssOi/McfFwHGkeuYj+LHJRHfZXGPO9GDfhDu+vufifsbjmaBE3a
2sq8269C3Zt0CP3X0f4eZG6GnpuRVzYhBl4A/YlyxGnUjTsAdxeT0Jc1WDp4B3HwBnQ8jXU7
lWMOmA6sn5LISay7iugzXoqmyznLT2Fw1PidDszb37fakW98skyZ+97SvT8KnMM+e02Ge3PO
qZalnQexxtOF5p+EraMOO82PRchoKK+ln5ljPHW+SiPXuTf3sGpNT728E8BW6HXAfFNr9ed+
yPS033JudgDq/gUcjZWp16cf9Gf2Jru3qJr6t6nX6regTFcDC4BJwDngaaAdqHeF/B3oxVux
Qv8eu8r1YGA5sBc5gP8MlZq7xfpr0d5keiZVI9aCM483qKC7OxT9hgH3E/Ax5lK6t0Msnp/U
/wPbW002fcK73hp802LS/We4vJ82nUm9/usRp+vR7zZkRLNAHqhVOyyj0+rwLN7MvHgbxZO5
r/UXVesRh813Od03Vy/3m62MR/+Gmf7mg+OmO88/hthk/GRkf0prUhYL+yCT9/5NxOUpi80A
PHHFaT1kZXUv4nYPKm9lIvi5xVOzwH3Jl8BeCcgLzc/vQPe3Yc9+6LEOOpwKiuCbaDqcB46A
7+ugu3Wv3rQ7UIN6JYb7EsM9jKNeYN//gyYHoanI/0PK6gaMY6/1ysWjgSa9C4wn1uB8jxqV
8/nGZJRzmff59rXrLRsWc2/x48rtw7V2tmgOWC25q+0N22B+ysjPLp6cT5Mad/11xpcUjYvX
j7u6ekN5rpomkc/q7V1w/yBx/Qc0lvNIv+XDsKq2cf2lOL+lZf1CtIuAmztRHk+VY64iw9Ok
7AiRP3nnmplHQYvKp1nxeJvDIGrDOoPbI2pvv9kQWv13xGit0SP21o+DjTxL1hyPqs5N0ufo
j+Tbbf8EvXYmD6tNnnHBT93/GMbHKw+FQko8GctbHZYbcn6eeQdo0fmOUsxxbq7yyFrtN17o
1BvO972N5wK6SOdTo3xHGU2qH8aiPZ2ypIvXiTHcaH6tjM/g2KB40Xiqx1PVkB+9zHAgnkHW
TYj42OX2Xeaj0bIjLp+1y1dtWhuXfz+PJkT9WNrLq6bUH3gkckasnSZH7BnIrrrIWHQ+fQ+o
lpuP7E1/zBI4Xh+hMSAQjVXZmRWN6ujlt1TFAvdJKG48Tcm/nRqrtqu6nYj0k1U83ueeLx7B
Hf6vWhtdH+WL2td5G/9Z+0fKx1hBlIKVAGPrQSN8wOA/EP+F+K/Gf4QpAt+LaWrX3yPSX4B+
g+FefJV4APgiznAw+JLvNWCL3gxiJdCt2qjW98kXaW/hWqt1+ity7jYvnm7PE217faJrqtY/
0P5A7cFQxeP8U7J6slt3r1sIIrjf8bvD7R3Vo1rXlREE8q8/z+A2Wqpae/991mmJMtz4+Zh7
v0crf+eDylt/ey59DHNEpY5oF/yb0Ao06g0gckKr4WX3TxrhKwj+vXH8L7v/QvA0A5X6YI/t
0Sz9WBexlmgd4J2KvlcLgu2g263ta4PQxh0GWxtaXfh5873lPMO6mnmdtrE2mijK2mlZzOVI
jrXFXN3dAyzUPDFGtozRfJ3ksTZfrvZy+Y3/eO2irJNYbz0Wc/nY00btxRqO9SHrF9YKLcKQ
Qdqu9jwquH+JJySXOj+s/jjJ7Ii5/wL+Kzyi/ZrVH609GzQ+QnSI2s1a2yadhyoOl2k9+WZp
nPss1f9fGv9W/BdMB32iGqc8/H+GEV62n+P/bsy9YQX5sk5nRn+PlS18yxZE9m6Sv/0ZPSR9
J0jPOdL7SxqbIFlPeX0lb4bGx2k/j3E6xyhGRmiLZLdLtl83vWq/CbKNmCI7RmvdePFM0boZ
omOFyZE29ZlYBcreDjwPrAKeibl/vhmycabOi75o1N4+Nv6f72IUjTqrdunYorEWnSfbQzU/
VGiMgHaOGOBsOgTa16az8XHRLF8P09gwyWiTzCKp8m0bgf4i8fDchisvNQWuXi8orzapJubY
yMD9O3HfLrRHqH84xv+23wA3wP8BeD9DjuwDfQ9jvwWuBfUYb+J4zN3HhuBDzF8DTqL9J/y7
fgZ5t7DHH7D2E+AK8uXHwJVgmOEm6tpb5TyXD65Dx5vAdcggPkKOvgZw/39h/t8mv2C4Ankf
A9cg44bZTj2yoiM8IK/ew+8Tq9xXjwr/X83XddCrAShi7wLsypuvP0Rdfgu54ddof2R+aYWP
RqLN+VrMF9Cul8wWs+nP0O8m/HXVcl+b4X28i7/C2t9jzaeY+wXezatY+zvIhS3BZYx9grV/
BP0n7L8Keh24Cb3+A0p/3AD+YWM5+LcAvXOKk4LJ/NTOqBb82eDvaN+CvA/K/s9CXjb42/9o
r7bYqo4reu7z3Pe1r7HBkIIBQ16EkgAu5RFMeTgYAkERtIQUNW1JExQISYlJ4jzMM7yJE552
AAMube+VyhdNVUV8RErz2X5Xykfbr0iVWlVVqvYnXWvPOvcebuwAEpHO0p45M7Nnz579GvDg
+o/Q/sz+5b2/QU7ewVXYynWcjft8bvLnbL/r1XxkAK+xWOtAuf4q/Av8AnCvf0N3BO+ugvH/
Ab8zOfNYR/ny3p9MnoJ3Cf3fA380G+S9NHh/hj1/5k3Cfq2QaaLuMIu1DfhPPYzFmrz3Kc78
OfAF9voP7urvaPfhXfmF8WoF6Ju3qumz8q/GSC1vEoxzjHsZgXMYF6mTBrUnqN8oPo3qN4lX
Rrwmq2335r0IP+4BRCOuFuacDtn0QzjHTPkn/bxdPh/QvHcNfK6hfw1+cQ226/pNdSiBxxxC
Mahd+7Df6n2Id+an0OUN3MPHoL8FLoPfH8DrE7RXQK+D0Clt9RJs+B/494ndfRFzx5sNfIz5
N7DPBfDi2IdeFPcbhZ1HYFdRgL4wI+LqMItPEc/qvxbvfew7AN7vgt8A7pd0NeafxJ4XwbcT
8zu//K93Fvw70f8n5l4EBjF3EHQA9/wM6HvgswH7c2yvnSnm7Qfehgx7bH/GyB5QqxdQH2aB
aUBO7fu9o6AHgJfhg72gr4LuAw4Au4Ed0AXryGGMXQD6gSHsdw70Cv6/C/wS7cPARfEqA2ds
POv9AjgOvAMMhNADPXKMfE4CV3H2t8RzH85Muc5rX557J/BrYA/wgfbg2H7gBLAXa36F+f2I
aSfQPmP6zUJ/SW+B2TvrPdYBrFFoezO9NWjMq9buvmpvH3pPw3qKGE8DfrWun2P5JaCsramb
CcozefXz4teourxg892ajPZJ4TwZxIgM7C6GMzfiPAXooNHkP4b7/w1kGcb9LwbPI5h3Du3D
+E+b4//r4HcBc0iHLG8VcWbfxi4j1t6ADQ5AxjOg/eCxAWt3Y68N6G/FeXj2rVjzOsbeNplz
VbrG/DNl+bQD8sz78i/o5639kd4evAfOJzZC9h6se8rsmzxjOEsc/5JoR71XIP9C9BdChoUY
24p/Nd2zFuX9JUzW+eb7a/C/ZLXoJtMTz+VDft/aFbs/+tMUbxHkXGQ6HY/xot3VHNN5Af9z
NlaxN1C6ip3S+0ioALyLft1FgA3g0Q28CLB9VbquWKy/CZBrkbWHwScMnu8I7uwI2tT7SKiE
3nNhrMJ+qyA3938adK/pzt1DHbD/VNBU6J1Y1L1E7b5IeVbuF1Ce+x3Qsntrjkppo4PgwRh3
CLRfdn4rSn302JtjZDpsMZs6i4FGcUcJ7wWc9YdmA07vzwPLGBvBczEo7bEC+izW0UdegE3R
T2irBP1lKWyQdDF8hPRJrCHdYNTz1mKvYfP7YkiGknTmW2zu091Sv2F6wCjtK24+SD9wNG10
O8YG7Hy5USl9ln5D+lPRp0ym0ogyhemBap/6jZrP0cZ4v4Hf0/fq6V6rP2I33X1Fd0G7ec3i
WMb2eU0xodd4pxCT2c8a+KbcAXl3uDcj5ma8LaDnQN8wHmmsi1lMD9vhMjvjPd5c3MGzGMfb
0/sR6p4LGCuHcAX6GNSa3bafj1xShN1xvkOv0QKQhn0UAO7ZYHgFcl+x/WO4R95JzOTbDL4H
LSZkMK8IninwZt7xYRMp7zT+9wA8zz6jWdMJaS/6zK27sNcuO2va5HsZvN/E2p+hfT60pmy6
iRv/svTEPu+B+LFoB+RdarGsAB/NgJ/vrRQWKId0m40wlkStT8p7327UszjKPmK86rilwGqA
dUi3+vMj7r3ZA3SqzXcn36KL1J+puUv1n3XTfaIcm2UxiDbGGuE5yPWW+WkUOmW9OU98OsVz
sWo81nRLgB9oTof4LQRma95sqwMPGh+OPy5e3JtvxgdJ4WNx7gXd+UYvWZ3ZhXbU8ucZyMe3
3GL4B+P1EcsjtPMC4lwMYyXUHT7uqlH8g/N2Sx+kCY3NFyj7NI3PD40tlb6pq++EdBWsaY7U
3mAPaP5s1SI840rVJ2uAJ4FHgRWM46Ldwlrp9NHQmmBsmf4tByaFxp6QPMRcycg9utTn/BWw
YfpGwdsGnfSYPRZNb9+HXZ2CTk9ZjIzCxl3+2I+59P9Bq01i8BnmTfpbzmJLr9l5DjrOg8YQ
q3yr2fqx7izW9ZpvRDHfN193/h0333I0AZqwtbVxt1+Nupx0BP030f45eG6HnNsRV7bBBp4D
fU8x4hzq+F7A+WIC8rIGS6FmLcF28xhvQMxyMeaQycD6KYGYxLqrhD7tpWSyDFl88q3uDGRg
3H7Vakfm+ESVMvadlN+fAIawzz7j4XLOkOXHop3zMNYEdInpJ27rKMMbpscSeDRW11LPjDEB
dbpKIda5nHtMtWZAA36ngZ2Q65DpJmP150HwDGjZYm52BJqx+srRSJUG8pRBP7Cc7HJRPQ1y
U5/Vb16Vrgc6gQeAIeAJoA1ocIX6V9CHXLHWzpRUTej4VGysC2gO1dwt1t+I9jaTM6EaMYOZ
BeSgonx3PPqNI+4n4KPNJeW3Y82eV+v9ULY3SkJ5k74+zvuJ2WTGal0X91MmM2kg/2bY6Wb0
uw1p0SxQADJq+1V0WB2eRc4saG6T5qTvaP2waj3imOkuJ39z9XLZzkp7DHKYyW86OGWy8/4j
sE3aT1rnT2pN0mzhAHjS74/CLs+abXqYE5OdNoBXVn4RMz+o5co43oa0p2aB+3JeHHvFwc83
PV+E7BdwnoOQYxNkOOuVMO9ek+EycBzzngHdI786aj4QRb0Sgb9E4Icx1Avsx/V2S4xCk6H3
Q9LqBvzHXpsViycDY5QXaE+swZmPmhTzmWPSirmM+8x9bcplEyIuF69QbL9Ha+eJ5oD14rve
ctgW01Naenb25HSa0H/X32TzEqIxzQ3+u7p6S3WsniYQzxosL7g3SEzvgKZqHClbPPTrahvX
78L9dVXl89EuAW7sdPV/smpzNR4BTegcPuInfa6ZcRS0pHia1ZzgzL4XPsMmg9sjfN6yncG3
+u+40YzR45br23FG3iVrjgWqcxPUOfoTmbvtTdBndzJDbc5p99537zH8n6Y45AtJzUlb3Jpj
sSEXjDPuAC2630myOY4tVBzZqP2mCR3K4czvrbwX0O/pfqKKd+QxRvXDVLRnkZdkCWSiDTeZ
Xmv/H+G/UfG8zan/n6yH9Bjw9EeaM8q66SEdu9i+23Q0WeeISWdt0lWr1sak36+jcdHgXyrg
V08pP/Bw6I5YOz0YOs9I58qH/oXHU7eBer6F0N7Ux1yB/xtCNAJ4opG6c2ZFwzIG/FvqbIH7
xGU3AU1Kvx36V3+u+nY81E/UzQl0HsyLhfAV/detDa8Pzwufr+Om+eftjVSIsIKoeOsA2tbd
hn+XwTcQ30J8q/GN8JDAfPFttRtuE6lvQL7RcDu6it8FfBN3OBqCku91YIdyBrEO6FZtlAn6
nBdq7+Baq3XKNT63Gtec7mBOuB3IE15Tt/6u9kdqj4a6OU4/Fasnu+V73YIXwp3+vzXc3mE5
6mVdF4In/Qb36d1EK3Vr77zPOi1ehft/OeLy92TF74JXy/U3x9LlGCNqdUSbEOSEcUCTcgCR
E8YZXnJv0tC8ohDkGzf/JfcuxJxmoFYf7LU9miUf6yLWEuNGyFPhfNXp7QLdZe2gNvDtv8No
a32rC79uvK8aZ1hXM67zbKyN7hVl7fRYxMVI/muNuLp7DbBE48QUnWWKxvPix9p8ldqrpDe+
8dpEWSex3loecfE4oE3aizUc60PWL6wVWoSxo7Rd7XlCcG+JleJLmWeo3y6ecyLuXcC3wsPa
r1n9ydqzUf+/JTpW7WatbZXM42WHj2k9583Vf+7TpfdfCm8rvgVT3oCo/pMf3p9+aC7bT/O9
G3E5rChd5nVn1PdUnYW5rDO09xjpO7ij+yXvdMn5Xcl9n/5NF6/HA3nF7xH9b9d+Adp1j2FM
DNEW8W4T72DdrLr9pv+f/SqNjeuqwufN2LO9mfHYs3m8xh7b43i8xONl3KxO7KRZ26aJUgcQ
pSUqEKmijSBthQR0SZEo3aCkJCENoZAQBMpS0qRVF7lpqYJokanyI8pPkFAkJOAPCPEjfOe+
78YvUUolkFB/1NZ3z7n3nXvuWe49cy99UwzQjw7O66bMAOdVSItE2cerPaXroLofAO4BtgB3
ON6br0IfR5gvjUWaa9u98f/8XfQjzVwtoI05juWYT+Wb+L2JSPugfrbeIDejhPpXYG7svsgy
1s0ca6aOAnU2KGW9LSjQX0UZzVsL61JGvPt6HetqhndiHWsT7+2k6y4G38r+k46+217EvXMO
8sdQH+dQEx/CvXQfxg/jPnAe849B55zUAwm5AMxC7j3gYfCHAZ17ATiJd+w7gKWv4N2ouIj5
HhIGb0Lvb41uD+ew1nmzXhRUbYmTumbsdeASavB56LwI+gf09dsl2GQxB/0XiDmc6xvhkqSu
YtboiWM8afw6h7GT6F+kv5cQ031YYxb8ScT9MGKpdura5zB+EvSisSsGRCCXgp6ofGBqX8Hg
NfwuvoR47sX4LPQ+i9+eV8DvxZpvQO8+M57EemF5G7+pZ6D/PWNTCn6oPS7i6JocqI0nMecd
45+XhzlpAm3C3LiJ2Xx+ktCThHwM62mMkwbPgX8N898D3jZ66uS0LIXMJMZiyEsEvBeTY8yV
xvsC7DyK/J5Gzl8H/SXGZrmOjZ8X4xTjnzJx24d8zRk74ujHoNM1ssfAK30Y9LDxK46YZEz8
Zs2eycj3sdYsYjdH309D55vQdx56n4Mete8y5v8dc/6Btf8M/pt4V84ZuQKgZ/Oj7vQuz5f+
ztjfzSTrnNa9GKEyWhf1NzpFvpn9euqpZz9NXTHq6iCv3+rkyzjHuwFSx7sLq8w4a8EA/Bjk
+dRz3sUzb2lCjkPPcfSPI0bHEROvn74ODdAxqmAN6uI62i9grwXlXcljHyblLdCXgR9D36/N
HsvLGsT1AGI6C12HkYe/YEzH38f3l7Hn3ocdb0H+DazzAnTptzMSkH8BR+HWEdAj5iz0O949
zNQnR8z9Lyffw7r7ofsZ6NuPfCrdCHndo4egdxLyk1f+KT+A/kn0/wrZQ8AByB4A3Y89cxfo
d6FnG9bXb48an4KyB/gGbHjErK81cjeouS/gfugC3UCc/EL5DujjwC7cFb8G+iDoY8DjwMPA
fYiF3iN/gm8vAM8CP2J9eBHjzwBHwX8bOERdPweeN99d+SnwFPAtYL8PuxFH/aZ6dE8fge9f
p87H4LPadZDrqt9fMfvehV+u/JBr6Lc9wNPAo5jzM8g/i3r4NPjnTXxdxC8kS8x+1/ue3gP0
jiL8/fgqcR+x1fHuL1u5l6++GZ35N+T1sN8/Su6/nX8c+AXPUJznTbHSufb+bMc33UDW9hPE
3cATwBcd7x6i79IZYA2hZ285sJjfqoyfwt5rdUzvaksoO8O117CvcdV7Uo42REi1hth7rX5r
oA/tPuQopzmY4JjybbRfc5R15u+kDaT1zK+uE/b5rDWo16dT57VwnR7qUx32npuhve3sN9KX
jM9mrUcdPvkkded9fvdQj30nRGiL//1Q4vx69tXeRb551t+qc22d7vHxvye2+3Kse6fWRzXn
fwNuBz7FPNn9/y7juZfU7oOP87n4X8+G7nu9v68n1f07Sr/bfbSesG+H5dRf4rxFRD8xRaQI
taFA5Am7z/WcNRJWxr5J7Bs0S9uVtvrQ5EPSh4QPfnl7duze66Uvmk895xFfLMbpYyfldO91
MQ7WTq0Fk6RNpDq+jjpWc12dq+fKvgeyzvwb1p5B+2azb4M6Z/59lSHsO8PG2cawwPlaizoI
a+NdwJ2Od16biRzt8MdpsQ9lH7IfggJlGxgjzd8S9m1M7X7qYpx0L6xwvLffJvqqedV3UB/t
trVzp+OdS619NznztaiNObb1zNaxBme+jtp6Yn27UZ1QnbfTnqXsL7sOOn4/cK/j1RVdb4z2
T1BmLXOh++ULnDPBXCygfC9le/ltEeXHaavWpiFg2JmvcQrdi3rGtzneOVnL+EySal71nK1m
rD7teHtvN2MyzVjaOXeTn+GcKdq4ivxa55N6+Z/qpfpSJtV86d1hBfu9PtpFjBIbCXumbroO
a4lOwtaJPqKbGCI0H7qnS858TZ4gVE7fLnqWWpz5+mXR40P7h6DkwwDHuumT7v31tG8b7dOz
ofVa99hq2tjCsTXkO6hniHOvr6G6v/Qc3emjFY6rDbdxvo2hta9CWP/subI5GCasvB0fIOz3
hcRnnPnfHxv/zxPd7A+Rn6AvHaRT9GeKebW1y8bOxtbmbpDx6mZcF9JPld1C+iXHqyn63daU
aerW2m5/l7rIVxmPzzI/n9TRj0kdlQ1nZXLzDNr6zTNnnSt7TsiTzYY6T25vPiF7tm8468iW
mRPOCeep7afGRqV8qjKMZmgQTX8ZzcJeND3daIqdaBa0o2ltkfKr0iat0rK6uPpz069KhyyQ
dvJdUpRO8iXpkW7yfXj39pIfkH4pk18kQzJIfkQqMkx+XMZk1PCnbrsVq27aiGb9OjQ3r0Ez
PYVm5SSa5cvQLFmMZqKqht0kE1KlkqV4hi4mv0KWyzLyq2SlTJJfLdMyRX6t3CxryG+Q9bKO
/C2ySTaS3yy3ya2GR7B34P8A/oNI/9hIdkd1R7UqEpCEHJRd8juMh6X2RBvKxwpnJFwNF6uJ
QktxS7GhcLCif5qwnOxFRH4jIcmq5GknGAgGwn1yWgJOIBDsqxahOVxcEMsnYr/K5dp0zpIr
l+VB6I9Se75nbLSaD2Uz+XsrFXdwMD+8atWwW162rCxmU4QhP+2THw+XxsdGS9VcdlrF3UqT
J+0OrzLyuSt/gk2NV20K1tbUGpsCNcEa2JQvGqsWxGKxfKE5l9M5IdkKm3bA54RZ47SDQATq
+qrZ4tiDu3akUpDJYqgfeoPUGwBn9BrZoJHtzzdCoSO1V/4oD8kHkKCP1Xy4dmdsZ+5y6LLG
OALslnekTtolYyROuc1O+Uws6sbdRCDfN14dH6nkc9lMOFTsLPWMjZd6ip1hDVJupFIdH4s0
Juvrk41ee0c6FA6H0l57qDGZbFyyVNulY+lQKDM6jjY9bmJTwLq3YN2ItOqqZ/DoDQfCQXjx
kkQCgT4vRm5fdZlTHKtUR7LVtmIoHrhlU7zlnM6PY/4uzG+5Jk6O8R0mIy2emUWf/eFd9+Q7
09FQLBKJ5pxUPJNOJJtb09l0qlzKNdZHQ5FoS1cqnkgWWts72r2cu1B7P9ap2OgMBBGd/vLA
4MCQRodRwHJh/7rha9bN+eI30hELx2PRqBtJpWBHKAp7HLUmnYkn3Vg0EU6mktl8oi7fEwtH
o9mUG3HqnUgklYmGQrFMUyoeT+azbixYE06il0zUtdk8PgA7XUlKSS2djEvICQVC8VAiVGvC
6iKskzGNa7QmVlPjeLFFaEeyxWxpLLxhaiqfzeYHAvl8+pFH0oMrZ2aujUGndKrmk3Wh8qlk
ovbfbFdJbxzHGe3q6e7q2qu7q7tm5ZAzJIciZUrkkJRkSSRtnbRYShzEkIUYQRIgixMgDhTD
MZLA50AIBAi55hBfclUiCTzlNODR/yFAbvkTzlfVPdwiEt1cpruW973vvVcbwVGmcjVotdD6
Ub83WBgMzyMCQIxh+DE+x6DJdEQTRlJOkzRnJvnoTiSMYrqQpuQK2RX4P+93aVL+sngP/r84
KiRXfViDbGq+EGwGha/GP7Jw40irLM8KN3WD/XnC7tSFsOPkDGvd6j7GUZImWSSN4jrjRSbL
Ac8VkcgOMZdJmmICa/k7PJZtW66XljMuy1s3B5zIah1zM5QJJsMeTaC7HEZPfR9tBXfmq7Ow
uqq0bdtxq7sw/d75NV5bnazeRs1iB8jRZhUn8Ev9CnwE7+yklKaM+fsAay2sFVpjksZSiaIQ
SsbpAoaFU+rvn6Q0M0B3ajKaJljnPS2E7uUat1qxLFBHCaE6qJBx6wOcGpSnGKc5Mimu9beu
u8O7YX8sgf1RKwZKuS2d1rRZ5rWzmCfnhGJn8pueg1cjSyLQBxUxC8DnIst4SRLMAGuCufj6
1u0eJ9oIEiXqKuC+MsoFh88HQ5pg3l4Ubm3ToAfW8jfvDUPPd+oUIAriIAK2H1Kn+1GM46jW
/gkI7T0LX73qiVPawD8cBn+A/WGoXlmrSICiOAL1SSimTk2Av3Y8AZ3G035722y35WUb6lE4
m934Poh8y+uQ6zsKTr4WXPZ63Ev7qdPjQ4n7ab877A0XyBpJ0PohA9w67e5kda3lldURYQOV
073zQrGBdqe4PGHKA8CFkKWFiitGEoaFKDrbOwObcco4/yIlQmBy8yFXZcFImGBhO6KY/egR
pzpnvO5hwAN85RhSRsPNFnAzRC2oZc3Ns72Cx6vnVf7a9HMti0J2ejIvWAl6xRJKsMlSSlKK
2otays7ufk+ycnmRJdhcu5oB65ZrnHnjMRSca9kjVBBDPEI0NcTktKAgR0c4STOdw3KubZ9A
s3eKyGYulRY5W89taYajUSnV1rYWf32Z2xvXSzPz+xTNXCRY9DMFEYpCL3/Ey18LRQjHaezk
b9cJn7vELz7c3w9nxXvFD+be4nqZB2ueWdpzKYlBLUCswdtcrMApd0ShLdYK67GmbjyQ1JLb
G9beCGcPH862tn5c478DY96HMVs1/iee/QrSSehd6749np3u4XN4Nm78PUAx8v4ehXHoJvOS
Lex3f378smhqW3t4v+4ENzgoRBrF68ERCgkVMqknmdqpU+TdMR5PFsxiGZaLJmzr9l9ezL76
avbixYu53j/1XtKtx0siHFH4M/IhI4yTyI82Gdcj7j7t7yAL1zGMMHNjnPrRmVwRl2/VjrlY
nBPHEf6iEqYUVSVKI94XxDmjIJSRr/cPKiGqg32496/fEISIG9fh3vhD3Ys2WPfIlZALPcqm
9NUPKlrlqECObUDchm3lRU0G3sHGVmwOPk3zBamUbA/szj/vUZLnhBZS9XpKfm/WcPtLP2c3
uOTnbKcd3/1vCmPbkZsVd9JOSSoCs76GzaO3tr5t4HxAUkKzamBBqQlZbo/6dvvXJNWK0Dsf
adGuJG198uTJrKm748mVeU9j6GmYAHyrNuI5xLfR9Cy67nve6Kdx7m5pley0hbZpynVKZKfS
CGmVV86VQ+o8hchPueh0lBS6ogTyCzwGip5DnRSYdC+jGBMuGs2Z91Fa54b/y3h1GHHkmocR
35CTn10KHz8uipdnx7C1tkIJERNcWOS4+Cov3DAawirYbFhBPU1Rwt5di8CGbyLvnNO6po5r
3GIskcCpVayDOkwdP9cYPE89f95VjKmumzNsfEHNsyVlUjnK++5xF3QPdFBoRKgqFQpTmTzM
zfEf4WtW99D02/9CVvkGvKVb93ALt8LMKZ5rTr9n5VbpBWh6sLl58I2e6Ro3Ae8+OPNuEuKw
fjdA7gyBkXvXgbU73RUHB5v/0v/Rs1Ot/W3wDH5uBZv1zBt8IwQheC03r7QArQo2yCgPK7El
ldTvXN68emUrcphBQDqR/NNc8rZU62LJeHX3Mdccx3HMcqGqnFFGxcj1twArB48QvGxDUmlH
H4AN45jQOC4njCrNaMSiJEliCGDCCE6pesRZxJrM4TKeDhaDBb9+wSTz6wdiwfqPXCojzBH8
TMxzUFwQkKTcKjXXWulCGUMJ5VhwzBilz7heXYPUmM2+8whcTCwOOZB7dJJ1HX4nPmmgp4rc
lKY6TZjzmSbT6mLIfIwTwghnIFhgjBZBli91VmhjuEDVr+BTvtSD9EurvpY6W1wp4MDR5BHX
z581e3+nZrvjuhJaOCV/jaRyBdSBRg6BCn6Cgzu6751ZhOfF6oWw+cAomRUyy6Uxk1QwzIhL
DTSU2doS6NndmflJKgZLDBMx7AsczPPfU8CiA8l/XGt4y6CNN6qru3AkPZR1foAjCDRe9JYU
cZIeJgCcIxf+jEOziCJTZSZz9AhKwnCCbBs5pSVp2OMQbpZXMsXV+hJxKXHFkBQhkubnNcXU
7D7kcZBAozh3igGjV1FcC4sPhmkAjfIazrGoqntt7EVmdweWV4IIlu9fumRGoxXQsrZ+pr+8
fUt3lmITIyRdtmPf/hsy05+Dy8Et6MfYI7DX7G4PBsBz9jVYnwv07rrgaZOLRwDDWZZRlUuB
4TcQ/ii2Q0CCD5d4mgvdilNroHfinORw+kvgSOLv94uKuxYuoijNC+gccOQoBk4IwjnEQRcR
6XUYLcXQjQDJp0mihXtV6CTxOMqGazZYqplGMMUmL3PHtDcpKQwI3muYBKA7afrxvLUGXqvX
Ig7nCgJ7pqCQxvw+goOt/ukPBU6YtHdnH8Icu3Dd9bkHB+3TnO5q5mZ6FSAXf1xRgLV3jTHh
n97tduta6ybXNOn8jctuTgnehC3KnB5j3/Ygx3b8bmXMdmeyae93rs5+t3/1Y3h/D96/dyZz
eWU/N+k9mK/OXJH38WfBcp0cDqV7mFNBbdn+H/v1ExvHVccB/Lez3p2ZnfXu7O7s7Max4ylN
SOLY7qRxMJGqyqmD41KbgBM1oDQta3uzu/KfTdebNKaoIMTFMhI+9oBEDz2AVFFFVCpIPSAV
oV7gQpFAKqUHEKjixB8JISTzfW8mWdtEIIHEAb5jf3bezLyZ92bem9+8V06rcRQ+PFm/gnHU
m0mjD33e8NUl9jyQfc9G9xHdJTY9vCOplOkl8a3Dysu4birjZtNpo2HhkJm/1rSSer1VwIJG
Qn3yeu61vb99fK/ixe1T9lX7SCWh2mdfwb3Gup5OZxzVMCkzW3QzGW8tjYbxZ7cGTBMxt7C8
2Is7t1CWGqvFUc9G1HtgoFXd2j/QjUf8soul7ONnwHai8If/bdc9dlQdOXrMNWxn+AiCjnNk
2FFjtf7dX+k4++/E+YOv0SN+IVss5txK1vMqTjZn4aPjOJa9nS0eP4qIN/man3KyQ4M5y3KC
wLHUPdso/3l9z/djLcJ0wSsEBR1riyVfx1rE/eEjgYHyMTer6lh7oHQ9nt4b+M5aOYTRjOVm
bXvY8/oP552iCr3uF6zcQ0OOablDg1m78Nrjh53isY+Wcp7qf4dRp7rsYN4S9VU1QtB9NZVG
X9XRRt/7J4JjBc/bSVXN8U9uDUXvieor67iX0/dar4TWKxZK0Vhozzer4vfacfLMgRFhL2w/
jX7Tr4bplSLGojm/ik+XlzZzORMRpHDIQuNWvGw2ofpTKo0BgGmlLTufy+Sy/YM+5kdpHaZs
NTF1MEMtxGPV5/ESlWQiHsel1FCmlFJP+27BOIU9mGVZhm0gZk/1o/oJH99orPV4TkUIPe0p
e6h0GbdwdiQIvLExt1A81P/Qi+7oqHvNscrpOHao+NbGMynL6eh9TuHr4xYLRRXj1Pt8N4Ey
S1JO4BXEMCjpI7n3a7pnzKySmJ8dKtgZL5XK5jIOwoadyTcWs6lUxiksbHm6zEw8djDF0e3w
XTFVnDkeDRknRsrDxnB5xNhqNrekN87c7o0zxcnqcebx/QPNwYFyzuj3+41ceaCUN/LG1mew
bF2/vqdM5941MFNNqWtgPmE+rK40eeapk9WhoerI8erAQHV2ZmJiZvrRR1X56h2I3vvo2xYX
qbrHWXXjtv+RxJA/blfQZ818evvZZ3cGk15f9d4cVfU5W4r63Kj5zJSVUmNT1VNN9dAuTz09
81TtRddtuWpwm8QsaU5+Iyv6e+DcK1fNIlXrwrnh4Un8zQ3rRe4v1QMuPMAd+Bb8vCeBqUgi
hGfgi/AnvPwT8A1UBuckXxHpOwE/jKReFknjePrOP/GWiLkMH4hYc7Gd2K9FbHePKcB++12R
zCy8FXE+DqhfdhB2Yu/u1+/G5vbL4Z5yXxPJI5DlUV93FLAudOE9kWI19ln4qkgJvbP0ZcC9
e8hT7gPUq4y6+lfgHfiLSOUxwP1V3oDfExERERH976kGRERERERERERERERERERERERERERE
RERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERE
RERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERERE
RERERERERERERERERERERERERERERET/XyQn35GEREsbonRSXGxF6T6kvxSn00h/PU6bcl6+
iZzSZ2NPUT6I0wau+Yc4nZQgIXG6D+kgTqeRnkI6gbTI+4nPx2lTvmI8rtMF7L9t/CBOm/JS
8mMnpk8Gp8+dmwym2zc3O61GsxsstJbaTWyv3aytb47OXbkwHpxfXQ2ig7VOPejUN+qd2/Xl
4Nb6cr0TdJv1YLW1VF/fqAe1RqdeX6utd4MXWt1msLDZXmwFT67VGq07uOL4+OzczMUn5k7N
Xx672O42W0v/avt+ImhtBDWU3GhtdOsdlN3t1JZRUmclaN/QVZhvLXXaG+0bXRTUudnu1Lqt
9vq4zMqczMhFeQLrUzIvl2VB6tKQW7IqNek84PgYttrSlaa0ZOk/Pn5CpuWkBHJazuFvEqlp
HL0pmyi7hXo0kTNAnVTeNrai42vIUZN15BrFda/IBRnHkfOo8yrWe89U91DX++qyAR25jd9l
7LmF85f1nkDXRuVa1eXUcWRDb9dwHXVmHSWq8tQVX0Cerq7JAspvyyK2A3lS52ggfSeu4zj+
/vF+A/xu6CtHdWro7a6uR1SvLlI1XbM1XfsV7GvLjT21nNdX6mDvhj7SjUvs4Km09dld5Gij
vuPx8+093QXUdFouoV0CvZ6XT+O5fUo+13uSjdHwZ+G3wz+G74Tt8MPwt+Hfwp+Gr4bvh98L
Xw+/v2s1R3btcP3a1ZUfhytX/xrWwwvhjUvPLLrh1fAleC40dsd2z0gQvhG+Gb4dvv5fv2cd
US59mPgdzpL78SVQYSXxCLYSeo8hyalfXP/Jc/nH/ixOlOXumdqPeuvdX2Lve9g8hLw6w98F
GACk7xhICg0KZW5kc3RyZWFtDWVuZG9iag0zOSAwIG9iajw8L1N0ZW1WIDExNC9Gb250TmFt
ZS9ITEZHQkwrTVMtR290aGljL1N0eWxlPDwvUGFub3NlKAgBAgsGAAAAAAAAACk+Pi9Gb250
U3RyZXRjaC9Ob3JtYWwvRm9udEZpbGUyIDM4IDAgUi9Gb250V2VpZ2h0IDQwMC9GbGFncyA1
L0Rlc2NlbnQgLTE0MC9Gb250QkJveFswIC0xMzcgMTAwMCA4NTldL0FzY2VudCA4NTkvRm9u
dEZhbWlseShNUyBHb3RoaWMpL0NhcEhlaWdodCA3MzcvWEhlaWdodCA1NTMvVHlwZS9Gb250
RGVzY3JpcHRvci9JdGFsaWNBbmdsZSAwL0xhbmcvamEvU3RlbUggODU+Pg1lbmRvYmoNNDAg
MCBvYmo8PC9TdWJ0eXBlL0NJREZvbnRUeXBlMi9Gb250RGVzY3JpcHRvciAzOSAwIFIvQmFz
ZUZvbnQvSExGR0JMK01TLUdvdGhpYy9XWzJbNTAwXTRbNTAwXTkgMTEgNTAwIDE0IDI0IDUw
MCAyNiAyOCA1MDAgMzUgMzggNTAwIDQwWzUwMF00MiA0MyA1MDAgNDYgNTAgNTAwIDUyIDU1
IDUwMCA1N1s1MDBdNjFbNTAwXTYzWzUwMF02NyA3NSA1MDAgNzcgOTIgNTAwXS9DSURTeXN0
ZW1JbmZvPDwvU3VwcGxlbWVudCAwL09yZGVyaW5nKElkZW50aXR5KS9SZWdpc3RyeShBZG9i
ZSk+Pi9EVyAxMDAwL1R5cGUvRm9udD4+DWVuZG9iag00MSAwIG9iajw8L0xlbmd0aCAxNzA3
Mi9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoMSAxNzk2MTY+PnN0cmVhbQ0KSInsV0tsnFcV
vtdO7Hm/7Rnb42Qc23ngOPGD2Hk4qUPsvN20adI0SRsS0jSRcBpThdAEARYLkEAI6BYJqQuK
BKiqumCBAKkLFkgskRAowAYkxAqhLlggzDmZ7+T/5uafyJVYIMGMPt3733vueZ/z399551za
rbpON3Hmhd1TZ/7+6d/Jyk8FL16/d7fRvaPzb875inMdP39t5ebtk2+/9RfnOn8t+9mby/df
+8Nv3l92/sp7QvODWzeuvfrB57806Tp+dkv2Z27JQoe/cEno/yTPI7du330z+5V33nFuQ8L5
ix8u37l+zV39xRXnr74sz/+4fe3NlZdOdN6R88eFvvH6tds39tR//K7r+Mk5kf/hyhs3VjY+
PPMr51/5p+y/77xb9d9yG2W+Kn/nChhXXcYdlhO+y3V6/claZyLnHv8uXVw84uZdY+3P7uHa
QzfiFBucb+6u/f/3P/1zP3QdbkWwYe1fa3+U5y6XcCnJqZxkWMlVXK+ruX5Xd5t0pe2+UKxD
1ib5/1KSri7/jrW/uvNu2u11Hwi/eTfrDropNyc5+nt3wS1JnW5+hLdk54FouOzuuIb8+0Wi
6qDIO/fe9p2nzr60uDAwNHRxXBNa8/pRnluCW6bb78UvPF5YfYxJQUmQFBQfdYgmcoJZQRp7
aawlQJd8VH+rblCQFeSxlsd6AWcUE4JprNl5PZMSdAg2YH2joFvQhVHXa+DbBZoOgNcSkGNn
NoDGeCntlKAM2Ztgew/OdUHvPHTMAXp+QFCBjD74JgEbu2FHArwKJM+T31TmjGAOOqQkDjXB
GcFZwZBgu+BTgl3ktwKhD7qo3LTQjUCWgelrgV9sv0bPIR7FWfg+D512CuYE84KDgj2Y7xLs
F7wimMJ8BPNP4Flt2SuYwbPy2SH4mGAr1o4InhEcFTwnuCx4VnBOcF7wSfCbx/mz2Ffa4zi7
CHpdO4T1w4JZyJ/E+n7w2Q07BgQnoM8Y6NXeUTzvg74zkLMP9o1hfQzIALpWB53qUIV80+0U
Yn1M8AJ0OAfbj2J9EX4+BDt1/TTon8XeLOxYwJmt0PkQeC7BTzOg0VhqE7gu+JFgWHBPsEXQ
LyghnuqXhmBQUERslYfmQ0WwTZAGdK0Mf/UKNJd7BFcxatwm4I9t8HMdvBtYG8Z8H7AE/+wC
ljHauUGa13Gen0fgc9UtsQ6k/sO4Cr9rTE/C7+dgl+I8fL4e1BAzh1itrOP5Hs15n+k+yn6I
kP6/DSOA5qXm9ADQIOSAScREz1kuaey0b3wPa19HHL4Lvt/B+EXQa0183zfr/j7OaP1qLmtf
036jdat1b7WrPWzcN2tjF9amQHccz+M4PwvovvUPrTd7T2jdbwOfWR/1OZ1P+6i+doFWe4X2
0hnooXw/7ps9ag5npsFH9dN+sMk387EBO7fDB7Og0bVnMDccBY9Rskfr/wDsOgEfTYPPMd/a
q/dD9iLOHMY56/kz2D8E/U2XGbJlNz3P4/w49J2jWMzApzvAZw/0sv6vfBawdwD6qT+1v92A
DycxzkGfMfhJ6Z6HvaegywHI3Io4boGcMZK9BLqt0Pkw+O+FnifJL4ch6wxsXIJfJuD//fCv
vYMXwaMBmRpLzdte+GEzbNA+2ueb+XIC6xXaOwi7S2Sr5orWSxFnR0DfB94j2K/j3C3f7N16
bl091u560CfEFowN8DSYn+cQtzHYtQ3rqtu34a89OF+nc0uI43nMT8Lv1teP+ajGrc+oXcPg
oWPaRzk246PatjuH7l2GvyYQ60Ef1ZrVx6yPanwHMAge49D/G76ZU8PQWXvcu9BvEbZojWrO
XIA96o9X4SON9zX4YB77J0D/MkH3jkP2go/ucF/1zX44gTjvxlz10Fy44pt33NvQZQg23fTN
u1gZsRmF/aPwt9bD53zUO3fDZuV7R/AA4x3f+l74qOvrwf1g7gnruXu0Qw/G3/pmLtdhI8P6
meb2l33zDnfXN+8aU/CTxkTvpFqrWd985+k8jZh0CwrYS2Ou9Jq7dn/S+9dnMXeBnk+7Y6Ux
jmFu92SN/QD5rR9rOn8Dtuo943XBZ3wzx3TUPqF3V81PzZvLoNN81PzTHD6L0Z61Lp4D1GcL
OK91ob1Ea2Ya+lh/0R54CH59AB/avU79o/Xztm/2Ps1LzUOtpznycR5n7J5h/s3BZ2msMb3y
LsL/RZzPYM/OpILnMmhKOG+8jK+dMbl6rzuNtXGMDZy1vFDZWms9iI3yv+SbfaSKMybX9FTe
JyG7TDr0YCxjtPwawrksnkM/WCzStG+0GpcjiFMG52zsh0zNpwrkNsA3B9516JtB3E2m2WM2
ZDEv4mwN+uQpLuaHLPHJYd3y/zR0KAZ2mM52xmwt+Cg/cuSnbMx5npteKR/lkell/qz4KIdS
xL+L+Jg8y9c0Ieej2jb9svC7fQ8mfev72nKKvxkttzl2xjNJo53nkfMiRTwzvtUvViOj5Ff7
3su24ZWkOdtpvGyN69j4ZGgvEwP2I8vlb1Drp3mis7NJkp8k+UbHeib9k/FIBrzieJg8G0Pd
Qz+bPiFd3Ll0gAzZlPStceD84rxk/bge0gGP0KYs5GRozNBZjn9crrE/wp7KecyxZd+bnFCv
gn8yJhzzNPFP0VqW6LgHsO9DP4R5wPSJgD/LDelTgZwwrmGexfGNW4ujZ79zviZpjfMlE+zF
+SLjW/MxrgbCZ45p+D0S6hrmT4h8G3lhHwl1Zl35TD6QG8Y9zt64/sB5FRc35pkI+MbVd2g3
99bQ7mRAF9ZuuBYnJ85fcXUd9uB2OnNtWC0kYnjF6c3+iOuDHK9Em3NxeoY1GGdTnJ9ZR+4x
T8vVp/kqGUPHMXha7mTb0IY1FlevYa0+LY7m2zA/2vmsXT2GNRfng1TMelx+hO/d8L4Uvn/C
90Foc5zvwndNO7+F+3F3t9C2BM0zAb3dle3ubzT2Hq/51ruqfe/wd08J83Jgu+3xXdHunnH9
PYylfg9sxzN/K5WwVvDRXT6JuX2P2FqebCv5qM7yxFNldfvmfb8BHvoNOkpzs2Gzj+qhgWel
02/KndChTj4yW8xffHe2byv7njC9+e5gZ8zmCp3jbw2TU/Ktd6wUzTPBWi6Qx9+2xjcREzP7
PuHvEfNpjsBy8yQ776PczpP8nI++OeLyne9+nE+WC5ZDFcRgwDfzdwjPDdhTw96Aj74x9Lv0
m6SPfUtyHzH57Fuu0fCez+/BPORyT8nTvEi+DHs/17vxs/eA1W/Y7zKBrDSdY5+q7aWAxmLb
8FEdJomO76RZ7Nsz6xL26hT8an4J74esYzZY535q34QVH+Ug9zTuOXYP4LwrEB/uweyfHPFM
+yjvTI+w74b+5nssv8+Yr9VLOpizf8P3USaQoajRvOhbc5PzKbQ94aNczhOdyev1UW8PY9Yu
vj20VvNRzhhfzvnwHRfWGvMO33UF8rGtlXzrvSxPvKw/cC/jPmIx5tou+daezN+0/M5KEy87
v5/WqjjTB5/oWMHIa/009oOmn8A0vUC1zdiLWFRhRxVybF3HMmTU/JP1wD2XfcU1aH4u+dZ3
hvm8G74o+tZcWSY+astO8pu+7/V9uxX7qre+Y78mWMC5YR/VYwX7xrsOGrubWB7kfWtO1X2U
R5aXpoO9k7MkJ/z+y9Ee+4lzwvLM7iTMl+9QrF+eaMs+uhfYWpbmKdovBNC9gcA209vuSWxv
muTze5bvcvzeKcH31s+sjsK7ncm1/DfbrdbNJuMxSfqUgE2++Q7X/UHfzF+tgyrkDCKenJNW
MwXoOeCju5nV2zDFoRdnbazivOWunt0BfSz/rK8ov+2g6QHNpI/q1eJc8a19ye6kdd96h+Z7
lNV6xUd9uEr6WeyroDHf94De5FZBWwE/i3ORMEY8LN/5/ma5VSObcuCXwVnrOVXY0odx2Ee9
p4aR87ron+xRPYib3Y+Nf5GeC1iz0ezrpbn51u5gdg+zvbKPcq0MPbI+yrE8wWJY8lH/6aV9
42M2mq5V+OLfhJfbchs3FkUHD5GaZLPZpCjSimTLShxnaio1eZv//7Rxl7EKq7dA5QHFJoBz
3+cCdD2X1l9Yxjx71HRq9kZ+wGbsAsfYO9W7G/Fd7r9VnuixyH0tDWPwxobl7lBaPSL/LvX3
UYuedlVMZ/3yviBGn6r+T6XVFPAAVpCBfPoQcfObz3eIOTUSnNMPmROddyfJ4m1pvchNZDyV
1sfID+oG/6lz9NtRZ+jCPACGiT96ovdcWk4xb4HZY2m4PygexjlxmuRfZB8knx6BTPzpfrPI
/yLf2TfIRj/TXsp6Xhi1B+6I7SXomG+xedZ5LmyZJZ8YuCY8lFZ3TqX1KHolOKWmbcp7W9yr
H0RPzXiUTPqLcTWVPv6pBWCe3mH+1uMsmdSna8hADn3+rqzz5FQaHqDxzJA8jU3X3IvuuNaT
Y9Qr4nAsDTPUTucnuQL2l/1n6U2tgq97luszOoBb4mXfW9/H0uakXg4ctE9cZp2zN4kWzDj+
5Dvyx845dMYFbwzXMHJkEs1eZ+y7dx3izDOx79DfPdM6/5kH8B11l/NPkgFvcoQ4Oj9dI4gT
PJ1zjjfYdxypeRfFLX0LPfXAtrkve9ahnlCTWJ5Dlv8vpWH7UlouuR6RN49l3SMvsU9euMYv
Nm/El/4MHXo86ZszcgBs0UuZAcAyMd2VNo8SD2Tyu9z9ra7XupZv5vllbv+u/bfS5vYvpc31
fP9Wz94qzXL2tfycLb/Xe8/1/Gv9/lzXa937Ur9/r/y+1nPuvtX9b5LxJWTC80W0L531XPV9
jr3PNQYv8qPzzTMN7xlmcd5TfleRH3vdm0vLZfY3ot0F7632fObFHm++Mfazdkw6nysNOmzE
d9LeVN7rsdP5GP+tOzwP+t+Td2vtxJ81SCe/i0bJsI93pdXusazjM4Y+m9jP++TyKJnJ13Ez
3/SVdXDujqXNFr5vmbdst1+njjzOvAd94s00Q+yZNuNoO3uyjfeN7hG3o+7Qi3ZlHU8WNdB2
7uPM8U19R52lHb2YOiab+Ga5Dhj36Vu+J9H0dOv5L3Oix/cQthtnH9WXqaxx4pqR/soYD+LB
XGNf2a5DeY+7fVnnijFmvbgz6w711XvJP2uPc8W161aN4j9z8EH095LByrwxP/tu6Ni4LW1u
6tWv9MVBZ/uQ06txmcuu1Ztqz60ajayhtNnrKnvsHxYxYm4b6y/8rmWNjRfxcw2g/oKVUTyz
9+BjZifXdb9x8dcl6ObQM+v/VvT0WWjPZV3PM+eyVzsu4OChc9c159ChQeY+ZLp24bt9WePK
/k9s2O7M+5Tn+ByD5qMZAPnwGoOuJ/sWz+zBzA6Zg66TQ435IDrnjGnJ70G0vu97xw9s9soZ
0viwfraZ79Qj48c8MOh++i17ZK+2j/rOvnOrPmUNtL49XXNvH/alb+B3CHmb0o9J5rD16fVV
z2a2M+eOzJHeDJF6b+MetfFQ3vsj9bqFecelh5dbdjqPHbOsW7fOPF94/soaZ59lz0w/9Wy6
tYjhrRkncWb9ps7ZR7loXZfvc8Qz+2wvXst6CJ5Zz3IfH/dqnn197PCwzswm5w4f9D+X97Fx
/ubeNmjAX+Zi5mfPZs+SmcfcO5b3Olkv/+/JGYMPPsk8zZy1/yx/L35H0SVWnAu21fqSt1kr
Mhbkmvf2NQ5/1uUaZrp8X7rG409s9bvU8zJnW33n3O83GTSHsNXyl9nzQTrPurfQPdZf5irm
O3J41Dm2TPXOXNZvhane3Yv/JJ2oDbxFoWHG9ZznswfxPuo+v3zzTnqodu3qHnk017NBdCfx
Zf4+hm3cnSvfY73HHji5lPX8mzM2NjEreZZH76v88FJaDix7T/XOuer9WNazKnZcpROzIzN1
zjZH+QN9kHmqMpEBVsCB31J/lvdzqmsQvoKW2RkMe4Zh9mDdmoXo8fT53mzc63OeP9F1Cjm7
srbTOvvdkD0p53bXhkn7t2YZZH4vPzG0yP5W4+BZBryc6j3ejefS8L98f61+/6s0zIDxl/p/
uf9WWs48BO+teJ5Kw+P3su55X36sP0IPdDA9vE+SeQ25vke92esOvNHtIJn7yvfTj/W5tHyZ
g/comrfSas2y/iMZe52d5SNqy7G0/F5+f48YOWfnkH3q8L+EnZ6Rz3U9itcu5Czr1/r/m+zF
Vv5PcTaVhodH3f1eWh+kP2wqb2auk2hYqRd8weAQ96g5Y/Uh8o/6pr6ApbNokPOss4N4Gx97
yUcHYoGfL+K75N9LaT3JvYZet+gG9unPyCMuU1nnxkn60htsn3OW+k4+EUPwchFvepVxCr9r
Wefiq2LzXBrmwbJxcyrrmGb/wtevovO8cAj6UXydi/YPtl/k0yl47fWfmJGX7u3GSmL2WloP
Q6dfI06z/GOfbCv9X1Ue/db5u+jwb8lYzn6rZ89ljVV6xEL7rdL9XX7WJfcO42yo8Vpo/yt/
fhe/OeRAS81A12tp9ZL+ROyfSqtB4HlXdTzF3qv4UxOvpc1/zHOmYT5yPuBPeir1Fh7MU+QO
fRZa/E8eHqTrQbwu8hE1YtA5eY4+R/2ywAg6gK8vdREzy6XGHUIW355n5pCx7PM2off5rWPf
EQN6ds6Fnlk9g+2D50b3LSffpOg06dtvTL8JrNskOs9ss3j7jTd1aPzGyuV99OT/Qd/5zk1b
Msc996VOPX2Yb/HxLFq/E+HvuRtMz5KL/vAgx0ed9b6pn+CXveX8vjSMfaqL2YGe9qt0wTa/
AT0Dkyd+K4L9h7h/Kutcd26CGWTtytp/4BqZnsefSqs1o/gRb3xOTaQ+OrbuQ347OFeW9Spd
vY8MvyV2nTvg2XoZb35jWH/nUr5Nxg5/v0Fsx/6Ds1FnritD3LFd3PO7x+9V+9H1yLVjG3um
tX32I/kCLrDd7y7mEXgxsztWy7ov6xx2v6K2815b/lOT8YvfgVmDoMEH99KB/jOWVvtu+YGZ
wPHaSQ45Puv8UGno7eQzNEO980tps8++tF66yHIvs3/JXeZ4z470gn3QUFPca7yf9o6Slblj
22fJchyG6m9k4BdqILSPiuNJMbNNri8Zu7Trri5j+1jl+j8+zzpBDlHvjGP3Y2w9iMb1kdwF
N5P42o98n8TPeebaBA6Yl2fJwTfMo54L4Mv8dZT8p7LG46b6D76utcSJWAziQ23/V2k5DW6o
NZNkgFHsdj3KmWRQvNDzXjYNVWfm6lm0xB1b7Fdo0XEvmjvd9cx4Ei/s3GrfMd+LPzqiz510
5N65tLnbs519bfwQm3vtkV8PpeVI9kPjxrH5pTScwRcMEYOj9lmj5HHvvrS82AWdsQkOqM2D
aI9hI7TgE70f6jm2g4+prGuOe797611pOeX65DnVOQu2yaOzeO4VR2Tjd3Cw0T51cFvp0jZ8
BdbvyxoH7B2C/zYW/juKh98cxptzzPGCzjzwt3HC/p143CuezvWp3psUQ2io5cbFfWl4uYu7
8HXOU/Pwq3W8E8+Ufy/51IKj9LgrrVaTL2+lvVOR5ZmHfnWR7/ld9q6iYw7wG8M+7s2K7l3G
mPuPY0YukGueIy/67xnX/d8y833lPgn/k+zBb/uy9o/fffaPMe+5Zlve22c9Xet95vkav9pn
nOMXv1/9/1a+beJ+9gTXRtMMQT8EL8u37F2Hfihr+4cOX/eSbewR19Rp1/llfnTP8lvBbwPP
PeiV/YKe57eK/bac38V9fzuGg3h5nrEP/F4yPoxzv8P8zvEe38Ytee9YQO8Zir5trPVmo56e
nhFyfvLdU2c/+0TGeYjfTdBlDuSdHvZ81/FIXPu357dbOXLLJ5lr3s9c7Pl/19nzHOS64XPj
kRnMfnHMuZc5YR/0/Oxf50/mQ86DvfeP63fWHvs3seC7vZrb45X1tbd6tbVnS+LKPKyHcdGT
/VFN7vn9I/uSF/G4pcOtnGcu6eVtxqyH53/yD3vuqx/Fpdfzev0w82+Ic/vXWOjlxK1+Zd6Z
K67N/xRv56Tx8k/f6atdZ3nWyNxxDbzV88zrFqa3N+huxdxzfc+nt2Jqnd33DsEn+7D38w2Z
d3q45B7vJuzs4bU3b9junI9sq+fqpOlhp9cbe70ndXD8e3XMceRuYm6I822HL3Rj7J/0f5k9
zh15y/9PpfW0U/1l5t7pG/l+32TeGTvGM70KHk8/1ueOX/PNk7hk4acp+EJ3KOt5C9778j4G
xgLzrOvEXqtnzxy+sf2z/s+in8t7nCQOEjMbyTxLRsZjVByNAcvL/85t5xR7s+Rn3pn/Nu5l
fHM2se7X8hOLi87/qzr9+WP9Xc8fy8+3q+fzJf7/Z7xMd+U2jiiMAqwhOeSQnO1uAmTFlq0s
QvIAef/3yiVUB/x4pnjjHw2yu2vf+zP88ZxwX/L8Oda36XPqcc3vJe14y7PfAbfs/5Ey3BNW
cn9PnN8S5oJ1SxrSY6HDd+Yt1nxSPLwkj3ve32ONsUvqLJlvyVNnU6zx95TrBjsN0G/K8z55
0F6X/I4J+5T7CbhX4Iqm6P+W57LdOc8vsPlznp3zTDEnH8x595r/99wfQWcGnPL/Kfdn6Lh8
v8Lm57TnBJu9AO+S92fwnZPWCTzf8mwG7jVlPMeae9L/DjjG2t3uJDvl6WONX+k9xRoXveFL
5mNs7SQ7qwd8Nj2JK5yXtO/V7uSXq91pPuhja5uz8VKOi4Z0EN4EPrdYc3YEXeba8v32vv75
vn7Az/KdfK84UT9basr3WOvsCDvpqzwVntcy/9f3hP9f899rSGc82BN8lpB8Y6x1U7WPM5Pq
4hTbOk566mecGc7gwZrfA4dziWiN8fgeIU9/yzpd50FY6ejvrGr+5ExXzYucuYeChmwy4H9v
9uiBM+z8U3/aRXCT4VCe0Xj5XCGZ+4I++2lvcKQ34HsCnN+JXmUz//fY97m88h3zoLX9aL73
GbHyofveZ+PBYH1Wq+YTwn8UExVuBVPJJ93V66q64os6Kb79nSX6HhOMR+YRfe+2JW/O6KI1
Gh2fu6kX608V44QnD8pLvwwGX/nD8402q94PpEV9p/g4HphrfEP1O7yF4zOz27mqmcyBvVlb
8UD6le1Zd/hG+H+1pIoFr4HUsY/tu1fnHqNtbOObtYh5O4Ae+wH30q8Dnb5YrluVy14PKl95
Xs2Ar+rwGFuf7OVHVTePBksbeD0gz73aTFpeNynDyXDkQ/Yowi/fSwHD/nuKra/Z09gbP7LR
XkwfwYdzkPcO+qKyt/cQnrktFcOKD7eZ1wXyneCfqm52RoP102Hoa495+qOa0XwOrWpN1ad1
1hb0PE4/WkNsZ4NlNTuwDud56We+xp1z0a7wPD8rf7GmVnSlj2g00KUtcNt4nJcagxXuyezV
x6OdWB9a0BoKXp3RV6w1JgNlb8HH+xz1r3g5nUX+A/SQjm2xZMvebNzEo00ZGy7TMbbytcZf
tEbgMm7Jz3VljHcGSxkb0K70PBj80WhUvlBeOr2D8XK5mtjGi8eG+9Hpk6fHgO9d397gKn19
OQ2vZYRz+1e+cDvJx4dCBve31hPOF1k0+4veW/yMixv4avYUPmu/aC3wr4X85NUAb4YvlZdL
n2bvZB6RhmirxowGK54Ho0P7deAjedjf1Wv35u7J8Kkr68w9tn26i8e5Zq8WdAV9wlU0qn7n
fbLqgRUPh92DkS8m46dzzp/EGROnzf9TPMp7NHyfGVnX/4S/brlf6F6Mxt7yGclnKuqwN8vq
/1rcV/ZmLGk2pJyCP+B/keWP9/XjfX0zXpXsshHjcoxajypenLbw3RaD8eHbZqkzyvkp/6dY
31Zz6jHF1i59+m+yNQB/wj/16kFjyDvP5QH4Y6xxeEp5hHMymprJFLOj8ZvwP2K/0LgBX3Wn
i+3MSDscwJ90yEc2EY0+ajsx3mSvGfuj4Xs86Zx9gW8p2lv9pU+d5cc578+wG2vBYPzP8Al1
Fk++FWVLvrP4fqENyIuyi1eHM+k/xtZPR8BLF/Wh0fAVSx5z2regRV1pY9f1VCz5h/WUMe94
0tN1djvLtswBt7Mvxpn2zEPqsvyrllFfpz/YP98D0p9voD07MCa6eIwP6cqaUMWb7NWBdme8
T/EYa7KtfKX4Ef2L0WR8HePRdqy5tBNr2xxr/i3fc2ztoflrNh/KZ5KBdU81XmdtbOsA7S9Z
ODMwF3rD4znjVHet7ek/xol6Fvvhyeh1wJd9j8Blb6nmHdFirHLmZU+oao2+rA/M5Ra0tGfe
ShbBKSZ8Fj+Dt2g1dtbHo/xe/0bj67naxlY32po+JUwDGJ3TtqyfTlNzpGRq8C9bVYtz0WA0
KQP5UE+PyaoO8l7vNq8p0r8z3qSrfNBM6nGknkO/sKcfwU/2Yszw3cl5QrDKCeaH5JpBhzWC
/6x1lJM6T0ZXuja5P8B+yqslpq+m92S03J+crzirdvADZ3HFvt6SzEnF0RDbuOcM3+OcurNP
6fxg/Bm/lL0xOop7xqHPcPQhZRxxLns3KYvyatl/im288v6Qd7JRCxy+YWSDBvzFj3p14NHb
efcX9tU6Gk/eMRbb2PpvbzWxtZXs8NH7sKLr8JwpqrmC8eaxVs0gjPEBPEbjwdniE/j4m5E9
gX3wZPR8fqVuPjv4HMkYZc9wm1RzFuG4+Lby/uezHP8p04wzyuE8VX9kO84IpEnehBmMD2Xy
+Wav1ig+aMu+gP/ozOPxVJxNBQ/WT59TqN9k59SZ8eD9jDWTs4HDcB7ymZRxX8l/At3Fj6+x
jd3l7A282FcZW+oL7N9nnLN+qy+dcKZ1jbW2sj4e8uwQ2753j7U3qne2xdfvPhlf9vZlP8c2
X9gzVf+usDvnUPLqcP8J/DUj/JJ2+gR7P8XaJ0hHOPJlj/s2ZT5gP0KWLra2EE3ZUz2Ife+A
vXSgzeRr9pkJ/Cfg3+NxHmCMicY99W9jq+cQ256rmFvOv0Y9ByoubrGdC4R3MD7URbMXY5F1
yPsRZ6YWdPWvfuO9nHVE84VgWFOW8wv2nNNYCzlDtYnDfum1Uj1sgX2OnzFEWyneO8Ayj9ti
+fxAPwpHcp1h50NsfcRZ82D0Fe89cHWvN2ATWx9Llh40hFv1lMlgm9j6lbKSXmUX6s48vBod
5rNk57zGHFS99Teu8p5xJnrL+oS7SifKQDkORo+xKh+xFnvNE40zzry2e41h3SIvt7nXeLe7
n2tmX+6+5Zl8IZ9PWEu8font/HVNW59zDdjLV5w5lavVvfY+C3O+8dWnDHPUM416xgk4e7Sc
bgX/S2xzpDE49nnpdsW9zmbA8V3apZ3pW39jCJfz08VoTEa3Bb8OdMRLeX6Jdbah3X0G7oyu
37kPnTdhnowG44A0FUOazVo7/wi/8m1F33OM8lb9w2PEaVY0VB/27EuabWGfPdrHAm5PpooW
fV71sr7g47np/mUf39PBefl857y0ZqNxNDptPMpS+bLbwW3jUUbqOBq+L9dTs6tynm8i1ZSq
LvBdKp6aHXU+2PIZrQeO56znXpWj/JespDtir/feZDwIO8Y2dpTTfKPyn29Dt5lkGuJRH81H
ssuerm4zfzfyPTuC3im2vujxLx/Td4Q7Gf1KviG28vfG23uP5KO89JP0nWLr0724dX8stK+g
N+G8N3vTvr19Paaq2uJx+FdqaxUD7JW0iXJSMlxjK6/HWxOPNmUscr6dorZfVZ9Jb682e28T
/QH8Hb7qf6xdblveu//8jHh8U1R5WPW3Ku4+umdeVXhDgSdZORtoNvVaczNdfA6WX2U31elb
bN8l9zz3eX0Gv3M85v4ca31gXCompcOEsy5q+15yPZtfWGMuuHvK/d8h38LnX7l+vK9/v68/
3tf39/V7rDP3AvcGfsv6G2i8JP0F/tf8P6WdXg1vznPJfY+1vp7S1l/z/Ja4X1Pme/IbIdf3
pKW4uSTcE/wxx7a23lPWW97pnTLg7AY5qc8lcZ+Bu+wb3IvvObY9UPCs0YpJvTN9BldMVvlT
xQVz2/Po9AFN9mCvy4IZY1uDSGNv3uC8qbmE84m/fTQbVjWSM+QR/8zDvf7xET2dN7Gtcw1o
N8Dhe7CaITvAu0zHqHWgPLTZ0ei2UdvhYHYejLb873x9/mL/+WhO7uNRHp4di/u9WZt+PBYw
rofHk8fyXq60O98qhjW/6l/1Zsn1/8Ra65a6qTp7ybOlNvyZ8i218Z7fLr9Lvf2c8LeEv8Za
Rye7U435HGsNvCbsU56/AP81769JZ4i1pl1jrbnMBZ9PhFPNGf6u4WxxMhzNqvQH5+Kh4K86
OANG/DRrn8BPPVNvL/pPtXg0vP/Gz552Tpv18ONr2v0lz19i7V/3xDvm90us/VF+Vn+Qf9iL
BSfYz4kv+hfwe4U8c9JST5QM4jXkveLlGTTOscaHdOBXvVA6v+VevO+gecfdstc8NMJumgXe
YAPaUDT1pe5nwD4lXck4J84QaxxLHuWN923ZbI51DlFO/mq2UX6cY80X3YmfZONs/Tnt4LbU
nNHk2Q34yulXyC8Y2foFZ9Rf9HV3SR4ep5qD7kZHX8nrvrjH1i/CH2OdhZSjla2ewJezlmqa
bPWEM/n+f5yXyXLkxhGGIw8igMbe3SRnRutYsqzQwRf76Pd/LhGh+gMf/s4COT5UACjkvqf2
TuWz6thzHOuR3tkL1thnUtWvbOek/NcCr/6l3snayN7PntjEsc+zR/luyb7pPYo9zullPao2
f7XGx/srYVQnKbfbirOAv2fzYW3uok187tM8SFl8/nD/ZbyzI1uvBfYpgaEdMll7g+Wc0xsf
4nP3/Ih9OCt6/LnOHejTBi7PCJiM3tls5vPVEEfbuL7UW7Okcslha77M4pq2HhOe2Tdxx4SX
+8Vnm0yv1mi7rcY42kU8pP8QR73pZ87gfHd46eOzks9SxJ3MTswtylrLLT2l3wS/DuDBupnR
JTz18fmR/qCdOL+xVtPHWc0dKnz6qMtBONrM7as+5XS6hJbvWlkNOTsd+Pl9FtPMP7fBxWCz
WiK8r2/nt7fza/HBb/g3A/cKXN1rRhpjj5GsXmV9xOMg829md49x32mnE14864lvLsaT8ZfJ
6b7yWSGzQZaDXsupG/08Gk+XP8sJysw8HRIc8n6q6Os9MPMdewP5ZL3MaXr8uJ0yHLcTd0/m
s/bILaY1f2pO5NGsPsW+E91izz3Nr4udAe/iN5b3FTREcy6w2mn1LZm126wGd409N6/lTjrO
4LeC3ghcwk141z/pIJqa4xeDkz7yheixPs32PeK+B7xkYIxnNY65IHvLLh7Pk+F5zrCXUja/
o9+zvkhZta8Mdj/Fo21oE+aIx7J8R/0Y18yHFXAt4BWLg/Gh75g3tLOO/pEOayTttH03ZlPq
POE+013/l3i0V3ZYDzKeYwKjeJsMRnejHbcH9XWY2eC015LHmX1Fo7c7xu49HuemTJce7+67
M90ao+P6kkZnuN5fxoSWy9Xbu2jOwO0Nzvnyn/ugpuuEu0sCPxjfLh51yvRgbs745jM7tX/i
1Rlt6kq4Cbz1VB3qEvqC51zG/0OCo37huUR89ZMJ75In61tjHHUWjez+TD76x2sDffsU++zm
ecGZyW3TxbHW+8lmUOF7znKmY44S5xV0sh2A/Uw6c6ZkD8r08bv35laepxPcHne+xzr88g5v
9ouab2iHJh57yWb7T7Cd4pA+526RzeEeW1kMsJ9qL+CO6Dp6vaQvt6O5bzZc5tum4y2OMeh9
tjZze40U/wyPfqJeTezzhvtfNmggl/LvGo8ydeDfJ9+qfWs8+qAFT8/FG3hxJlRtz/zSAsbz
WDp5PFKXKY66C/dS7lqjxbu26NgZ3zaOthJt/WuKbZ1+Jntn3y3uGtw/2fuXRGbZ9AlwT4Bp
cP9deX82Og1sU8PN6Lr+iscGd60dx3W9HVa9szV4vdd85X73XOigU2cwPJTnye6fQLNL8K9m
C9m5Td5H0HoF/Rl01cfdT5lv3P4Z/wY8iDvaf8Kv5bnYPfkOiYxZTPlzjEf5VQ9cD+fvfqcv
9M06JdiX2HsS5ybukVPR2+cf7pOcx872lAk8CMP6OMU+U6n++5zsMuj9Gsd+RhkmvPueQ9mp
j+8hTlffsov6RmYL8vVeR30VQzPoEFcztvLB+ZC23unLJY6zA/kIZsZTvcZxB8CQh2qMaG+4
t9jjz+dJPTWPqz/3yX8dl+Mfb+eX8vwd8ms+2b6fY4+nFTD/hPxref4r9j7BHeil4L/GPg+8
xJ53X2KfnzcaX9/O97Dd9u9zwf1a4GbwoI9fynmFv5fYY0zxrj1HNmVMUP5rsYdiTLUl2wE4
894A43HDOsXZ1veENY5zQDZjsz4p3iRzb7CiIZnaYivGpWY27STqL5rV+0JfPu+KHe/A60CL
cskur5CHcc45kjZtYSf2bM7anKNZW+TnHv9Vh5R7pEsZOHsSn35yGNr8bPfhDsG6qlhjDfNd
hXcj7gd7Zzy2lX/MU/YFzseE/z6OuXJ2ujjmiR/pMSX3/J5AS7uBYsd9wjz6M46zAHnRX1e8
/wdw/wYPxZBmXs9F7i/ccbhzCYa9hvge/6w1mk1+gf7y6R9FVo85yjLFcdbxWF3xrvmH+aL+
yri/xp7f6qsuWy0XpBe/SZe09HwGPd8zszMA9gI62Y41JPzkC8rGOsUa5Xo4L94Tr0vg+8o9
ZfvIP9Z53b+aD10mt0EbdbvV7J7JcvbP66/7kHbnexZTTkfxRL6ah1y+TF7+c53dJqy3mS7e
J5jv/D+f8PVdRf0v653K3cFgJCtzqDd+HlPKf9HV3Lfd/xh/9/8VMqwF/n9xnPXu8ThTs994
/Zccv0OXDffn2PvCCv6qK9yDvEdLztnu1TvkiwU8hNcBVnDkyR2H9U16aO5oAUNbj3H0M2n5
/MLTJbxbe/puSXjvndLTe6X0ZbyOCUwt3rc+9V/4kbpyz+NsyVnA5wny4f2K5wLYyWgxpnw+
8Rl/tvsr+GazjttbfLRDCXc1PO6f2/en2HeUEXiUmbPd3Xy3mGz6VtzQ9q77CL4eC9ynGDdn
/hqMlr7pP/YuyuHvil36V7S6BI75Tb/IJ4xl8pkq3xPutGvIdzP+D4bjObwY/d5gRVN8VPNF
n/QG45vVCuUM5aeO9NNk/9jPVsg0GP8pHmsA9cj8qu8uHu1NeS8Jvu6pU280RvumnNPJUX6p
Z1Ge2lH81eC8/7gszEvaknXD9ZBsY0KPPFQjXF7iutyccS6xxztjh/WVe5brTXjFEOsSc1Tn
E3A1w9KG2/0L6NDfzAmPxZr/avpTP4fnruG9scbHY0+wnBU8Bmv2JD3KOH7gnbVQT99Xna/X
Naer+xv8TJ4r+LC3UJ5LPMa5f2c29drRV94z/MWekvG9nKd8zE+3z8X+ZbDSvTO61IuxQ1+w
p2XwHiu8v5qPe/u+FrvcKv7mPEf7sZ+rxrvsmR3PdP2W0yd4Po9xr/T4834uW2U9ZTS63n/d
z16nOOt5T93Oi+lwieNMSZqqI6vxu5a7GbjeT8lDO6nTl3xex/zba0sWO5l/uHtqVspmGsnH
Wbwmq8diNo84bZ9J3Dekx/mzT/j6vOe8s5jJeJ/NUvJ9pi97GeFruyVrisP4zPze6Y0v8yCj
77sI6+UYR924s9bgPTd6gyW+7x8ZHOfbj9jjYnjO02cV4jFPiO+2c3t39q76rFon+hejy1m/
w+mNlo7qZwta27vqjHRayvcax93N5ZDMulOOL6bHHEc5SYPyigfj0HmrfvDJvsaY4d2Y0L/G
sW529qS8vf2jj8c42pOzOPuVf4vW1exIPXu7awr8xY7HBOV32tJJfYa+Iq5knIyG7gaD99rV
GwzznHKwl9CW9A1znba9l3fFHONBhzU/s4fL6Dme2eZu34w33d3MD0sc42c0Gp7jWa50cdSP
vqNf3Z6MPeaPxwVlmeyeMnf2rzM6o90NBuc6so+7vC6bfLTZ88V0oi8kg+vJf5SFcUz+W04r
57TPkgfjlXHLujfEXn/1LjvpXU+3K2vM9t3gn+Rqy/G4fO/UcsLvVSckI33lMSC9n0Gnw93F
/Ob9juezyeQwq/lcOTfANl2B+wGwPfDvsfc9+ou+Ff07YPo45vgUjzIxBrs45pTr5DmU3fl9
lsPZd5PgZXnh/e+9k/XeMzkyHV2/TK4zmTN5vEaqllNPf3q98Tr5EZ9kfu0rMBfQ74xnpldN
92xWyOa/M5+d+dttld1nM3emR81fPGM86lGLGdLJ7O32Za2fjeaWm63Ry2LObepzSh9Hf00n
ctfov/es5f/ZneOfxfN7sFlsqS+ol8vGnMl0x8MdKOOhWYz2VP/I5m31KO0QXtOuxrMpcI3p
tMRer7fzGnsfFP8GtJfyrfgVrsfba+z9k73C41e612or/cbe5f3mzKdnJ6PHmih/Z7jcJ+U7
rw9nx+Fu9i07/fwOHa/tjAXFCu3qsEPl3vPda96S6ECfjQlNl02zIWVz2Zt4lOFq394bWqNT
s1lNx8xPZ/QyPYXTfgBv/D//9Sf0dV+za9bLMz09rr8kvLo4zpLKIZeB8ZbFKOHle8399OsF
MMzJbP8QnRtodeDntDu7a/CkLR2etZWwjDXVMK8l7ifx9jiq9TDqwlj03M587P+3ujbhe628
f8uhjN+SO9/Kh3OK14IB3zpTPM6WczzG7VZvPplMNV1cjzn2PU3/1Tc3Gt/FMSYz/5zNXppF
PC4Epx1NtYQz0wQaWY8TvubGEe99HGNQcc8+z5jWnMS5xfk14Eu6nFuZcyPgRZMwlL1PaFMH
2YjxUauPjdEjTdaBCfBZ/rrfOecpB2kzn284HxL/YvDsy00c/cMa5zYij6zeNZHrojihHq7X
9tQMobPFyB08n+MYm+4b2Ye5ztqpfKZdhc++eovHWYb9TDx0l+UYbUq80e4zHw72rM0lWw36
4e38VJ6bHi/FZg103+BW2GEpMHO5b2LvRRvsNfb5syt37DufIe92vhSce/l/i2MMPP/Fernk
SJIUYVguqIzMiHy/q7q6erp6NIMAgcSVkFhwBC7ANVixZsGKBWejQm2/4os/zSOrRixM4eFu
L7e3h16M+RNsn/UwxSZja16GN5TwzmWcm8/wH2Na754jzhRTjCW9dxp8t6afdNmVYWa9lKFe
LILP3mw7r/DS2Spsqbrpcwttorvu4k6vZVzXs5pLWzBvmXfKkTX4yG5X7C/xZW1TrCq+VrbP
PFA8ipb5nM1g9LP4Mm8pR7NJY3wa4M2Nt2JEPvEazvmT63nCi/+u/xSd10+vqZxD2WdrcjNa
3/e4pl1Zy1iL/Mt66b7m3KF44Z7wvTbyn/3c5w3GBWvJCrSsM0uTST3YN7bg7XNra3xYH/0+
S6Nlv/AayG9r9Lyf3588FMs+P7qNunJrM/YX2dlzzOdbgc+TBK9fjOFsxjqaTMmdJfeuxYDX
S8as29zzQn1S+54HHqtuC9ZT4eyDp+5EHrW5jfE6tzPG4sn2Fsab9UK1MasBjI2p2kYf1mJQ
31nFP5ty63eeS2fqPgVz8G0qZ5lt7vGdApczdfYRmTUbtwmOy+MeZyW+sdqELoM2OXdfdOVW
91p+9jArt/fjjMe3hJ91wFmVITbYF6kH3xjqR9syzh3WafUC3mddxjnntbRWbzkbbbGvGjYL
etmjBc22jGsd5xbV5K35lPYQb9nY9ZYMnm/BO6ultKno6X/6WDWrMbmsc1msZDMG42xpcmiT
OejIl3aQnbwvUob71Xvk0uR4La7NctQn6+eN8eH9vEdRP8VJY1+tsxkv05H1NvPNVP1pkz2v
hdn8LFkzo21iT/sPFT5ZvRA/4c2MZ1Nu64rvZ3u1M7+T5PkedZIutMEfy5DP/Rv2x/L9XamY
U+zrDcaa4b6RfJ/jPBZegu5g9tuUIe769RPWPY891t5XGCuqJawbj9DrBTp1oQd9KxmHMtRp
1uMn0DdxNgM/2Ye1Ufm7A56+spX6C+sD55ZNyNpB1w44S9iUd18Cn/nIPt3zeYAN12WoDZy7
OV+K5wznrAOfyxBDJ/CW/gvIPJRxDDG+WL9kM8lblSHG2ENFvwU+3318Y6xhK6+3/h5c4Uy2
kwzu+zuvM76d4bDWUk/GueRxdlCv70wO+a7wFT9/S6kXUx7fE/4uIo74uq460/yj95VyyXlJ
7/fsCVzmwnjTr/Sn/MY4W2Pd7zd2/43Zfmn8SM8e6vNM1oun/u9Brb/THj6H+X/NfuRf80FG
l+1nc+4U3UdkZOA5/VEZbivVJq5p++zdQdx7d8/Os3dSVz5mhyyf1DtqOH7GO2Z6TvGawqWP
NobTVvbnCa/O+GxsL8uLLJ4yn7u+92zvtp2qn9Rtqj6QvgHP1tZe77pSv5PTuhyvA34ffztl
uG4LfyOdSp4vPktktszeCs6LevrdqPs82Xd7+BzreervHu07jyy3PKcp33XnbFerzbW+whqQ
xb/PWjyv6Uh+WexksV/j43ZWzclypwW+xwL5tLaeyt3W+Lo+Waxm4LH2UR7eU7K8ytbvqTM1
O2T5k9Xaqfyu+fA9NqvhuU6/pK93Rst4UFxP3d3XtX5Si5ssVt97/wyv5uOs5+nN4X00s6nP
r84rq1Wsvf5edF5TNsv6YC12OZd2Fdpa3nktoP5ZDc/unsly3KzvE2+enGc+XJS89mZ7GRCP
8ed92XVb2D/jrmYLnnlPnZrHajNzLV68/1IP0tVmg3uxRp08JrIYy3hn9vOeNLc92a3vp/17
cgl+qzhXPv9gcEr2CF/xFbxi/9XwiFvjcU/ePZwaLD6IX5Pz8g74Ulm/F2o0P7/BZzv/Fvuv
7+Ar33yzO74E39fg/TTBQ/hfYv0t/j8FvGJP+J9Nzteg72PuMfb6s3Pg9XvX+D4HPOH/Jf6f
Q+ZLnD3G/hPs1J8fA1c41PVz7J0D5xKyL8H3GTyvgX8JntJbuv4Qa8GnwHmy/WvsnYPXOXCv
8K14SrdH8JKOp9i/mN7a+wTZL9h/DNor5J/j378n6Eq8F5zTV9RB8q5lrJPudDEc7Z1MD93v
bF9fX0G7im//zzlF80tfC/v42+JsXYY629P7e5S9dRV8lqBRHfVescF+j3MIWYvQrwv91YM2
gec6SOf+u8P/MdbruM8x8HcBmtW24HsOnEP8n+J8Dbv1dPs4XwWvNs503oGv/LkIup7PLHBE
cwhdTnG3U/CV/6Sf/nXPFjIOcbYH70vgXgP/KfgrNhQHbdBd4vwA3x+Bt4eOTZztYn2CzQ9l
yIsu/hUvihHx15vW5x/5jT17X4Z+vQlgv+b8w/lY5wTO48LlO6vFOecMyvLZZhk66x5b0MxL
fdYiL+VLB/mKNfHsEtiaLrWZWvfbgGZl+D47T82S5K9YUrxSnu7FesDaQR/du4PrKVrO3LJZ
Hy/KV52tTTZ9K949jXJ7F/Qv5Tau1uVWH/LalLH+6uOMobXJZixyJpVOquXXij3W5dZ+tJW/
IbKZ+1xu41N5535RrMzKEBviq/p9wX2WZaiByoslaJuEv84Zm4pj5lYTvLW3T+4pnzzDV+xf
wnOZWR7U7Mc47MqtD0gn22yN17rcxugq7uf6+DtV+rPvZvHAf8+9mfHz+xL8reh4bhvW6zah
kd+m6pN6iMeprzPbLBLe2b3uAftwVguyHuI2qf3X7Le8g+fx/v+AX2KffbLH2F9/UM4f3nm3
9+hay+cslt7LN4vPGh7r6Krc1+c999C3z0XNIQ8GfU4vY91gbwacPf71bYHXVNazMtQngmq0
eK2DriljvTK+/fcCfMECuL8y2l8HPJRb/WYmo3YXP3swWuft5+LxUIaeRp7yeTMh755uDuqL
B+DNJ+io66HktuntzHjh2Sbh6zwy+5BPB3tk543p5rLY71eB67MxZ2rOKz5b6HxdhhlBeXYq
t31EdFv7l6xVGecpc1Qz0hH7/o6hLM0zC3wFtAtx3N+ck8ivMZosdqaA+TivyM581n/1PtXb
Tu872UFvRO2vEtiU8ZtQsA26XRneJ5qhibM0Xmvjoxq9w/kCtHonrMFT/ttBjw48/R3L+0mO
7t3DqQxvmR8AX5P/Hr7EV7H/GPocg88WcqQj+5B6LOfG/nspt/F373+qV7ZxJ87/nMs8nvjO
8PmV9D0cTPe54TRGzxlWMcpZuAG/axnnzazc5mdtfqjl8dz2ZgneqYzzs/bucWDdmYFOviae
+Lu+2Vr/F9DMkvMsJlbQI+NLHb22OW+Bz4Y1eziPLOb9zjV/eWzwO5ugm5LVVnCz/1r80HYb
nPnc3RpP2mFfbvX0vrErQ466vfytm+l5L7Ycp7GzBl/JdNmt/XOfPJiz5OM2JU+nkb35FmO+
Zn7KaobXtkzevoxrnueNxzTzzeeghdHW8sfnGNWffu112+Vq3df7WbmtPe/pJYrfTcjtef2E
vQ446rvS93MZ5qwdbNTamrNIi69oGty1NRn9/jH+ezr11ocyxMKxDP1+CZsswUs9fwmQHZfB
5xz4Pe/H4Hcpw/ypmP8E+0kG5xjGqfSSHaQPZy3qIpvLV+It+efE94/QpQV/6bGBbOojeTPg
cs6X/CN8ucS6Aw/J9BqnOcnrunzOt8C6jH3GnNfdNIfIJprxpKveP9cyzGbiJd94Duxhpx1s
zZlT/AUN1syjk91BOJqb18Zf96N9VO9oQ/qTb6Ud7rkP+6zLEBvy2QFrxtUe8rvAE477Wrbv
ZfZxeIHfGTeKqTNsvCvjGJP/V2UcrxvQ6N5X2EJ42zLukaLjO2ABmmMZ+1y6607S/aGM8+Nk
+qhG8K58m8pe0ncJfOYtc2oFOZ5bV7sbe9Ace6phXj9Ve2lb5vKhDPmjOG6MB+OANuxt9Zvg
IT77MrwLD2Vcs7oyzkfmMOup4k9n/lZVjnBva/+KSfZtgu7oPY1+lF359X230xo8fX5lf/M4
58ydzYeqL7uAZRnXA/Wote1LryXOOKNIf9mP+jQAn1O3pmtXxvdXH3t+g9/CJsrNNfBnsb4k
vmdtYW7objpnDe/KbSz0+L8r33tlH5fHsOMm1tsy1NN9rBXTq1hrn/1nifUWd2MNYU0SjXSn
zdm7eXf6bot/5bzbR/xmZexvB9afPfTyGPF/xgN9wplVccLc0N0F0l228jrKerCNO5/LMKdr
r6e9QA5nhXn4fF3Gec1Z6DF4ncJHT2V44ylumR/SmXdSnPRyP0G3vn73c/JX2KLX9U9v8GOc
H+L7+zL0gVnoodlQteA59hWDvZ7fgr/myQPODqHXp5DLOfil3M43jGvVWfYZ9W71mh7ntXx/
M/T3+bkMcasaovlCNe5cxnWAdekcOL2+/3iDf77Bv97g32/w3zf4T8Df3+Bvb/CXN/jzG/w1
7pfB1eAYck4BLyGvP/sfu3XzG0Udx3H8+5uZ7s4+ze52u7u0FVhY3S0Ueaq7m0YSEWgpiC2h
lVA0ai0FltIubkqERAIXjRcvJnryZLzgwZB4kJN/ARduJvoXmEii0Xizfmf3V1xNINEDxuQ9
m9fM5/t7mPnNQ5O+07Mmsf1FO/4XuaWNt2SzyihfRdVAt3193bb1qbgdG3JVRG1RWR33ux6L
3Sxez3miNofnNo8Rs+frVfybuB3rP8LGujb02faYndtr45ppe695W4frTfSI9ty7Z48bffGe
ZyM2h9cNbE7Z51Gy1wk2np99z8v2fYTv+7J6X62qc2peTasFdVO9qppqRbXVafWaumKPr6hr
tg69pd4O5784ZLImI/v1v5qMCWREj2l7TJqUTOoxZetA603d9q8mR06au2b9vQ9l8539L506
c+fW5vm7JjJxUXflI3eNFyYvTH2dNPGmprB0HpZOWLph6YSlG5bysFfC0oSlhKUpHzGj3U16
N1di6z/Ib3Jfn+SzMi3SKNYb1WhtrBot1xrVQj5faEQaY4VGpVIrD0Sq5UqtVtcRkWinN6qj
89qcLxTr1dpfJpaLjbF8pJlKPuPs3JlJBrGiMQdMcWsQi7l9XqwQHyrEs8FwfNB8lvSeSueH
zCZTNtsrQSKlbTv9ZGGbk8lt8YaXs8lxP5ErfJB2io4J3OF0dqsxiblMv5sdLE77if7+2Zyf
noobt89P+YPTA16wJ5Oo+onBbb47ltTvJ7zHn+Sepu2yV+pyQO8zWijUK7r+sTFd6sN9uPqN
XbUaiYS3VogUKpV6NZzwXGdfuelkkunsC34sseV53W2d0d1HuWDvoVyw7eWBTNsrJ2L96WRy
kzHRUScbSySddCwVveelS4X+3b570HdnfDcXzOSCg/mMb17PGsfzEjv84OnBOTc37BdPuP3D
wcCf7ykOAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADwH3gAAAAAAAAAAAAA
AAAAAACAJ8V8AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB4UiSQL8VId9uhutmVlFbd7Gmu2xzR
fNjmqOySkzpSvJi2DMm7Njt6zk9sdrX9c5s9zd/YHNH8rWajWeSU/GxzVM6YI2H2vbDdfGpz
2P5gZHFH6XDryvV288LFtdLZqZnpo/PHShOXlxbX2q3V5qJ27i7tGx+vTZ2YPHr8+Ohsc2X2
6uqji7n2wrmllYX2cql1/hGn21U6tNS81Fy9IFNyQiblqBzX36jMSlNWdH9VVnX1S3JB02VZ
kPZjxv2bnhFZ1PdQ0mfekityXc/f1GtdlDVtO6vzZmRa583LMa0ndAVLOn5NR7V0blNzd+Zu
Pe6Tcf3VZE57F+ScjlzprHdZ+1py/h+eb5emQ9rblEtqVdf0/1mpfr2nb5gVvU64OZKRPeGX
bxbM/U6L6bTKjY+3n30jfeBXSXQ/99s/dv9Ivm4dvCay/r2sy3daJnVsZ8AfAgwAly8NwAoN
CmVuZHN0cmVhbQ1lbmRvYmoNNDIgMCBvYmo8PC9TdGVtViAwL0ZvbnROYW1lL0hMRkdKSitT
aW1TdW4vRm9udFN0cmV0Y2gvTm9ybWFsL0ZvbnRGaWxlMiA0MSAwIFIvRm9udFdlaWdodCA0
MDAvRmxhZ3MgNC9EZXNjZW50IC0xNDAvRm9udEJCb3hbMCAtMTQxIDk5NiA4NTVdL0FzY2Vu
dCA4NTkvRm9udEZhbWlseShTaW1TdW4pL0NhcEhlaWdodCAwL1R5cGUvRm9udERlc2NyaXB0
b3IvSXRhbGljQW5nbGUgMC9MYW5nL3poLUNOPj4NZW5kb2JqDTQzIDAgb2JqPDwvU3VidHlw
ZS9DSURGb250VHlwZTIvRm9udERlc2NyaXB0b3IgNDIgMCBSL0Jhc2VGb250L0hMRkdKSitT
aW1TdW4vQ0lEU3lzdGVtSW5mbzw8L1N1cHBsZW1lbnQgMC9PcmRlcmluZyhJZGVudGl0eSkv
UmVnaXN0cnkoQWRvYmUpPj4vRFcgMTAwMC9UeXBlL0ZvbnQ+Pg1lbmRvYmoNMSAwIG9iajw8
L0Nyb3BCb3hbMCAwIDU5NS4yMiA4NDJdL1BhcmVudCAxMiAwIFIvQ29udGVudHMgMyAwIFIv
Um90YXRlIDAvTWVkaWFCb3hbMCAwIDU5NS4yMiA4NDJdL1Jlc291cmNlcyAyIDAgUi9UeXBl
L1BhZ2U+Pg1lbmRvYmoNMiAwIG9iajw8L0NvbG9yU3BhY2U8PC9DczYgMjAgMCBSPj4vRm9u
dDw8L1RUMSAxOSAwIFIvVFQyIDI5IDAgUi9UVDQgMzAgMCBSL1RUNiAzMSAwIFI+Pi9Qcm9j
U2V0Wy9QREYvVGV4dF0vRXh0R1N0YXRlPDwvR1MxIDIyIDAgUj4+Pj4NZW5kb2JqDTMgMCBv
Ymo8PC9MZW5ndGggNDYxMC9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSIm0V8uu3DgO
3ddX1A/EraftAoIsOjNooIGZTWoX9KJccQUTTGbRWfTvjyxRJCXSrnuTNAIjt2xLpsjDcw5/
+e2DPX/+dvr1evrlerVne74+TvMwz8GdTfoHf06XYT5P4zyY2fjz9evJnD+f3pjBGOPO13v6
ef3r9PHt9nO73o3DDD9CNCbadBm4GeZ3b8Zh2v5a3pntvws8iVN9EkN9GW+FETctq6b6yoKr
xvTrJlbiZjmcR7r8Fs72vfJ3WOuaFdcsbE0OP7BzxRGjupVH+RWM6FIebGtdDdvd6hoX8wE8
7oYJsTPcsqbeSt/84/p7yu8bO8ToU+7/sSX7firPrl/g0Wjs9oiVRK2GW8rR1aOUvNaTx8hi
EDnFNPuy6lFXOdxvZUUyq9zsBmmLpXI5PM9foMJGXg0D6xggECPbqlIRwgfsv8XDyoprSjWi
rQfA1BNiJ/Yypq0F4UjnY6GlXftjF5BuS+u7EK/PhfZ2CN7a1Hmpmh/beCLCFDA88rgDfmrN
sQFy3tQdGYD0Rg2lI7S8lkbFhBA08GWWI085MW9VqG3lozJ7CY0V6pjuhU+8cUWR6GuXktMw
8o0CNTRswxFGnaueJKW0OYDH3awROfK4/tZCg14pn5NkR1+uPLN9C+JdcroFNFoOaIr8Qir4
u4hZBX/evb+Nm8ULADrU+nXgphw6z45AvSRzDbXeThk+8QSPhXI0jNhygEmiTPYEP2aDEkso
cdtVbyPM7b1KQgrFpSPb23Zze2VbnXdQqSAtrFtUKrAjXPesK3DTsU99DxXkIO45EBF8KTId
6y6O1YhXAw2vQ0MDVWQlyz0wt5Sp6Txfk99znB+QszZGISSgQPG+Q1z2HSGdgsJjiJak7A0V
EEfnI0ilZUCuKsZgfNtXCQIx7ookOqq6t7V+mHVsAIOo2DjsudI/Sjlr8zNNv7XYIKy5pn+8
ABpZKrV3OBIxsXbkDZObRQcxIp9/2sF153sjhK3vWmKU2KBjm/bYkckGguB4JTmG9N6jMGau
5kORiaQBY6wakJG0vLN+iHVD5jE1engmIsL7Mj/ZmYZwEWmJTBpbNlVEpOjVfv9tqchX49jz
R3YngtJShSmYySRzAVtERjh179wIsrNrXZ14QmZxFs0ab62IUNmhR+H2Q/iebIeruWks9Y6f
lLa+uADYYlWAV13Y65gCkzuLAkCSXD2+JyDMsovqbOHHjl88D5HZY5mkEcAfgBenOg4dBDCT
Y0RGJ59f2TnnmitPMRd8TW8oqeqzxIZCHnN7bNYSj71JrhPCCMd4ILs8YYptTkw5qUwxv0Ma
hVs/whmxOO6ABzIsDU3361ai6sDSJkidKHj/k0BjvZgVwBmooTPNAlZzyk0fGaQF1MNwSTDs
Jtq02HOGIpyKfWHOx7xVeWvHIDUzaFWQ0jrQFnszKJvckNbIM6katms8DyljrD30XE6o+fHz
iwzT7EEjfwpVRpJ06Ws44KVYqZyjVaQ7hL7fxgOWwlQzaurn1ibhu9OFNEzMLGV+JaeEr9y4
hyHUovuqBiiK4eIJZRSHVPkhbwhjwY9TRrFj+pnLUfFM5siZE3rGNq2cPPe8bd0M3HhHHWlW
ENJN0wLRi7Y3sg4HM2JCdUPpc4bzA0MwviyV3oe9dsgifzDllrSQT2AM+ExKfObxAxAAI5ht
RXnl+uX0z+vpl/ffxvP92zltO8w+ugv+/+3+v5PzYbiM5zjHYXRnO85DmM/WDZM7/7meHqdf
r6d5mOfgUlDmDH9Ol2FOS+bBjSYh72v66Oen6HNrLXW9iVY25bjFEeacJERiqJpcsg2NYBmt
2soE5plweVG61rDG+q5gBKgIS3b6tyXYTkMYw0QyYOCjiOu8q4WoJpGCF0wADpvFY3KKmuPE
ZtDz+j1aZeEUbu0d374UFndXLkV/UQWWnKSEkT8TZH5L1+8pL18SIO00n/9KWfvX+eMf5vwp
A8rOCZkBmkFF9fsPGdXpTBfn6I8P7/+9dc+47WjSlid7/s85IT0OCZ4Z6fP5K0f+fP5v+5Oe
XqbB8Mfl91fcLf126XEwfvBs8+13CLh585Oe1s3b319xN9j8g96FFzfM6aUpJIDVNkyJ7fow
z7RzA/wnDldOSZJsgflpknwACBaGJPb6yr7EMCe9K/dhjYltXFHziop+Dn0gy8SVY4zP3RNi
WbM1DeOoUyCNnF2YSC4r56nwkK2Iljy0bihPpoEbM7K4KJw3OoZWie22KxebUkGN/Z4PbBiI
uIQy4UR1QmzHtEBj2sKGBy7gHCQzqEUgk53iVY21Ot+U6SvMDVsf2icCQ6IY4ijGTenH5eJm
jZJy65kh2rSXUcwY9Zrv541+kpAKgHV6bX3I2FxgNUdU5A2M1SGb1KxRwVsyyqpZZ6HmJuuJ
R4lUdouq4m3K6Dcx2O6UU3mF6dgCIm52JhnavaLMBc/Gt9B/LzI4ueHiTXhOLhucFx5A7KpI
fBCU42i3DG//l4+v3pD13kqdc7Od8ZO0DNTm0J3xoLHLSYmLA+toDPvG4slGBUcnmklwTKEB
q84nruiPw1U3eoVPcDSx4ZvKWJYvu0MueDomKAT00KuMQiwqEtB/SnF1xfFxLydDEC0OkqzK
1rFm5ZlwgfnQwAxqeM4Qd7Zus6XQwEC25/imYiQZY0HOLrwBiMbM/jT5lBx4+7KBMEg/3TBv
PrKDyxckuFFHApl9e+Ng8rANR9jBgKaigRCJmyAaio5SN9wVTMtbvlvlmga5i8o24XgEJ1SY
D0dEWUgVlUeKrEg0GDZjoedbuIag5nRjD2nfKkvPjVnjtdB7MYEJbABULGi2fFP5HzXZ5jUq
Gna2iJX+6s3SJK/jBo1cSJ2N3hGK2SMpt21rOQwewhNpoQQCrVcF7fs3Sv+W0wbp00zAyjJM
gyjAJDZ+pz/2IutqNChv6Ta863q3xkrQOTVRDTdXcZQgBTNHCDjSbNTotfMznjeKVnTujCN3
xrH2qPThaP2gl1ufxqYpkPNPnBpriSKDGsv51PXm+IreRPPHoBt2Wra++eh6k2yc6M2tmGOs
xQQTZP0QaygMIRo9P0NDiABs1ac1PryBr2LaGwenTpDP1JDY+bnLavuspFLZm7Z1dRvvCurs
qIL2yHjsq6/tjs3tzzGZ1RirYc1Csupo+NjEQzkHvSp9pPn5l7q4WOJhO7OprUkLs2zSLwk7
g6+svFGViuGXDaAgp4WdTwEWyy5Hj+rnY812M7DaDp2cwkoTLPLYqzg2tcqlrKIao10xOkiI
lUyZVDtqTCSrokFh1SZjKm+bY87QodHPmo1Smrc7GRety5uolQ2ChudkeZErQzdz+C60vSEn
AAZGCgEBC7Tsm1rDmgZ2sesI6hUtUtER4F00Rohss/AQm+11RPqIThSRQMe2qCY1YpDjdxAF
xiE5t5eNi2QFYpWZMNM4IubKF55QgjE6MTDeubJgV7P1siI0xjdcGxRCKbaubI0RURPQUIAC
WGVDlp5ZF9kXu2gIL5SNKuKFtvPWusGPOqAk9X0HNxxxbjngTR7wZ/Knx2JvYVyYMdjSeH9W
BINmXTMEa+1NDhYDBmVSNREMPlMziVupX0CJ1AQUK1f2Z2jwIB3+AA2rQGdlx+24lBoS5uW7
ZaM1fj9JNlaZWc8R9KzpAbWWJ1ECMcKcmHOpfHIpshEdT2SsnMr5fGbxmCbvq+gIg+Qf7xRb
M5oxW926GZHDUGXCsOPMOjTaaQNAB9NG/gaoCdw6UA1tQH3hSOKWXTcGubM1q5YkTmkOLPwB
0HRqQvxVPZkMDqd51NDQh/UsV3EogsAQfcEoBp6TfiOcrYteBAFwK9N676jZ8yc8NFb2YERH
LkGyySK2aPwZCc4rXcYIHSoJ3xa/YI/GETVLPzicbuDEAVIHKcrBlrI6yGKHskIBSDJgEJse
OvYQCXQgK8tOLIbBx64BGOUYzVxFbpuF5yyhCSS8LcpbOv7V3oF6gSrZc56UbnbYmmBr2hoz
kzA2BRUrG2GAugFTHsgRHx7QkjadBs4szQf0HZrtNAA31WJPbgJs1N1jB21SbqsjntLadjvi
0j8TiMwN4wvU4BnlF3llCsjCjK1c6iZa0k/rv7j8ss0Yn5CkbGLS8s/OGgLOQzlCO9iFqZoC
ZjoL6WykAjc9ren57UEoPpgwCvYpMGbzuBp5AYJCBBrHKSBotF3r9BfVe2RUyc4ytUeIcm7R
tO7RoaTtQE0CWQNXI5/RXx20tFTUwL6sy50jXcVGlFs+m1nFLXx/afDH1vq/EObrXtP3unsI
84bvnkr8rSsksIBiiPYGhkPNv3fE2EhcCw2sZor6aIZocsR6YlJLwSrfU0AtoeyjlfWRedRj
CHTnrp9MN2ouzJ3LNWHuBgbZEartb1WEizt/TSasZJ/rAB77GTSoaaELJh0Ah4agukbJ+BUA
JKSSCJS+AQWRsMlhHoxOtV995YjYZU9VHmiu9KetybemOwIkxfzEkakgSLobcBMP8YR86sJ6
FnO+40EKWcjNZg7mG3e2wBAXUU60MzhmZdhImN8YEHlzWvt/2qulx20cBt/9K3RMCkS1ZL3c
4w6KAgW6l+Q26CGvKaY70wLJFNOfv9SLoiw72y52UaQTRjYlUh+/j/QKCR/MxXmS58J3uKto
573Se6qaKwTer7BBC2dILnet8RM5JRXQQhOFETfyeYsYA/gEucnSKKdjl27nYa4IZmS0j9ic
RhUwjznpG5LTB3JfIvU/dr7LdCSEuYEwPVf1HHT6UCphanbSrUVf3SBGTUh7YaoIR5zrGGmj
vC99UoBfPO//0CMVVZ6j6hDCjVmmYpyqJx7a4o3DSCtWc4NRbCRzUc7UKnnHQ1adaNGeaa5x
4JCkiHLx6Bl2ioDVM2NsC4H+XIddCLDMTgcawr515kro/lhIaYcFIZwpO5MyYX6/E8Lx0y1l
gkh2o0PlSvShYKJit1IcA8WZdi1VqNIo10BoskcwUaoFtVedqPaShGbiysVOcd/oP1KBmKnR
GSROGkC8Js9dpWcxrTMdj6PGpGGHdCNLANAthlJfV48hpWMyqAW/1yTh9DgX94J0z4+ZqI91
kkpruzinkV4vC/iYknQmatFTnSLkYFKPqBsQL2hF4sTq0jQpuRB2m+PSm5O0o5JNBigiXBUQ
GhkJxxAZD7nHudEllxLFtieRQ6iuvk38mbaK73fd27urYccrA6/cDVqO+Pd6/NYJZbiUDBoV
bgxzfFRMSG4lu5y7h+6PXee4c0rCiXqWvtqRO3hh4FDKwEPPoFpflhvMKM9NPzVV4WqmvYGa
PMv54Ehk8M9HY7myRiYtBaE0OglqnJ5ih/ylE35piI9NBbXFH4LD4y5XpcdsuExLodKSgee7
iGvaMI4Us22WXNqjp52FIdmoBlpSKbcoLqWuxWzE4+15pgZdDusWV+SmDJYfynMUk3fbgEl4
eAQE4pft3Z/+7gx7ZaJnn1iA6KACRAGXzxSyTrGniV3WneRCkvVoP6M/sGV4X2veU/9gC0P8
V3ZZR/+V/Yz+sv9tdy+hctgv/Pe5Z6dOWc2VYnpU3LtTWnp32mluHLirbVjvh/B4Xt/+U8Wz
j7DyFX5TcLxXdh821W7go4RNDR/BKZqOe9eBEfQ4cu0t4dOZrCMc1/HeZRvOZw3XaGMw3hEa
fpMjBuq5R4Y3o21Gn8jsx1h/krxLtI5dPkW0n7p8xmjn40dP2Yr7HLvDmwywf3UxAghQqnIz
CThPE7sCUljfdrM5FxDKqErShUsXGiISToU0xHiThVlPNmY92fmk0RNaYR/Mu4DsaJJ3YcAl
5l0YKFrMe7Iw78nGvCc7RxA9oRX2CXkHQXm728FvbPcAbD26QN3hi4K0KgMvWXAYhQVY+QKE
/QE+H+Exj1kReMHTgidyTxo2cjxEfpLycPQcD1uouEXvPcj4FKqCGv0bgfihYnav3f2K3f9c
O25X9vO7teVixdZBYHY7E/1IrsYsLFExNPoQKvr4tP9rvRGCu9V5DQvDCjR0D96G1Sn/frmy
8/76COsWzEvcZQNX1g/Od29WCodbuHJMv5vf4mW9GcHfd/AHaV+xH+nLt/UGoOb3kT2Xfn8f
zOUKyw7sl338YfIYxyjThaR8bzSs2t7mfMUM9/4I/1Ga3S+kOcRtcOfV+9Pjy/fL4/6JrWFv
EJG/BRgAOHnpmQoNCmVuZHN0cmVhbQ1lbmRvYmoNNCAwIG9iajw8L0Nyb3BCb3hbMCAwIDU5
NS4yMiA4NDJdL1BhcmVudCAxMiAwIFIvQ29udGVudHMgNiAwIFIvUm90YXRlIDAvTWVkaWFC
b3hbMCAwIDU5NS4yMiA4NDJdL1Jlc291cmNlcyA1IDAgUi9UeXBlL1BhZ2U+Pg1lbmRvYmoN
NSAwIG9iajw8L0NvbG9yU3BhY2U8PC9DczYgMjAgMCBSPj4vRm9udDw8L1RUMSAxOSAwIFIv
VFQyIDI5IDAgUi9UVDQgMzAgMCBSL1RUNiAzMSAwIFI+Pi9Qcm9jU2V0Wy9QREYvVGV4dF0v
RXh0R1N0YXRlPDwvR1MxIDIyIDAgUj4+Pj4NZW5kb2JqDTYgMCBvYmo8PC9MZW5ndGggNDMy
MS9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSInUV02P40YOvftX6A+Mpr4lAY05ZDZY
IMDupX0LcrC73cEOpnNIH/L3tz5JVpGy3dPAIovE05ZkVRXJx/ceP399C9PT26QnNa/Wmw3+
vj39cfj8z0c9/f520F7Ni5mW4GfnJr3My6RNuvPn5fBy+Ol4+Hw86rjG8eWwzuvqzKTif/Xr
ss1rfHWd1arsdHw9qOn3wyc1K6XMdHyKl8e/Dr8+pMv0+RLmtV7YoJR3Sjlbb3r15VOYl/TN
f1Hxj7vUJ/En7Ulgt5xrty7lrQU2+fLb8ZfDZ0xC/C8FvszbapZ4cfxHPpo5x9O0o/m1LazX
/H4KSM/bZiy+kc7vbPyE8slxLPngdRUPx1vgVlxS9Wf7+ViO9/Ux1ygeYzMGvzx+/Xfc/pe4
77d0M0x/TVpN/5p+/U1Nzwc9/WfKxVtdLp6fXmktg5m+D9f4fAnzRh7ny1dYLF2G9DjW1eLa
8crRtbtrfN7Wppevba229GMC1h6cvJsNwCmCqCTs+C1efdKzD0qnQhCUyQDbSlHgpjcAI5eh
4jV/ovcrGBfKADs1wC24Xv+z9qYlx3E+rR7/vqT9yjuwm3uBd84EL/n4FxJCBDusjT9xgeyT
9oj3SdjL2Fdn1nFuY4f3DavxkOqBnuEFk5VTOWYDd07tcapnVeV4On7XOqPf6tlZrbGtNESn
WzL1isvguhrOvbazpQU/tRUTSry1tF07aOCB2IoVGpAQwj0tITF/7dYT/kp19HTucgRtv5FS
9Mdxl/LJEPGUFgOHhsZ8IoRWzH/jtExnmEikrfZOGMNeGPzhpG4RDl/eWoU0djiAELB3xnPG
IwYZGqnPg299Xtla29k/1PgqW9dbEhjupAz/MU06cxZRfe9QViG9g6IDNXa1t7Vq54z/r3Rp
x/otr1n7LXbpyG0ZYoxRzql+Lfx280TIrw+ANkr98cb4roaNgH3qaOtqwipMz4XesFtlykC+
MmeyRKaMLsOqS3x4P2dYf61oOVzeKbCCNSxvlVehQzEb2VYs+3X2W00QECMkaVeCen4RQNyk
hOzTNefK1val+wUFcDwmf8L301u6VVxDS2h3HWgZor6EXKSnnVvGBsnchS7RVGkwihJhiEjI
afHEM5J0+8FYYEqAOALv29CTryOUv1OtgUZT9bO66kqj/GgeMlvNaup67NATnqryoJaUvPNT
TD1E2gR3zlgiDCyBJe+0WfDSroCypIcS5U2WwCPWzC1U2X+AFzIiz11NSIEzGjbeDZxpEQ22
p1wNacmVPXHQyT3eyHYnw4I19QsvVqg/oZSUL1rqBZ8yaAbiVooJnd6gNIQx6d5cKv1pRG0D
LEcD9EwaJ+7u+L+hLygijkQo5Q1nGYSpc6zG/kxJBCoUP+fmG4WaDJQllYVD+9z7RYphmsML
e3P0ieoFOlXdlu6PlQ9u0dx10VMXQnQBy0fUs8YayqeRMfCkxHbUB0njlqjsVNO5GFTvwQ2D
7AE76fZckNJQK2QD03oujOueO6JWtPNUsuUPrTe7qt7y7VaQ9D2getYeONCCaa4URoSB9qeU
UFldkZwwFThGweqb4kMuYQ1Sf1jGeyQ7wDXJfGFTYHTifwFp0mC5Cwstti1BCzEjzXyXsGVv
hkoEzPbS1Jis+15vlmnO0+bBwO1gVzkta8WIp2LeSm0hEjjhDdKCl9bmpH2ENBaWqjmQrFMT
dCWMTJ0a00hUx118OEGX6n3fAALS3Y0h1EIFasvbGtaZIyG1dfCtravj1Hb2qRYplGre660r
YLjJEB/CBUavYRi59Apukbd3tyE1PmP3alBzrkG9MW1hCEzS5bk1c12fKrgbXZo0qim2AcVB
79nByNwpxc9FI1VjWgMH0qpfmoQHLQWCCu+7kd9PXbOsHPXtzTLV9pYig9uxOhBdSHa+ua52
87n9zr40eaPWZRVcGh3xhjqspEJjl1FcKZoZwiV7EKG0RCCY1eUiz05DfxZPXZsxH2X5WFcm
hdh39zlAYdy5qqR9Wlw/1nIORDXUVYGICmUhE+Yb2mGFqeXurVZAP72jQVrXEviMps0JNWfu
ZkQKoR+MQ6Y4S46jTihI6foef5tTt1BV26iNyGl5pvLTzW2S/eyY1gBRSQcZiMoQogI2EVuL
sF75jSJjUUGDbGXEMlD920n8+80NfppfofKbk3TiaD0x0NNUqr08ihmHJDVjk4qJ9e6KKqgo
xZJQTeRkXIasHWEENnVw989tC1hNXRiw4f0RUZRfO0rg/D+wQ4ZsGd9EbEiiumEmsJCaJl4b
GRvXeINhw++PQCtnshPDRpsgJKu3ZzRbSYtRsfVIaTbI9ArELVCpopnhnBRf1z4BvmPaaqwv
5JiEAe2gBdzXkcMTuPR0iQYudHuzsPMZl4bfTtxkbEhlqBnY89gAm4/xBk4rTWYDtgYDwonl
zV366YDCPIsw02yqKTlRCeYnDAmxceG7eUUmH84Bqpmu/x+JXWh1/scSuz8jglhaDLvtqgMD
Rgsb0oCUv4n4JTQ9SmsNa49GpZwraeShrVKF5GOtok4jnyhWzht5U0PSiNaI9YO8tSLeUz9C
vaCjHMSympK9WiTqMmCDiicDAp9PYsU69YgKClradw6fMJuk1vYBZdjBxg4Tr4OJYabhwwrb
7azyvu0AZ6FrYXuStl1dVjj5MG6r+FVprCorH78dfj4ePn99C9PT2xSTM6/Wmw3+vj39cVi2
eZ2ctbMLk9XbbCZt5sVMf14OL4efjod1XldnYl7VVL/WN8Ic8xjT8nrQ+Wla7NZgl3ls7fR9
aCOJ8M88V2Qc6HJFfrJQcoaSOMQrsr5br1MsYDBi1IbaFrzdMjQvTZSoG3H1AT/mFavNIQJ7
utALbe9UIWwv8KMvoSYjZqLC2Bi+je+Yi9xGhvN7cSHNY/E22qDwacUIwAiYzWSMeTO9IuKC
m753V+2Zc+mF793Va1vG+VmlFx8P1wAdkRwioE1e9z5EGzPHWg2I3oVxqilyMh2r3jGVkhKr
ob7EXYLtQI4lJSaS6aopOtEOCwIJV6pfxLVhOU9pcqtTEC16h0xFj/VjIkjaNOygm4Qth35z
4EJLSzMhNpJWI5SvQU75+K9N/97LoWqd/f2IS8zjTkK5CnZaUkmojvGADz3ixOp0jMfeLORX
BHiH8SCHAK4LEu4uyBl51d+fRVz5SoFiQljYAH3XmzXSUSFHO8IAW7z6o3xGR32qjDgPZXCo
QhW4oavuHdiykfjMZqLG34csu7nIe/dzmaVDWyD46Y28Z/RDGIBI+i4D0t5fWb2Y7b82zQhu
GI5AkLVUoNIZ0a0FVY7yXxfJBww950a/27ekOTpogBNhyEr+Kvjmr2qr6iisDxW9y92QWtZZ
u8hXcfk7FdKual7WH/F8vlMx4IcKFbRp4PnQXQV2q/YwOsVBuQR6oWBZBvXYpZfmMIlXBG5a
kOIEnII/oB6BilsJgLtT3ECwXbb3fLRPrzdpCxnCVQ1kMnWJ6H6nGtrgZuveR1ohzBuD1/4c
cZ8BQ2PqhJlrb47AubSY5cZlJ+CytnMxz8ko19+qaqoD2w3lsOGpm1EQU3WpYrQJdq/NKOsQ
tmJU6bgTjJvnAZVTXcXHuFjH1cWkVUy1v/omaanMko20zLtIy6vZre9DlbezNj9MWppX0Q7d
63mmAT3uBWHYd6/t5EGYXyUCKsUfPZohfEo6PhTXThAEp2qC2eu+aMJGm8nHXncF6dVCiCR4
iwHpGenxbgIsszsA7PIugNkwhwiwoOeMrzhD3sKX3Wb7w/i64ucbcoifV+wW4mvp36KmRSYM
KlY5ZcuumsEBYJmKk+Kk2s0TJY9m+fHQWwuZ0shKmkc9yH7shD0k6OTO3Lmj67ohUcc4tekp
7x6AGJPmO+u3Wd1rm4yfI3rdO8w4Ji0MsKCKxZy3ZzTd+g90DR3WQn5m4U3Tkp01bNC23IsX
thshyQKhbm3S26Z8MjTAjC/E8AdW6Sthc84EPhnBRKivYzfDQmjzR/NJCbXV+slj3sI5Dxpo
x4aI7X9d3etwQbr7Dqiqdd5ChN86Rya6D6o68l6424L9TW19+y7YGruNFmyjWMSDXkTEpzo2
68bawC2DBQuMwQiXE2rqobrQM0ggPxOcNfLOXeSbDduBqiYFwkJmIoxftbDVWgIu3vM92DOb
n3VUUK0SW96FPbMtc5KTe7HnqV2/DEVwfJBy3M26bSiCxDIiTSKhrk0FkwC2IQkytK3Fr/rZ
mOk1X4d8GWej7/1le2pVtCAGntbL17ZWvl7j48druVxd8h85l2r6PX6iESlxHr/Fq086+mel
EzKGu97adHfwL5p2k166WbBORp6Avbd8Z0bP/yW9Wnobt4HwXb+CR6qAteKb2msLFA0QoEBy
M3KQbTnJrtssLKdp/31n+JbF3XazBycaUZzHN8PhNwuys+TH6xlNqAXcq2nOI78szkWEteAX
YcoVTdNeEDD24u99ar/O/sQQaX1twFrQ7CpzSa/kVf0W135RvwVUqX7Hwh1PlWJfuz5amYFM
5R4RG9Ca2U+hfx7hk305kcjYP9cUwizTX+S5Ri+X7Eaue7Ejs6lv60rXzVf8VTjV3llGl3pO
DLH0IAEfCjoo3ESNRQFVSyM6lVtROisxWrtG/BsHC/BbDp5Z38LMrnqwYtryeV/coeuMmIJC
VUCJV9SS4/6veajgdqt5yK6zs/vaPeBv/fWJyL0/hPmD12pAjUU4WTrjTLyrNPDoePIYr6OE
K7dOI4/RMr1qEWxXmA9KpyvCMuQeXrKisrVfzYw8Y+TKZd1pisNZS3MmjbUZI9Kwb5+xyvmv
TR8yl9YybFOWZ63x5Wm15EN9GmdhT7U0cvPOIweiJeOQsC7OY1kawCC2MG7Cff7ffx56cmik
gVFTEmMkUv4/Gqk4jqlGq04BZViIwCi0YxRx9a758POsyX4mdWLHyA2sfIJ3kkvyRrbOpLKi
G4B2GLg1NShNskUCqKyjfgZYiQCBIQ3ywh6chcHEBhGcAw0qiikQpyVJzsY+hal6/HdKsoSB
R5KoSJrOoOSteGnfRCe8fGqih16O3ntNUfJ29s3upwZudo2xvyctohdoI6Ul0MLTlVzSRLd8
11QhRyYobIZc9AYthoBEP2ANhHCDlEAPckI9yMlRpylJzk6CnYO3KqPOFYuQc4nkM5jwQgLc
iwlvLwbPUUV6ROUOaqC3H+7vYXog98fGdIN1NNc9SCgSqaFyTQdn0Y2rwLbOwMJ+hd8NfIZl
yjBTjNwSz4GBkxnlSBuz8sD5bo/EDUxIb6JHDdx/5Y4w7pAD7nCEDlj3/VuzpWT7d2s7Q4eH
j63pGCUtnlXQo70e3slBc6/CM0GVdDDpddyOn9sNY52lUwsLgsJ0NII2QQ/x/Xkm0zg/wzok
g569lY3sVA/JgLvCcGaTCZvdRGto4tJu4CTRF9AHiFPyGh7+bDcwm6Ed3ncc7WMw5xmWLciX
0b+4+qxLUYaEBLw3ynScoc1fCoR7dOG7YDYZZl3CrCjrH1omO0k/XgMtCox1xhjalVNwhxEj
to+P8IAgTjPGJhAap5FArNpjjsgcwmcEIVf08hT2P+NXAw2bQyKUjwATwaSo5doGP76MZ5/a
x5Dacwub6PjlKcjk8hJM7k/j+fmIyFv6D7mgQUmfWgGbQx2Q13l8jM9tGkqM0DZi6ecZD4Xw
LryATgkhkMvTRH77/S+5aSEyhkCg2XPLO03HFvMPeRdgdG41rJ/8+ngB/+GDXZCntgexNM8H
Ec0zmSpgS8fDAaJloGqa52kOVQT32r8CDAAXPrDZCg0KZW5kc3RyZWFtDWVuZG9iag03IDAg
b2JqPDwvQ3JvcEJveFswIDAgNTk1LjIyIDg0Ml0vUGFyZW50IDEyIDAgUi9Db250ZW50cyA5
IDAgUi9Sb3RhdGUgMC9NZWRpYUJveFswIDAgNTk1LjIyIDg0Ml0vUmVzb3VyY2VzIDggMCBS
L1R5cGUvUGFnZT4+DWVuZG9iag04IDAgb2JqPDwvQ29sb3JTcGFjZTw8L0NzNiAyMCAwIFI+
Pi9Gb250PDwvVFQxIDE5IDAgUi9UVDIgMjkgMCBSL1RUNCAzMCAwIFIvVFQ2IDMxIDAgUj4+
L1Byb2NTZXRbL1BERi9UZXh0XS9FeHRHU3RhdGU8PC9HUzEgMjIgMCBSPj4+Pg1lbmRvYmoN
OSAwIG9iajw8L0xlbmd0aCAxNjA2L0ZpbHRlci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIiZxX
S28bOQy+z6/Q0bOAFVHvKYoc2i0KFNi9ZG5GDrbjFC3iFmgKZH/+kqJe43G6DwSOzZH0SfrI
j+TcvH/24vgsQCgZjdNT/X4+fhtuPt6B+Pw8aKtkiCJ4J60VWgVpBGgZtPhxGh6Hd/NwM8+A
IPPjEGWMVguFf/lnmCStjVJFZcR8HpT4PGyVVEppMR/RnF+G3Vsy6XPrZcyGs/gB/IT80Pnb
rZcBf9lwq+iBrdNvQUUJNGTKbFVmu0N+ZB2N4wNHYLxMg/S8rGD7hI1fGcd2u+ZHrkK7/AhU
WtVdoEzRe7pGWTmtwSIZfF11Sivv50/DTfMN/pE/AC8IU0Rr/j0xZg/tGmATmCnn0fuykUEK
TdlMn+qxfMddWa3y9Atu1gx0hLvsi7IzzmlMrrawsVJXObGLGRpvZcj9sVBbl3Rn6rxbcKzv
N1+cv7mdmLaNs2lxENUvrsfJowY9Cka65LJ0ZfDdfPLZh5nd9v4uSQrXTFq3H3fv/8Rw/4QO
/EoPvXgRoMQfYnevxMMA4otIWpuS1Jw498rzWjxd2G08eFz0tDTPBYssj6N3w3WZT0YCytQh
V1ZMgDoldXtf1b3WdFlipc6iblGapB1I2SlETQqDbfMQySnTyM7KglJVVzliNPgi6Mq7rUjk
yn1DOpTswBFIE9oqn4J02+Tc9k+aPXW7khspQ4GSTscsti5d7TKg3TfVVlW8Ety9auhWepnL
9k04OYVorVNktqSE130tjd2uGKtx/ng9HZYlxBphdTu6qeRcHDotJazVJC0jZUio+adci+Bq
Vk5nMJmvKxykycCXs0XtLqxya/JunodfpVIUN5rpQvdZihAtBXOO7HOyOdAD6WFh1lFvpLJt
lM1zxUIbWEy/EgYKz2oWxm5B+J7DfF1H6EqV6y6D9hRwfivpK8c1rOqNfejppxDtC2sfdzyc
oKpLi99P/ZpW7jhEq7NawNsSnG7feaLOUktN9NfuwqluM9Wq2rx9NdO+2rxMUVoRtJGTFgZb
EHvRslzxHa/wmFovc9ouVdbshcfqknr3U3lksuBPnVq7pIL1ZlJTK+A1kRy6aE+hcMjqditV
tCxRcuq6EK4lhNPV2+tc+x6srdz34nN94DQXIGVOM8sRRZIZtBJQIZ1RRoyTJtYhts4FxFDJ
Q90Z7CpiwyRbN9SF2UYL8tI+V7QM/opquUWl+PBNtKt21MachexKck4v29FOwHEVLe4i3/c+
qgHVJ+7WfU2dsrlr6mLIdO5tUFAb1Dw/NUOHVTYgF3P3uYi6Umn7GDFddC1C8XpNu8wGAKV5
ynbT9mk5rVyhpEuI7YwAbIOvAWlAWgPQ9cdd+ex6xLr80OMyxraAbEE6Z0yBWr+c6FdrP7Kr
Lvx8RY6rYsy1obndL5Lk9DqhfIxWTlPZf+zfMGrp78p5VrbqgIxrSSbD+T5YoMzvw0p1kab4
wSLl1PRHjHoFxKiiTorH5q95KJPNrZatE/B9xKdPnoxZZ6dRtuJf/EtttQ3ptRWlTZX7PFin
qaTnruDpws59gG/jd/9QaAAbekgNvcXM85KbeRdT5QkeD0K7VttK44WLqRZxm+8iSF2MI543
cqfBKcti++6KWe+SUKqV9jjWm5q04qnZjgALkDFETdmFreNQDsH201BOyHY5PSNVKwEeh8Nv
Q36b+X+e0YGZL57g1P90YXMyN234brhOuVH4VtJRjooOsVJuND2s101WI53txjrblciEVK20
T6MdArmh0Y5NbnISI4Gj8Cv7sNVoZ7vRzna5ASNVK7C7kXasZjfzrDH+5schEC1U1dIPi0XN
Uhgb6fM7Gr6//ECxfezeQSG9g+IraGpP0pubS9JDFTxofTiS5HALy1soQtA8K2VZWuEMreDX
PtziZdhtxO6vcZKwgZFeEfGLjPsxSLd5M6qNGCkjIKxnWCTZTLEh6gIIYBnw3X7cYknfPJ8Q
Km4exu2Elvg+OrS+Zet53Ab85ilHXvAzbf0F/+vN9xHzDE13MuQzbLEjs8FSAgoaG4V8AOwd
8ASK9zZyxBcNTd9tYaM9s7rV0lg3FYT/TqMNlUbvG43YHG1A349gpd28uWTOrN5P86E/pHsj
T4CpdfPl5xjS9cn4MWokJGz2RJfbPEkGxcT6twADAAaYHgkKDQplbmRzdHJlYW0NZW5kb2Jq
DTEwIDAgb2JqPDwvTnVtc1swIDExIDAgUl0+Pg1lbmRvYmoNMTEgMCBvYmo8PC9TL0Q+Pg1l
bmRvYmoNMTIgMCBvYmo8PC9Db3VudCA0L1R5cGUvUGFnZXMvS2lkc1sxNyAwIFIgMSAwIFIg
NCAwIFIgNyAwIFJdPj4NZW5kb2JqDTEzIDAgb2JqPDwvU3VidHlwZS9YTUwvTGVuZ3RoIDM1
NjIvVHlwZS9NZXRhZGF0YT4+c3RyZWFtDQo8P3hwYWNrZXQgYmVnaW49Iu+7vyIgaWQ9Ilc1
TTBNcENlaGlIenJlU3pOVGN6a2M5ZCI/Pgo8eDp4bXBtZXRhIHhtbG5zOng9ImFkb2JlOm5z
Om1ldGEvIiB4OnhtcHRrPSIzLjEtNzAxIj4KICAgPHJkZjpSREYgeG1sbnM6cmRmPSJodHRw
Oi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4KICAgICAgPHJkZjpE
ZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6cGRmPSJodHRwOi8v
bnMuYWRvYmUuY29tL3BkZi8xLjMvIj4KICAgICAgICAgPHBkZjpQcm9kdWNlcj5BY3JvYmF0
IERpc3RpbGxlciA3LjAgKFdpbmRvd3MpPC9wZGY6UHJvZHVjZXI+CiAgICAgIDwvcmRmOkRl
c2NyaXB0aW9uPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIgogICAgICAg
ICAgICB4bWxuczp4YXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iPgogICAgICAg
ICA8eGFwOkNyZWF0b3JUb29sPlBTY3JpcHQ1LmRsbCBWZXJzaW9uIDUuMjwveGFwOkNyZWF0
b3JUb29sPgogICAgICAgICA8eGFwOk1vZGlmeURhdGU+MjAxMC0wMi0yMFQxMToxMToyMCsw
ODowMDwveGFwOk1vZGlmeURhdGU+CiAgICAgICAgIDx4YXA6Q3JlYXRlRGF0ZT4yMDEwLTAy
LTIwVDExOjExOjIwKzA4OjAwPC94YXA6Q3JlYXRlRGF0ZT4KICAgICAgPC9yZGY6RGVzY3Jp
cHRpb24+CiAgICAgIDxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSIiCiAgICAgICAgICAg
IHhtbG5zOmRjPSJodHRwOi8vcHVybC5vcmcvZGMvZWxlbWVudHMvMS4xLyI+CiAgICAgICAg
IDxkYzpmb3JtYXQ+YXBwbGljYXRpb24vcGRmPC9kYzpmb3JtYXQ+CiAgICAgICAgIDxkYzp0
aXRsZT4KICAgICAgICAgICAgPHJkZjpBbHQ+CiAgICAgICAgICAgICAgIDxyZGY6bGkgeG1s
Omxhbmc9IngtZGVmYXVsdCI+TWljcm9zb2Z0IFdvcmQgLSBhZGRyZXNzLWZvcm1hdC1jb21t
ZW50cy0yMDEwMDIxOC12NS5kb2M8L3JkZjpsaT4KICAgICAgICAgICAgPC9yZGY6QWx0Pgog
ICAgICAgICA8L2RjOnRpdGxlPgogICAgICAgICA8ZGM6Y3JlYXRvcj4KICAgICAgICAgICAg
PHJkZjpTZXE+CiAgICAgICAgICAgICAgIDxyZGY6bGk+eGluZzwvcmRmOmxpPgogICAgICAg
ICAgICA8L3JkZjpTZXE+CiAgICAgICAgIDwvZGM6Y3JlYXRvcj4KICAgICAgPC9yZGY6RGVz
Y3JpcHRpb24+CiAgICAgIDxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSIiCiAgICAgICAg
ICAgIHhtbG5zOnhhcE1NPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvbW0vIj4KICAg
ICAgICAgPHhhcE1NOkRvY3VtZW50SUQ+dXVpZDozOGEwMDZiZi1mMDI5LTQ1ODctOTlkMy1j
ZTczMzY4MWI5ZmE8L3hhcE1NOkRvY3VtZW50SUQ+CiAgICAgICAgIDx4YXBNTTpJbnN0YW5j
ZUlEPnV1aWQ6ZmNjOTEwMTktODE2Yi00MGMyLTliY2YtYzMzZWU5MzExMWNiPC94YXBNTTpJ
bnN0YW5jZUlEPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgPC9yZGY6UkRGPgo8L3g6
eG1wbWV0YT4KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAK
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgIAo8P3hwYWNrZXQgZW5kPSJ3Ij8+DQplbmRzdHJlYW0NZW5kb2JqDTE0IDAgb2JqPDwv
Q3JlYXRpb25EYXRlKEQ6MjAxMDAyMjAxMTExMjArMDgnMDAnKS9BdXRob3IoeGluZykvQ3Jl
YXRvcihQU2NyaXB0NS5kbGwgVmVyc2lvbiA1LjIpL1Byb2R1Y2VyKEFjcm9iYXQgRGlzdGls
bGVyIDcuMCBcKFdpbmRvd3NcKSkvTW9kRGF0ZShEOjIwMTAwMjIwMTExMTIwKzA4JzAwJykv
VGl0bGUoTWljcm9zb2Z0IFdvcmQgLSBhZGRyZXNzLWZvcm1hdC1jb21tZW50cy0yMDEwMDIx
OC12NS5kb2MpPj4NZW5kb2JqDXhyZWYNCjAgMTUNCjAwMDAwMDAwMDAgNjU1MzUgZg0KMDAw
MDA1Nzc3MSAwMDAwMCBuDQowMDAwMDU3OTAzIDAwMDAwIG4NCjAwMDAwNTgwNDUgMDAwMDAg
bg0KMDAwMDA2MjcyNCAwMDAwMCBuDQowMDAwMDYyODU2IDAwMDAwIG4NCjAwMDAwNjI5OTgg
MDAwMDAgbg0KMDAwMDA2NzM4OCAwMDAwMCBuDQowMDAwMDY3NTIwIDAwMDAwIG4NCjAwMDAw
Njc2NjIgMDAwMDAgbg0KMDAwMDA2OTMzNyAwMDAwMCBuDQowMDAwMDY5MzcyIDAwMDAwIG4N
CjAwMDAwNjkzOTYgMDAwMDAgbg0KMDAwMDA2OTQ2NiAwMDAwMCBuDQowMDAwMDczMTA1IDAw
MDAwIG4NCnRyYWlsZXINCjw8L1NpemUgMTU+Pg0Kc3RhcnR4cmVmDQoxMTYNCiUlRU9GDQo=
--------------010003000803020706050108--

From brian.e.carpenter@gmail.com  Fri Feb 19 19:54:42 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 BB3033A7F7F for <behave@core3.amsl.com>; Fri, 19 Feb 2010 19:54:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[AWL=-0.022, 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 Xsiq4fm8SIDH for <behave@core3.amsl.com>; Fri, 19 Feb 2010 19:54:41 -0800 (PST)
Received: from mail-yx0-f173.google.com (mail-yx0-f173.google.com [209.85.210.173]) by core3.amsl.com (Postfix) with ESMTP id C5FAD3A7F3B for <behave@ietf.org>; Fri, 19 Feb 2010 19:54:41 -0800 (PST)
Received: by yxe3 with SMTP id 3so890084yxe.32 for <behave@ietf.org>; Fri, 19 Feb 2010 19:56:27 -0800 (PST)
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=I0r/NA8qKQ9t9s3tz6LKsKOMmB+qvR9P1owq57jrvtA=; b=IpGTjEKK3+amy8mQ4EwwIlbA3PsDwGJ/WjAljquPUbl5knoPIHAAOsiRNMctAGTVrp tILHWsblT0N07nLFDsQh8ArS/g90EU/dAQHrh1qhmi4Li6b4BSMWENnmJLbCdjdr/J65 RJHmstSiwFwq01C1jc2xWCYKPZHmQCqfH/KZA=
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=RiTbLKZxe5ebCQfOoSzXNEI4hsPurw46lxBIYkKuHF+ExvE6WRKvuexp5Xgas9BvTs eFSeFHytVp8ttf0O3WAltJyombxe9CKDJMbH9CUKlXC+/Y18R2BiIxGaSI8lNiEd0OUN MgWchrmWizIld96xA27hYwDKeTMx/J5+Vzvkg=
Received: by 10.101.163.1 with SMTP id q1mr4240023ano.165.1266638187488; Fri, 19 Feb 2010 19:56:27 -0800 (PST)
Received: from ?10.1.1.5? ([121.98.142.15]) by mx.google.com with ESMTPS id 9sm392528ywe.7.2010.02.19.19.56.24 (version=SSLv3 cipher=RC4-MD5); Fri, 19 Feb 2010 19:56:26 -0800 (PST)
Message-ID: <4B7F5D63.1070409@gmail.com>
Date: Sat, 20 Feb 2010 16:56:19 +1300
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: Xing Li <xing@cernet.edu.cn>
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com> <85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com> <4B7F4B3F.9050607@cernet.edu.cn>
In-Reply-To: <4B7F4B3F.9050607@cernet.edu.cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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: Sat, 20 Feb 2010 03:54:42 -0000

On 2010-02-20 15:38, Xing Li wrote:
> Senthil Sivakumar (ssenthil) =E5=86=99=E9=81=93:
>> With stateless, theoriticaly two packets of the same flow can go throu=
gh
>> two different translators and make it to the end point, can it not? Ho=
w
>> can the translator keep track of the ordering of the packets?
>> Stateless (stateful?) is a little different, but even there, except
>> for the initial
>> handshake the packets can come through in different order and you cant=

>> hold on to a packet in the translator and order them. I think this is
>> best left undefined and left to the end point application and translat=
or
>> implementation. Do we know of any application that would fail if the
>> translator doesn't send the packets in the right order?  =20
>=20
> Agree. Stateless translator should behave like a router when dealing
> with L4 and above. xing

It shouldn't try to do *better* than a router, that would be
pointless. So I'm not saying it should attempt to correct
misordering, and *obviously* we can't solve the problem of a
given packet flow being split across two stateless translators,
exactly because they are stateless.

What I proposed does not attempt to do that. It addreses exactly
the case that Simon raised: a translator (stateful or stateless)
that wants to multithread. And the solution (such as a 5-tuple or
6-tuple hash) should be stateless too.

     Brian
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Beha=
lf
>> Of Brian E Carpenter
>> Sent: Friday, February 19, 2010 4:03 PM
>> To: Simon Perreault
>> Cc: behave@ietf.org
>> Subject: Re: [BEHAVE] NAT64: Out of order session handling
>>
>> On 2010-02-20 05:38, Simon Perreault wrote:
>> ...
>> =20
>>> First, I don't know if it should go into the stateful or stateless
>>> document, or both.
>>>    =20
>>
>> imho, stateless (and if I am not mistaken about the normative
>> dependency, it then also automatically applies to stateful).
>>
>> Reason: we really need the same behaviour in all translators.
>>
>> =20
>>> Second, how about "Translation MAY reorder packets."?
>>>    =20
>>
>> Disagree. Reordering is generally evil and should be avoided as much a=
s
>> possible, because it damages TCP performance and can do even worse
>> things to UDP streams. So I think we should invert this and say
>>
>> Translators SHOULD be designed to avoid packet reordering as much as
>> possible.
>>
>> If you want to multithread, that means selecting a thread according to=

>> some sort of hash of the 5-tuple (IPv4) or 6-tuple (including flow
>> label) for IPv6. I don't see it as different from any other load
>> balancing mechanism.
>>
>>     Brian
>>
>> _______________________________________________
>> 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
>>
>>
>>  =20
>=20
>=20


From xing@cernet.edu.cn  Fri Feb 19 21:37:31 2010
Return-Path: <xing@cernet.edu.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 4D9893A7B1E for <behave@core3.amsl.com>; Fri, 19 Feb 2010 21:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.229
X-Spam-Level: 
X-Spam-Status: No, score=0.229 tagged_above=-999 required=5 tests=[AWL=0.132,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 TuRMLzL4Zq+l for <behave@core3.amsl.com>; Fri, 19 Feb 2010 21:37:30 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id D03573A7CE9 for <behave@ietf.org>; Fri, 19 Feb 2010 21:37:29 -0800 (PST)
Received: from [192.168.1.101]([124.225.139.33]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b7f7f53; Sat, 20 Feb 2010 13:39:17 +0800
Message-ID: <4B7F7582.8000700@cernet.edu.cn>
Date: Sat, 20 Feb 2010 13:39:14 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>	<4B7F4B3F.9050607@cernet.edu.cn> <4B7F5D63.1070409@gmail.com>
In-Reply-To: <4B7F5D63.1070409@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 5uhDiiXB
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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: Sat, 20 Feb 2010 05:37:31 -0000

Brian E Carpenter 写道:
> On 2010-02-20 15:38, Xing Li wrote:
>   
>> Senthil Sivakumar (ssenthil) 写道:
>>     
>>> With stateless, theoriticaly two packets of the same flow can go through
>>> two different translators and make it to the end point, can it not? How
>>> can the translator keep track of the ordering of the packets?
>>> Stateless (stateful?) is a little different, but even there, except
>>> for the initial
>>> handshake the packets can come through in different order and you cant
>>> hold on to a packet in the translator and order them. I think this is
>>> best left undefined and left to the end point application and translator
>>> implementation. Do we know of any application that would fail if the
>>> translator doesn't send the packets in the right order?   
>>>       
>> Agree. Stateless translator should behave like a router when dealing
>> with L4 and above. xing
>>     
>
> It shouldn't try to do *better* than a router, that would be
> pointless. So I'm not saying it should attempt to correct
> misordering, and *obviously* we can't solve the problem of a
> given packet flow being split across two stateless translators,
> exactly because they are stateless.
>
> What I proposed does not attempt to do that. It addreses exactly
> the case that Simon raised: a translator (stateful or stateless)
> that wants to multithread. And the solution (such as a 5-tuple or
> 6-tuple hash) should be stateless too.
>   

Then we may add a paragraph in section 1.2 of xlate, mention

a translator that wants to multithread should avoid changing the order 
of the packets.

Is this the correct understanding? Do you have a suggested wording? Thanks.

Regards,

xing

>      Brian
>   
>>> -----Original Message-----
>>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
>>> Of Brian E Carpenter
>>> Sent: Friday, February 19, 2010 4:03 PM
>>> To: Simon Perreault
>>> Cc: behave@ietf.org
>>> Subject: Re: [BEHAVE] NAT64: Out of order session handling
>>>
>>> On 2010-02-20 05:38, Simon Perreault wrote:
>>> ...
>>>  
>>>       
>>>> First, I don't know if it should go into the stateful or stateless
>>>> document, or both.
>>>>     
>>>>         
>>> imho, stateless (and if I am not mistaken about the normative
>>> dependency, it then also automatically applies to stateful).
>>>
>>> Reason: we really need the same behaviour in all translators.
>>>
>>>  
>>>       
>>>> Second, how about "Translation MAY reorder packets."?
>>>>     
>>>>         
>>> Disagree. Reordering is generally evil and should be avoided as much as
>>> possible, because it damages TCP performance and can do even worse
>>> things to UDP streams. So I think we should invert this and say
>>>
>>> Translators SHOULD be designed to avoid packet reordering as much as
>>> possible.
>>>
>>> If you want to multithread, that means selecting a thread according to
>>> some sort of hash of the 5-tuple (IPv4) or 6-tuple (including flow
>>> label) for IPv6. I don't see it as different from any other load
>>> balancing mechanism.
>>>
>>>     Brian
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>>   
>>>       
>>     
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From denghui02@gmail.com  Sat Feb 20 01:43:30 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 0008628C123; Sat, 20 Feb 2010 01:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.383
X-Spam-Level: 
X-Spam-Status: No, score=-2.383 tagged_above=-999 required=5 tests=[AWL=0.216,  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 5ZRkEIC1kDnR; Sat, 20 Feb 2010 01:43:29 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 3D4B528C122; Sat, 20 Feb 2010 01:43:29 -0800 (PST)
Received: by pwi3 with SMTP id 3so950974pwi.31 for <multiple recipients>; Sat, 20 Feb 2010 01:45:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=8SxS4NbmiUnS7gfMUKKnAxF2f4X4Zl4wNTG5MW/yJtw=; b=Otc+ufuPWiFHIm9SoxgY0sU/fi03LMGu+cd9DbEgomxAIwEXuFfxud0gNYQn6bvDEx JWY+A6FiLyP6sSljp9+kq9iV+l+BwcaZpQjSY3StBJUiLOMwQ15MNCwghL3s3Utec1yF Agkmu5o8s2zmf6iPcgviln6V+O6qkhe930rCs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=I9KNhDX00ycW3q8Tg14poKcDMClcJYjyHa9M3idSVp7fCBPPje5odN91hmspHOt4gr atLHt5vS0u+o7f49/26535Pqwg9CcZePjje1dRogR5LzKlZyASqrmNyww+/cJAHSz2bC SfA00TIA8HAGaaqOptPmITP9CwucDf5EFf9HE=
MIME-Version: 1.0
Received: by 10.141.214.1 with SMTP id r1mr1954928rvq.251.1266659116559; Sat,  20 Feb 2010 01:45:16 -0800 (PST)
Date: Sat, 20 Feb 2010 17:45:16 +0800
Message-ID: <1d38a3351002200145r2cd2cd46x2fa9bd2c9ef47f74@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: 3gv6@ietf.org, behave@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [BEHAVE] Comments on draft-wing-behave-dns64-config-02
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: Sat, 20 Feb 2010 09:43:30 -0000

Hello Dan,

Many thanks for writing this document, I feel this idea is good.
Sometime, IPv6 only might be upgraded to support dual stack, then
DNS64 and NAT64 sometime might need to be supported in dual stack network,
comments below:

1) From title, this is more like dual stack connections other than
dual stack hosts?

2) if we put DNS64 in the host like PNAT, then DNSsec will operate much better.

3) in Section 3.4 what do you mean side effect? 44ALG or 64ALG?

4) In section 3.4.2 regarding applications own adress selection rules,
can you help to give some examples on it?

5) section 3.1 require 2 DNS might has some practical issue..

thanks for writing this document

-Hui

From simon.perreault@viagenie.ca  Sat Feb 20 06:45:00 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 0914D28C151 for <behave@core3.amsl.com>; Sat, 20 Feb 2010 06:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.300, 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 R2KJp0OSXp1C for <behave@core3.amsl.com>; Sat, 20 Feb 2010 06:44:46 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id 0E81628C14F for <behave@ietf.org>; Sat, 20 Feb 2010 06:44:46 -0800 (PST)
Received: from balaise.nomis80.org (modemcable245.152-21-96.mc.videotron.ca [96.21.152.245]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 397B521C9E for <behave@ietf.org>; Sat, 20 Feb 2010 09:46:34 -0500 (EST)
Message-ID: <4B7FF5C9.1080208@viagenie.ca>
Date: Sat, 20 Feb 2010 09:46:33 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>	<4B7F4B3F.9050607@cernet.edu.cn>	<4B7F5D63.1070409@gmail.com> <4B7F7582.8000700@cernet.edu.cn>
In-Reply-To: <4B7F7582.8000700@cernet.edu.cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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: Sat, 20 Feb 2010 14:45:00 -0000

On 02/20/2010 12:39 AM, Xing Li wrote:
> a translator that wants to multithread should avoid changing the order
> of the packets.
> 
> Is this the correct understanding? Do you have a suggested wording? Thanks.

It's not perfect because it mentions "multithreading", which is an
implementation detail. Only externally-observable behaviour should be
part of the spec.

For the record, I find Brian's wording perfect. Here it is again:

> Translators SHOULD be designed to avoid packet reordering as much
> as possible.

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

From ebisawa@sablenetworks.net  Sun Feb 21 02:36:46 2010
Return-Path: <ebisawa@sablenetworks.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 0F83728C115 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 02:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 wm7TXCQ+fed5 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 02:36:45 -0800 (PST)
Received: from sablenetworks.net (sablenetworks.net [202.229.133.90]) by core3.amsl.com (Postfix) with ESMTP id BBA0328C0F1 for <behave@ietf.org>; Sun, 21 Feb 2010 02:36:44 -0800 (PST)
Received: (qmail 15475 invoked by SAV 20100221.005 by uid 0); 21 Feb 2010 19:38:37 +0900
Received: from unknown (HELO ?192.168.11.6?) (ebisawa@220.219.184.150) by dc12.etius.jp (202.229.133.90) with ESMTPA; 21 Feb 2010 19:38:37 +0900
Date: Sun, 21 Feb 2010 19:38:11 +0900
From: Kentaro Ebisawa <ebisawa@sablenetworks.net>
To: <behave@ietf.org>
In-Reply-To: <139901caac18$0ae0d5e0$c4f0200a@cisco.com>
References: <139901caac18$0ae0d5e0$c4f0200a@cisco.com>
Message-Id: <20100221185309.58DA.B01659E3@sablenetworks.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.50 [ja]
Cc: draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-stateful-08
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: Sun, 21 Feb 2010 10:36:46 -0000

Hi,

I've reviewed the draft and here's some comments.
Most of them are editorial nits and other part of the doc seems good to me.

* Section 1.2.2.
192.0.2.1. should be 192.0.2.1 (don't need the last period) in 3 places.
[Page 9]
>          address in the packet and (192.0.2.1.,80) as destination
[Page 10]
>       transport address (203.0.113.1,2000) and source transport address
>       (192.0.2.1.,80).
[Page 10]
>          transport address in the packet.  Note that 192.0.2.1. is

* Section 2.
[Page 12]
>   Filtering, Endpoint-Independent:  The NAT64 filters out only incoming
>      IPv4 packets not destined to a transport address for which there
>      is not state in the NAT64, regardless of the source IPv4 transport
          ^^^
s/not/no/

>      communicate using sessions that hairpin through the NAT.  Hairpin
>      packets packets can be either TCP or UDP.  More detailed
       ^^^^^^^^^^^^^^^
delete extra "packets"

* Section 3.5.2.2. *** ESTABLISHED ***
[Page 30]
>   If the lifetime expires then the NAT64 SHOULD send a probe packet (as
>   defined next) to al least one of the endpoints of the TCP connection.
                     ^^
s/al/at/

* Section 3.5.2.3.
[Page 31]
>      If there exists some other BIB entry containing S' as the IPv6
>      address and mapping it to some IPv4 address T, then use SHOULD T
>      as the IPv4 address.  Otherwise, use any IPv4 address of the IPv4
I think "then use SHOULD T as the IPv4 address."  should be
"then T SHOULD be used as the IPv4 address."

* Section 3.5.3.
[Page 33]
>      does not exist, the packet is dropped.  An ICMP error message MAY
>      be sent to the original sender of the packet, unless the discarded
>      packet is itself an ICMP error message.  The ICMP error message,

Since this part is talking about how to process incoming ICMPv4 Query packet,
I think "unless the discarded packet is itself an ICMP error message."
is redundant and can be deleted.

[Page 34]
>      discarded.  If the packet is discarded, then an ICMP message MAY
>      be sent to the original sender of the packet, unless the discarded
>      packet is itself an ICMP message.  The ICMP message, if sent, has

As mentioned above, "unless the discarded packet is itself an ICMP message"
can be deleted.

Also, "The ICMP message, if sent," should be "The ICMP error message, if sent,".

* Section 3.5.4.
[Page 35]
>         If we note n the length of the prefix Pref64::/n, then n MUST
>         the less or equal than 96.  If a Pref64::/n is configured
          ^^^^^^^^
s/the less or equal than 96/be less than or equal to 96/

* Section 3.8.
>   If the destination IP address is an IPv4 address assigned to the
>   NAT64 itself then the packet is a hairpin packet.  Hairpin packets

Just to be more clear, I think we should explicitly mention this is
talking about IPv4 address of the translated packet. For example,

 If the destination IP address of the translated packet is an IPv4 address assigned to the ...


-- 
Kentaro Ebisawa <ebisawa@sablenetworks.net>


On Fri, 12 Feb 2010 11:17:39 -0800
"Dan Wing" <dwing@cisco.com> wrote:

> ** We need at least 5 reviewers to tell us this document is ready 
> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org 
> ** with a subject line containing the document name, and "ready 
> ** to submit to IESG" or "not ready to submit to IESG" in the 
> ** message body.  If not ready to submit, please propose new text.
> 
> 
> This email starts the 2nd WGLC for draft-ietf-behave-v6v4-xlate-stateful-08,
> ending in one week (Friday, February 19).  For reference, the first WGLC was
> for draft-ietf-behave-v6v4-xlate-stateful-07.
> 
> Differences between 07 (first WGLC) and 08 (2nd WGLC) are:
> 
> http://tools.ietf.org/rfcdiff?url1=draft-ietf-behave-v6v4-xlate-stateful-07&ur
> l2=draft-ietf-behave-v6v4-xlate-stateful-08.txt
> 
> -d
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From marcelo@it.uc3m.es  Sun Feb 21 04:01:45 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 331253A82F3 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 04:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.296
X-Spam-Level: 
X-Spam-Status: No, score=-106.296 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599, 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 qXkQuNR15ch8 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 04:01:44 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 048313A82F1 for <behave@ietf.org>; Sun, 21 Feb 2010 04:01:43 -0800 (PST)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro.local (unknown [95.18.30.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id EC6B37F026F; Sun, 21 Feb 2010 13:03:33 +0100 (CET)
Message-ID: <4B812108.9070101@it.uc3m.es>
Date: Sun, 21 Feb 2010 13:03:20 +0100
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.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Kentaro Ebisawa <ebisawa@sablenetworks.net>
References: <139901caac18$0ae0d5e0$c4f0200a@cisco.com> <20100221185309.58DA.B01659E3@sablenetworks.net>
In-Reply-To: <20100221185309.58DA.B01659E3@sablenetworks.net>
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-17162.002
Cc: draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org, behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-stateful-08
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: Sun, 21 Feb 2010 12:01:45 -0000

thanks for the review.

I don't see any difficutly incorporating all the proposed changes.

I will include them in the next version

Regards, marcelo



El 21/02/10 11:38, Kentaro Ebisawa escribió:
> Hi,
>
> I've reviewed the draft and here's some comments.
> Most of them are editorial nits and other part of the doc seems good to me.
>
> * Section 1.2.2.
> 192.0.2.1. should be 192.0.2.1 (don't need the last period) in 3 places.
> [Page 9]
>    
>>           address in the packet and (192.0.2.1.,80) as destination
>>      
> [Page 10]
>    
>>        transport address (203.0.113.1,2000) and source transport address
>>        (192.0.2.1.,80).
>>      
> [Page 10]
>    
>>           transport address in the packet.  Note that 192.0.2.1. is
>>      
> * Section 2.
> [Page 12]
>    
>>    Filtering, Endpoint-Independent:  The NAT64 filters out only incoming
>>       IPv4 packets not destined to a transport address for which there
>>       is not state in the NAT64, regardless of the source IPv4 transport
>>      
>            ^^^
> s/not/no/
>
>    
>>       communicate using sessions that hairpin through the NAT.  Hairpin
>>       packets packets can be either TCP or UDP.  More detailed
>>      
>         ^^^^^^^^^^^^^^^
> delete extra "packets"
>
> * Section 3.5.2.2. *** ESTABLISHED ***
> [Page 30]
>    
>>    If the lifetime expires then the NAT64 SHOULD send a probe packet (as
>>    defined next) to al least one of the endpoints of the TCP connection.
>>      
>                       ^^
> s/al/at/
>
> * Section 3.5.2.3.
> [Page 31]
>    
>>       If there exists some other BIB entry containing S' as the IPv6
>>       address and mapping it to some IPv4 address T, then use SHOULD T
>>       as the IPv4 address.  Otherwise, use any IPv4 address of the IPv4
>>      
> I think "then use SHOULD T as the IPv4 address."  should be
> "then T SHOULD be used as the IPv4 address."
>
> * Section 3.5.3.
> [Page 33]
>    
>>       does not exist, the packet is dropped.  An ICMP error message MAY
>>       be sent to the original sender of the packet, unless the discarded
>>       packet is itself an ICMP error message.  The ICMP error message,
>>      
> Since this part is talking about how to process incoming ICMPv4 Query packet,
> I think "unless the discarded packet is itself an ICMP error message."
> is redundant and can be deleted.
>
> [Page 34]
>    
>>       discarded.  If the packet is discarded, then an ICMP message MAY
>>       be sent to the original sender of the packet, unless the discarded
>>       packet is itself an ICMP message.  The ICMP message, if sent, has
>>      
> As mentioned above, "unless the discarded packet is itself an ICMP message"
> can be deleted.
>
> Also, "The ICMP message, if sent," should be "The ICMP error message, if sent,".
>
> * Section 3.5.4.
> [Page 35]
>    
>>          If we note n the length of the prefix Pref64::/n, then n MUST
>>          the less or equal than 96.  If a Pref64::/n is configured
>>      
>            ^^^^^^^^
> s/the less or equal than 96/be less than or equal to 96/
>
> * Section 3.8.
>    
>>    If the destination IP address is an IPv4 address assigned to the
>>    NAT64 itself then the packet is a hairpin packet.  Hairpin packets
>>      
> Just to be more clear, I think we should explicitly mention this is
> talking about IPv4 address of the translated packet. For example,
>
>   If the destination IP address of the translated packet is an IPv4 address assigned to the ...
>
>
>    


From ebisawa@sablenetworks.net  Sun Feb 21 07:39:47 2010
Return-Path: <ebisawa@sablenetworks.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 94B7B3A81FC for <behave@core3.amsl.com>; Sun, 21 Feb 2010 07:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 FX5GtQxxlvZ7 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 07:39:46 -0800 (PST)
Received: from sablenetworks.net (sablenetworks.net [202.229.133.90]) by core3.amsl.com (Postfix) with ESMTP id 515F73A80FB for <behave@ietf.org>; Sun, 21 Feb 2010 07:39:46 -0800 (PST)
Received: (qmail 9456 invoked by SAV 20100221.017 by uid 0); 22 Feb 2010 00:41:40 +0900
Received: from unknown (HELO ?192.168.11.6?) (ebisawa@220.219.184.150) by dc12.etius.jp (202.229.133.90) with ESMTPA; 22 Feb 2010 00:41:40 +0900
Date: Mon, 22 Feb 2010 00:40:57 +0900
From: Kentaro Ebisawa <ebisawa@sablenetworks.net>
To: Xing Li <xing@cernet.edu.cn>
In-Reply-To: <4B7E934C.5070706@cernet.edu.cn>
References: <20100219174313.58C9.B01659E3@sablenetworks.net> <4B7E934C.5070706@cernet.edu.cn>
Message-Id: <20100222002640.58DD.B01659E3@sablenetworks.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.50 [ja]
Cc: "draft-ietf-behave-v6v4-xlate@tools.ietf.org" <draft-ietf-behave-v6v4-xlate@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Sun, 21 Feb 2010 15:39:47 -0000

Hi Xing,

In section 3.1., there is a description about sending "Fragment Needed"
message when DF=1 and translated packet is larger than the next-hop MTU.

>   If the DF bit is set and the MTU of the next-hop interface is less
>   than the total length value of the IPv4 packet plus 20, the
>   translator MUST send an ICMPv4 "Fragmentation Needed" error message
>   to the IPv4 source address.

But I noticed there is no corresponding description in section 4. that
translator should send PTB when DF=1 and translated packet is larger
than the next-hop MTU.

So I think it will be more clear if we add description like below.
# unless I missed it's mentioned someplace else in the doc.

* Section 4. [Page 18]
>   if there is no fragmentation header in the IPv6 packet, the
>   translator SHOULD set DF to 0 for the packets equal to or smaller
>   than 1280 bytes and set DF to 1 for packets larger than 1280 bytes.
If translated packet with DF set to 1 will be larger than the MTU of
the next-hop interface, then translator MUST drop packet and send
ICMPv6 "Packet Too Big" (Type 2/Code 0) error message to the IPv6
host with adjusted MTU in the ICMPv6 message.

Thanks,
-- 
Kentaro Ebisawa <ebisawa@sablenetworks.net>


On Fri, 19 Feb 2010 21:34:04 +0800
Xing Li <xing@cernet.edu.cn> wrote:

> Kentaro Ebisawa $B<LF;(B:
> > Hi,
> >
> > I've reviewed xlate-09 and here's some comments.
> >
> > 1. In "8. Appendix:", Address 166.111.1.2 is used as an example.
> >    Should't we use address from RFC5737 (198.51.100.0/24, 203.0.113.0/24) insted ?
> >   
> 
> yes. we will use the document block in next version.
> > 2. In "3.3.  Translating ICMPv4 Error Messages into ICMPv6" :
> >   
> >>   There are some differences between the ICMPv4 and the ICMPv6 error
> >>   message formats as detailed above.  In addition, the ICMP error
> >>   messages contain for the packet in error, which needs to be
> >>     
> >
> > I think it should be ...
> >
> >    message formats as detailed above.  In addition, the ICMP error
> >    messages contain packet in error, which needs to be
> >   
> 
> yes, corrected.
> 
> > 3. [Page 23]
> >   
> >>   addresses.  In this case, the translator can ether do stateful
> >>     
> >
> > ether -> either
> >
> >   
> yes, corrected.
> 
> thanks.
> 
> regards,
> 
> xing
> 
> > Thanks,
> >   
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From dwing@cisco.com  Sun Feb 21 09:30: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 60B2028C187 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 09:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.539
X-Spam-Level: 
X-Spam-Status: No, score=-10.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 Do0HDOLhn+TY for <behave@core3.amsl.com>; Sun, 21 Feb 2010 09:30:44 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 2BCAF3A7DE4 for <behave@ietf.org>; Sun, 21 Feb 2010 09:30:44 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcKABv9gEurR7Hu/2dsb2JhbACHTYESki5zohmXIIRrBIMV
X-IronPort-AV: E=Sophos;i="4.49,512,1262563200"; d="scan'208";a="154459488"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 21 Feb 2010 17:32:39 +0000
Received: from dwingwxp01 ([10.32.240.197]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o1LHWdOQ009224; Sun, 21 Feb 2010 17:32:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Hui Deng'" <denghui02@gmail.com>, "'Cameron Byrne'" <cb.list6@gmail.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com>
Date: Sun, 21 Feb 2010 09:32:38 -0800
Message-ID: <01eb01cab31b$dd9922d0$bea66b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcqvqKFbmaAwGIKbRIWqgcldcJvlqwDcye4g
In-Reply-To: <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: 'Andrew Sullivan' <ajs@shinkuro.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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: Sun, 21 Feb 2010 17:30:45 -0000

Hui,

I don't understand.  Are you proposing changes to =
draft-cao-behave-dsdns64, or
discussing something else?

-d


> -----Original Message-----
> From: Hui Deng [mailto:denghui02@gmail.com]=20
> Sent: Wednesday, February 17, 2010 12:10 AM
> To: Cameron Byrne
> Cc: Dan Wing; Andrew Sullivan; behave@ietf.org
> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>=20
> if we could prefer NAT64 than NAT44, it really benefit for IPv6,
> IETF should prefer IPv6 friend solution other than IPv4=20
> friend solution
>=20
> I also don't think that assigning unlimited IPv4 address to UE and
> encouraging them continue to use NAT44 is not a good way to go, when
> will IPv6 come?
>=20
> if we prefer 6 to 4, than I believe NAT64 could also be used for dual
> stack connection.
>=20
> thanks
>=20
> -Hui
>=20
> 2010/2/13 Cameron Byrne <cb.list6@gmail.com>:
> > On Fri, Feb 12, 2010 at 12:27 PM, Dan Wing <dwing@cisco.com> wrote:
> >>
> >>
> >>> -----Original Message-----
> >>> From: behave-bounces@ietf.org
> >>> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
> >>> Sent: Friday, February 12, 2010 11:52 AM
> >>> To: behave@ietf.org
> >>> Subject: [BEHAVE] draft-cao-behave-dsdns64-00
> >>>
> >>> Dear colleagues,
> >>>
> >>> I just read draft-cao-behave-dsdns64-00. =A0I confess that I am
> >>> completely mystified by it.
> >
> > I don't agree with the premise of the draft -- that traffic=20
> going via
> > a NAT64 is entirely bad. =A0In some environments maybe it is=20
> bad, but in
> > my environment 99% of the mobile phone / device traffic=20
> goes via NAT44
> > today. =A0NAT64 and NAT44 are very similar in function and cost to =
the
> > service provider. =A0If the flow goes via NAT44 or NAT64 it does not
> > matter to me, either way the user can access the content=20
> they want and
> > the service provider has to support / scale =A0"state" in the =
network
> > for that session(s). =A0If the user receives a natural AAAA record, =
i
> > have less NAT state since a natural (non-DNS64 synthesized) record
> > will bypass the NAT64 completely, thus saving me money since i don't
> > have to grow the NAT capacity for any native IPv6 content (keep in
> > mind Google and Youtube are the largest content sources in=20
> the USA ..
> > and they service native IPv6)
> >
> > So, using today's model, if all my users were IPv6-only with NAT64
> > instead of IPv4 with NAT44, i would have much less cost in=20
> the network
> > since native AAAA flows would not go via the NAT.
> >
> >
> >>>
> >>> The central point of the draft appears to be that the DNS64 should
> >>> handle A queries normally.
> >>>
> >>> There is no explanation of how that would even possibly work. =
=A0The
> >>> DNS64 works by synthesizing AAAA out of A records. =A0It=20
> _can't_ return
> >>> an A record because it will return the AAAA first.
> >>>
> >>> If that assumption is violated, actually, the entire=20
> DNS64 project is
> >>> doomed as near as I can tell.
> >>>
> >>> Have I missed something?
> >>
> >> It should work if the policy table IPv6/IPv4 preference is inverted
> >> from the default. =A0That is, the host's RFC3484 policy=20
> table could be
> >> changed to prefer IPv4.
> >>
> >
> > And this is exactly what we DO NOT want to happen. =A0Since it means
> > that only IPv6-only systems will go to IPv6 content, thus=20
> perpetuating
> > the "chicken and egg" problem to new unforeseen levels of=20
> stale-mate.
> >
> >> That would have significant implications, though: =A0if a server
> >> is dual-stacked, the dual-stack client will always use IPv4. =
=A0That
> >> IPv4 traffic is likely to be NATted (due to impending IPv4
> >> exhaustion and the need for the ISP to conserve IPv4 addresses),
> >> which will harm the user's experience if they need more TCP
> >> ports than available on the NAT. =A0Some applications need a lot
> >> of TCP ports, as we know -- the canonical example is Google Maps
> >> but there are other applications that also use a lot of TCP
> >
> > This is a very important point and a powerful trend with AJAX
> > webpages, here is the citation for NTT's work on this topic of MANY
> > MANY session consuming a great deal of NAT resources.
> >
> >=20
> http://www.nttv6.jp/~miyakawa/IETF72/IETF-IAB-TECH-PLENARY-NTT
> -miyakawa.pdf
> >
> >> ports. =A0To avoid the poor user experience of running out of
> >> TCP ports on the NAT, the content provider has an incentive to
> >> enable IPv6. =A0However, if the dual-stack client continues to
> >> prefer IPv4, the IPv6 path isn't used, and the user experience
> >> continues to be poor. =A0With such an address preference, the
> >> user experience only improves when the A record is no longer
> >> in the DNS. =A0That also means thousands, or millions, of
> >
> > Right, this leads to the proverbial flag-day that the IETF=20
> said would
> > never exists, because it will also invariably partition portions of
> > the Internet on the flag day
> >
> >> clients would suddenly switch from using IPv4 to using IPv6
> >> which would be a difficult adjustment for the content provider.
> >>
> >> -d
> >>
> >>
> >>> Best regards,
> >>>
> >>> A
> >>>
> >>> --
> >>> Andrew Sullivan
> >>> ajs@shinkuro.com
> >>> Shinkuro, Inc.
> >>> _______________________________________________
> >>> 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
> >>
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
>=20


From xing@cernet.edu.cn  Sun Feb 21 15:45:42 2010
Return-Path: <xing@cernet.edu.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 B219028C209 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 15:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.22
X-Spam-Level: 
X-Spam-Status: No, score=0.22 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 b4SzueYhqlSk for <behave@core3.amsl.com>; Sun, 21 Feb 2010 15:45:41 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 42AAE3A6A8A for <behave@ietf.org>; Sun, 21 Feb 2010 15:45:40 -0800 (PST)
Received: from [192.168.1.101]([124.225.138.242]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jmb4b822d5b; Mon, 22 Feb 2010 07:47:32 +0800
Message-ID: <4B81C608.1050404@cernet.edu.cn>
Date: Mon, 22 Feb 2010 07:47:20 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Kentaro Ebisawa <ebisawa@sablenetworks.net>
References: <20100219174313.58C9.B01659E3@sablenetworks.net> <4B7E934C.5070706@cernet.edu.cn> <20100222002640.58DD.B01659E3@sablenetworks.net>
In-Reply-To: <20100222002640.58DD.B01659E3@sablenetworks.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 13Y6VjXB
Cc: "draft-ietf-behave-v6v4-xlate@tools.ietf.org" <draft-ietf-behave-v6v4-xlate@tools.ietf.org>, "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-v6v4-xlate-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: Sun, 21 Feb 2010 23:45:42 -0000

Hi, Kentaro,

Thanks for your comment.

Kentaro Ebisawa $B<LF;(B:
> Hi Xing,
>
> In section 3.1., there is a description about sending "Fragment Needed"
> message when DF=1 and translated packet is larger than the next-hop MTU.
>
>   
>>   If the DF bit is set and the MTU of the next-hop interface is less
>>   than the total length value of the IPv4 packet plus 20, the
>>   translator MUST send an ICMPv4 "Fragmentation Needed" error message
>>   to the IPv4 source address.
>>     
>
> But I noticed there is no corresponding description in section 4. that
> translator should send PTB when DF=1 and translated packet is larger
> than the next-hop MTU.
>
> So I think it will be more clear if we add description like below.
> # unless I missed it's mentioned someplace else in the doc.
>
> * Section 4. [Page 18]
>   
>>   if there is no fragmentation header in the IPv6 packet, the
>>   translator SHOULD set DF to 0 for the packets equal to or smaller
>>   than 1280 bytes and set DF to 1 for packets larger than 1280 bytes.
>>     
> If translated packet with DF set to 1 will be larger than the MTU of
> the next-hop interface, then translator MUST drop packet and send
> ICMPv6 "Packet Too Big" (Type 2/Code 0) error message to the IPv6
> host with adjusted MTU in the ICMPv6 message.
>   

The reasons we did not have this paragraph is that in general this will
not happen, since from IPv6->IPv4, the packet size will be 20 byte smaller.

Using your suggested wording, we can make it more clear. Thanks.

Regards,

xing


> Thanks,
>   


From denghui02@gmail.com  Sun Feb 21 18:19:31 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 6DD6128C219 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 18:19:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level: 
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[AWL=0.202,  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 cAAlXE-fDbZw for <behave@core3.amsl.com>; Sun, 21 Feb 2010 18:19:30 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id EBC9F28C129 for <behave@ietf.org>; Sun, 21 Feb 2010 18:19:29 -0800 (PST)
Received: by pwi3 with SMTP id 3so2236624pwi.31 for <behave@ietf.org>; Sun, 21 Feb 2010 18:21:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=B5WihE++fa9tUrxSf7zbB5IZzVzAaHdeiSqnHdr4qP4=; b=CnU5n8xSFDWma8X9MWLdllN4vZB0ppy4YXiqTozVccj39RuAY6AniAQQ07qF+TikOX w63N/8Ur9A1hhP1ICPoFDWj8dfj75OzmTlMWWd92U8N9AkjkfrrvU81LwQqxEOuSji95 zOybmSlBNHKWxMNM4pRCD0u+g13kzuSAJIs54=
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 :cc:content-type:content-transfer-encoding; b=D9u0zD5OzlFeFJozenQvDvUDqR5YDXXD724j0jTwgDk+ZMA2ZvmLp+WcyjeQPTUF5x eGlO1G1XpWpkdXTHRbfpK+7YSo6LhEU9x+75Q2cOJEwdK/CJjaVe8h6S9yo3ocbrfue5 /zmk3iAUUQGQY7x1ucojLMyZMDKlhtjVUopNc=
MIME-Version: 1.0
Received: by 10.141.106.15 with SMTP id i15mr991652rvm.252.1266805283463; Sun,  21 Feb 2010 18:21:23 -0800 (PST)
In-Reply-To: <01eb01cab31b$dd9922d0$bea66b80@cisco.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com>
Date: Mon, 22 Feb 2010 10:21:23 +0800
Message-ID: <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Andrew Sullivan <ajs@shinkuro.com>, Cameron Byrne <cb.list6@gmail.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 22 Feb 2010 02:19:31 -0000

Dan,

I guess that I used two No in that sentence, that is not correct.

what I mean is that I would like to support NAT64 is prior to NAT44,
secondly, if NAT64 could be used in dual stack network, that's also good.

thanks

-Hui

2010/2/22 Dan Wing <dwing@cisco.com>:
> Hui,
>
> I don't understand. =A0Are you proposing changes to draft-cao-behave-dsdn=
s64, or
> discussing something else?
>
> -d
>
>
>> -----Original Message-----
>> From: Hui Deng [mailto:denghui02@gmail.com]
>> Sent: Wednesday, February 17, 2010 12:10 AM
>> To: Cameron Byrne
>> Cc: Dan Wing; Andrew Sullivan; behave@ietf.org
>> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>>
>> if we could prefer NAT64 than NAT44, it really benefit for IPv6,
>> IETF should prefer IPv6 friend solution other than IPv4
>> friend solution
>>
>> I also don't think that assigning unlimited IPv4 address to UE and
>> encouraging them continue to use NAT44 is not a good way to go, when
>> will IPv6 come?
>>
>> if we prefer 6 to 4, than I believe NAT64 could also be used for dual
>> stack connection.
>>
>> thanks
>>
>> -Hui
>>
>> 2010/2/13 Cameron Byrne <cb.list6@gmail.com>:
>> > On Fri, Feb 12, 2010 at 12:27 PM, Dan Wing <dwing@cisco.com> wrote:
>> >>
>> >>
>> >>> -----Original Message-----
>> >>> From: behave-bounces@ietf.org
>> >>> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
>> >>> Sent: Friday, February 12, 2010 11:52 AM
>> >>> To: behave@ietf.org
>> >>> Subject: [BEHAVE] draft-cao-behave-dsdns64-00
>> >>>
>> >>> Dear colleagues,
>> >>>
>> >>> I just read draft-cao-behave-dsdns64-00. =A0I confess that I am
>> >>> completely mystified by it.
>> >
>> > I don't agree with the premise of the draft -- that traffic
>> going via
>> > a NAT64 is entirely bad. =A0In some environments maybe it is
>> bad, but in
>> > my environment 99% of the mobile phone / device traffic
>> goes via NAT44
>> > today. =A0NAT64 and NAT44 are very similar in function and cost to the
>> > service provider. =A0If the flow goes via NAT44 or NAT64 it does not
>> > matter to me, either way the user can access the content
>> they want and
>> > the service provider has to support / scale =A0"state" in the network
>> > for that session(s). =A0If the user receives a natural AAAA record, i
>> > have less NAT state since a natural (non-DNS64 synthesized) record
>> > will bypass the NAT64 completely, thus saving me money since i don't
>> > have to grow the NAT capacity for any native IPv6 content (keep in
>> > mind Google and Youtube are the largest content sources in
>> the USA ..
>> > and they service native IPv6)
>> >
>> > So, using today's model, if all my users were IPv6-only with NAT64
>> > instead of IPv4 with NAT44, i would have much less cost in
>> the network
>> > since native AAAA flows would not go via the NAT.
>> >
>> >
>> >>>
>> >>> The central point of the draft appears to be that the DNS64 should
>> >>> handle A queries normally.
>> >>>
>> >>> There is no explanation of how that would even possibly work. =A0The
>> >>> DNS64 works by synthesizing AAAA out of A records. =A0It
>> _can't_ return
>> >>> an A record because it will return the AAAA first.
>> >>>
>> >>> If that assumption is violated, actually, the entire
>> DNS64 project is
>> >>> doomed as near as I can tell.
>> >>>
>> >>> Have I missed something?
>> >>
>> >> It should work if the policy table IPv6/IPv4 preference is inverted
>> >> from the default. =A0That is, the host's RFC3484 policy
>> table could be
>> >> changed to prefer IPv4.
>> >>
>> >
>> > And this is exactly what we DO NOT want to happen. =A0Since it means
>> > that only IPv6-only systems will go to IPv6 content, thus
>> perpetuating
>> > the "chicken and egg" problem to new unforeseen levels of
>> stale-mate.
>> >
>> >> That would have significant implications, though: =A0if a server
>> >> is dual-stacked, the dual-stack client will always use IPv4. =A0That
>> >> IPv4 traffic is likely to be NATted (due to impending IPv4
>> >> exhaustion and the need for the ISP to conserve IPv4 addresses),
>> >> which will harm the user's experience if they need more TCP
>> >> ports than available on the NAT. =A0Some applications need a lot
>> >> of TCP ports, as we know -- the canonical example is Google Maps
>> >> but there are other applications that also use a lot of TCP
>> >
>> > This is a very important point and a powerful trend with AJAX
>> > webpages, here is the citation for NTT's work on this topic of MANY
>> > MANY session consuming a great deal of NAT resources.
>> >
>> >
>> http://www.nttv6.jp/~miyakawa/IETF72/IETF-IAB-TECH-PLENARY-NTT
>> -miyakawa.pdf
>> >
>> >> ports. =A0To avoid the poor user experience of running out of
>> >> TCP ports on the NAT, the content provider has an incentive to
>> >> enable IPv6. =A0However, if the dual-stack client continues to
>> >> prefer IPv4, the IPv6 path isn't used, and the user experience
>> >> continues to be poor. =A0With such an address preference, the
>> >> user experience only improves when the A record is no longer
>> >> in the DNS. =A0That also means thousands, or millions, of
>> >
>> > Right, this leads to the proverbial flag-day that the IETF
>> said would
>> > never exists, because it will also invariably partition portions of
>> > the Internet on the flag day
>> >
>> >> clients would suddenly switch from using IPv4 to using IPv6
>> >> which would be a difficult adjustment for the content provider.
>> >>
>> >> -d
>> >>
>> >>
>> >>> Best regards,
>> >>>
>> >>> A
>> >>>
>> >>> --
>> >>> Andrew Sullivan
>> >>> ajs@shinkuro.com
>> >>> Shinkuro, Inc.
>> >>> _______________________________________________
>> >>> 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
>> >>
>> > _______________________________________________
>> > Behave mailing list
>> > Behave@ietf.org
>> > https://www.ietf.org/mailman/listinfo/behave
>> >
>>
>
>

From ssenthil@cisco.com  Sun Feb 21 18:40:37 2010
Return-Path: <ssenthil@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 1B9D23A8295 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 18:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.391
X-Spam-Level: 
X-Spam-Status: No, score=-10.391 tagged_above=-999 required=5 tests=[AWL=0.208, 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 1xFlDckcvZR9 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 18:40:35 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id C6A853A6926 for <behave@ietf.org>; Sun, 21 Feb 2010 18:40:33 -0800 (PST)
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: AvsEAMZ9gUurR7Hu/2dsb2JhbACbBHOjcZcxhGsEgxU
X-IronPort-AV: E=Sophos;i="4.49,514,1262563200"; d="scan'208";a="90665518"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 22 Feb 2010 02:42:29 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o1M2gSBt001409; Mon, 22 Feb 2010 02:42:29 GMT
Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 21 Feb 2010 18:42:29 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 21 Feb 2010 18:42:28 -0800
Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB09721D67@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <4B7FF5C9.1080208@viagenie.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] NAT64: Out of order session handling
Thread-Index: AcqyO41ygjf1BcanR/WJqQSOg/RdrABLD3LQ
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>	<4B7F4B3F.9050607@cernet.edu.cn>	<4B7F5D63.1070409@gmail.com><4B7F7582.8000700@cernet.edu.cn> <4B7FF5C9.1080208@viagenie.ca>
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: "Simon Perreault" <simon.perreault@viagenie.ca>, <behave@ietf.org>
X-OriginalArrivalTime: 22 Feb 2010 02:42:29.0830 (UTC) FILETIME=[AD42FE60:01CAB368]
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 22 Feb 2010 02:40:37 -0000

=20

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of Simon Perreault
Sent: Saturday, February 20, 2010 9:47 AM
To: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling

On 02/20/2010 12:39 AM, Xing Li wrote:
> a translator that wants to multithread should avoid changing the order

> of the packets.
>=20
> Is this the correct understanding? Do you have a suggested wording?
Thanks.

It's not perfect because it mentions "multithreading", which is an
implementation detail. Only externally-observable behaviour should be
part of the spec.

For the record, I find Brian's wording perfect. Here it is again:

> Translators SHOULD be designed to avoid packet reordering as much as=20
> possible.

[Senthil] This text, IMO, is not implementable. The translator cannot
avoid reordering
unless it keeps track of ordering. It cannot order if the packets are
going through different translators.=20
I don't know how to quantify "as much as possible", under what
conditions it is ok to reorder?
Instead something like this could be more useful.
"Translator should make sure that the packets leave the translator in
the same order in which they arrived".

But this will have some issues with translators doing ALG functionality,
but that would be a separate discussion.

Senthil


Thanks,
Simon
--=20
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

From ssenthil@cisco.com  Sun Feb 21 18:43:09 2010
Return-Path: <ssenthil@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 B3DD13A8373 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 18:43:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.426
X-Spam-Level: 
X-Spam-Status: No, score=-10.426 tagged_above=-999 required=5 tests=[AWL=0.173, 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 dUlxXEYB3Xil for <behave@core3.amsl.com>; Sun, 21 Feb 2010 18:43:08 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id CD0DB3A8372 for <behave@ietf.org>; Sun, 21 Feb 2010 18:43:08 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALZ+gUurR7H+/2dsb2JhbACbBHOjd5cyhGsEgxU
X-IronPort-AV: E=Sophos;i="4.49,514,1262563200"; d="scan'208";a="241498900"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 22 Feb 2010 02:45:05 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o1M2j5N1008795; Mon, 22 Feb 2010 02:45:05 GMT
Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 21 Feb 2010 18:45:05 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 21 Feb 2010 18:45:04 -0800
Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB09721D68@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB09721D67@xmb-sjc-236.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] NAT64: Out of order session handling
Thread-Index: AcqyO41ygjf1BcanR/WJqQSOg/RdrABLD3LQAAA/SFA=
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>	<4B7F4B3F.9050607@cernet.edu.cn>	<4B7F5D63.1070409@gmail.com><4B7F7582.8000700@cernet.edu.cn><4B7FF5C9.1080208@viagenie.ca> <85B2F271FDF6B949B3672BA5A7BB62FB09721D67@xmb-sjc-236.amer.cisco.com>
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>, "Simon Perreault" <simon.perreault@viagenie.ca>, <behave@ietf.org>
X-OriginalArrivalTime: 22 Feb 2010 02:45:05.0797 (UTC) FILETIME=[0A39AB50:01CAB369]
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 22 Feb 2010 02:43:09 -0000

Corrected text below.=20

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of Senthil Sivakumar (ssenthil)
Sent: Sunday, February 21, 2010 9:42 PM
To: Simon Perreault; behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling


=20

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of Simon Perreault
Sent: Saturday, February 20, 2010 9:47 AM
To: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling

On 02/20/2010 12:39 AM, Xing Li wrote:
> a translator that wants to multithread should avoid changing the order

> of the packets.
>=20
> Is this the correct understanding? Do you have a suggested wording?
Thanks.

It's not perfect because it mentions "multithreading", which is an
implementation detail. Only externally-observable behaviour should be
part of the spec.

For the record, I find Brian's wording perfect. Here it is again:

> Translators SHOULD be designed to avoid packet reordering as much as=20
> possible.

[Senthil] This text, IMO, is not implementable. The translator cannot
avoid reordering unless it keeps track of ordering. It cannot order if
the packets are going through different translators.=20
I don't know how to quantify "as much as possible", under what
conditions it is ok to reorder?
Instead something like this could be more useful.
"Translator should make sure that the packets leave the translator in
the same order in which they arrived".

[Senthil] Should be,=20
"Translator should make sure that the packets belonging to the same flow
leave the translator in the same order in which they arrived".

But this will have some issues with translators doing ALG functionality,
but that would be a separate discussion.

Senthil


Thanks,
Simon
--=20
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org
_______________________________________________
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 ebisawa@sablenetworks.net  Sun Feb 21 19:50:38 2010
Return-Path: <ebisawa@sablenetworks.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 893FC28C21A for <behave@core3.amsl.com>; Sun, 21 Feb 2010 19:50:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 L+5ktakDT1V3 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 19:50:37 -0800 (PST)
Received: from sablenetworks.net (sablenetworks.net [202.229.133.90]) by core3.amsl.com (Postfix) with ESMTP id 27BEB28C129 for <behave@ietf.org>; Sun, 21 Feb 2010 19:50:36 -0800 (PST)
Received: (qmail 12626 invoked by SAV 20100221.041 by uid 0); 22 Feb 2010 12:52:32 +0900
Received: from unknown (HELO ?192.168.11.6?) (ebisawa@220.219.184.150) by dc12.etius.jp (202.229.133.90) with ESMTPA; 22 Feb 2010 12:52:32 +0900
Date: Mon, 22 Feb 2010 12:52:08 +0900
From: Kentaro Ebisawa <ebisawa@sablenetworks.net>
To: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB09721D68@xmb-sjc-236.amer.cisco.com>
References: <85B2F271FDF6B949B3672BA5A7BB62FB09721D67@xmb-sjc-236.amer.cisco.com> <85B2F271FDF6B949B3672BA5A7BB62FB09721D68@xmb-sjc-236.amer.cisco.com>
Message-Id: <20100222124153.58E7.B01659E3@sablenetworks.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.50 [ja]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 22 Feb 2010 03:50:38 -0000

Hi,

> [Senthil] Should be, 
> "Translator should make sure that the packets belonging to the same flow
> leave the translator in the same order in which they arrived".
> 
> But this will have some issues with translators doing ALG functionality,
> but that would be a separate discussion.

I think exception to this is when handling fragmented packets.
In compliance to Section 3.4. Page 19, implementation should have
freedom to queue and sort fragments in order or translate packets
as they arrive.

Thanks,
-- 
Kentaro Ebisawa <ebisawa@sablenetworks.net>


On Sun, 21 Feb 2010 18:45:04 -0800
"Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com> wrote:

> Corrected text below. 
> 
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Senthil Sivakumar (ssenthil)
> Sent: Sunday, February 21, 2010 9:42 PM
> To: Simon Perreault; behave@ietf.org
> Subject: Re: [BEHAVE] NAT64: Out of order session handling
> 
> 
>  
> 
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Simon Perreault
> Sent: Saturday, February 20, 2010 9:47 AM
> To: behave@ietf.org
> Subject: Re: [BEHAVE] NAT64: Out of order session handling
> 
> On 02/20/2010 12:39 AM, Xing Li wrote:
> > a translator that wants to multithread should avoid changing the order
> 
> > of the packets.
> > 
> > Is this the correct understanding? Do you have a suggested wording?
> Thanks.
> 
> It's not perfect because it mentions "multithreading", which is an
> implementation detail. Only externally-observable behaviour should be
> part of the spec.
> 
> For the record, I find Brian's wording perfect. Here it is again:
> 
> > Translators SHOULD be designed to avoid packet reordering as much as 
> > possible.
> 
> [Senthil] This text, IMO, is not implementable. The translator cannot
> avoid reordering unless it keeps track of ordering. It cannot order if
> the packets are going through different translators. 
> I don't know how to quantify "as much as possible", under what
> conditions it is ok to reorder?
> Instead something like this could be more useful.
> "Translator should make sure that the packets leave the translator in
> the same order in which they arrived".
> 
> [Senthil] Should be, 
> "Translator should make sure that the packets belonging to the same flow
> leave the translator in the same order in which they arrived".
> 
> But this will have some issues with translators doing ALG functionality,
> but that would be a separate discussion.
> 
> Senthil
> 
> 
> Thanks,
> Simon
> -- 
> DNS64 open-source   --> http://ecdysis.viagenie.ca
> STUN/TURN server    --> http://numb.viagenie.ca
> vCard 4.0           --> http://www.vcarddav.org
> _______________________________________________
> 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
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From rpenno@juniper.net  Sun Feb 21 21:03:20 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 4C30A28C196 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 21:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.065
X-Spam-Level: 
X-Spam-Status: No, score=-6.065 tagged_above=-999 required=5 tests=[AWL=0.534,  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 QbI0-pYG0g7E for <behave@core3.amsl.com>; Sun, 21 Feb 2010 21:03:19 -0800 (PST)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by core3.amsl.com (Postfix) with ESMTP id 9057728C236 for <behave@ietf.org>; Sun, 21 Feb 2010 21:03:17 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKS4IQip6fI3aqwfN4/T2SgD2paxr4RrgU@postini.com; Sun, 21 Feb 2010 21:05:17 PST
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.1.393.1; Sun, 21 Feb 2010 21:03:08 -0800
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; Mon, 22 Feb 2010 00:03:07 -0500
From: Reinaldo Penno <rpenno@juniper.net>
To: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>, Simon Perreault <simon.perreault@viagenie.ca>, "behave@ietf.org" <behave@ietf.org>
Date: Mon, 22 Feb 2010 00:03:05 -0500
Thread-Topic: [BEHAVE] NAT64: Out of order session handling
Thread-Index: AcqyO41ygjf1BcanR/WJqQSOg/RdrABLD3LQAAA/SFAABOIq/g==
Message-ID: <C7A75009.13F7A%rpenno@juniper.net>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB09721D68@xmb-sjc-236.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.3.0.091002
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 22 Feb 2010 05:03:20 -0000

I think this text is fine.


On 2/21/10 6:45 PM, "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
wrote:

> [Senthil] Should be,
> "Translator should make sure that the packets belonging to the same flow
> leave the translator in the same order in which they arrived".


From wangxuewei@huawei.com  Sun Feb 21 22:04:49 2010
Return-Path: <wangxuewei@huawei.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 1218C28C196 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 22:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.682
X-Spam-Level: 
X-Spam-Status: No, score=0.682 tagged_above=-999 required=5 tests=[AWL=1.177,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 ss1fFiWo3BIe for <behave@core3.amsl.com>; Sun, 21 Feb 2010 22:04:48 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 0139D28C169 for <behave@ietf.org>; Sun, 21 Feb 2010 22:04:48 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KY800606BMYM3@szxga02-in.huawei.com> for behave@ietf.org; Mon, 22 Feb 2010 14:06:34 +0800 (CST)
Received: from w00104636 ([10.111.12.167]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KY800A84BMX92@szxga02-in.huawei.com> for behave@ietf.org; Mon, 22 Feb 2010 14:06:34 +0800 (CST)
Date: Mon, 22 Feb 2010 14:06:33 +0800
From: Xuewei Wang <wangxuewei@huawei.com>
To: behave@ietf.org
Message-id: <016901cab385$2f91d870$a70c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Cc: Cameron Byrne <cb.list6@gmail.com>, Yan Wang <wangyan-lab@cnnic.cn>, Xiaohu Xu <xuxh@huawei.com>, zhangdacheng@huawei.com
Subject: [BEHAVE] Fw: New Version Notification for draft-wang-behave-nat64-load-balancer-01
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, 22 Feb 2010 06:04:49 -0000

A new version of I-D, draft-wang-behave-nat64-load-balancer-01.txt has been submitted. 
There were several changes made between the -00 and -01 versions of this draft:
o Added some discussions about pros and cons at section 3.1.
o Added a new mechanism at section 4.2.2.
o Add minor mathematical corrections.

Any comments are welcome, thanks.


Xuewei Wang
----- Original Message ----- 
From: "IETF I-D Submission Tool" <idsubmission@ietf.org>
To: <wangxuewei@huawei.com>
Cc: <zhangdacheng@huawei.com>
Sent: Monday, February 22, 2010 12:08 PM
Subject: New Version Notification for draft-wang-behave-nat64-load-balancer-01


> 
> A new version of I-D, draft-wang-behave-nat64-load-balancer-01.txt has been successfuly submitted by Xuewei Wang and posted to the IETF repository.
> 
> Filename: draft-wang-behave-nat64-load-balancer
> Revision: 01
> Title: Some Considerations on the Load-Balancer for NAT64
> Creation_date: 2010-02-22
> WG ID: Independent Submission
> Number_of_pages: 10
> 
> Abstract:
> [STANDBY] has discussed how to achieve load-balancing among a group 
> of NAT64 devices, however, it doesn't mention the mechanism to 
> achieve load-balancing with load-balancers, e.g., how to assign 
> different prefix64s to different hosts. In this memo, we propose our 
> investigation on this topic.
>                                                                                  
> 
> 
> The IETF Secretariat.
> 
>

From dwing@cisco.com  Sun Feb 21 22:49:52 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 C48A23A82B9 for <behave@core3.amsl.com>; Sun, 21 Feb 2010 22:49:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level: 
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 Qm203Us-IJaN for <behave@core3.amsl.com>; Sun, 21 Feb 2010 22:49:51 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 5A70D3A8070 for <behave@ietf.org>; Sun, 21 Feb 2010 22:49:51 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMHAOa3gUurR7Ht/2dsb2JhbACHTYESkidzo2+XM4RrBIMV
X-IronPort-AV: E=Sophos;i="4.49,516,1262563200"; d="scan'208";a="486549108"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 22 Feb 2010 06:51:48 +0000
Received: from dwingwxp01 ([10.32.240.197]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o1M6pm7X017428; Mon, 22 Feb 2010 06:51:48 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Hui Deng'" <denghui02@gmail.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com> <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com>
Date: Sun, 21 Feb 2010 22:51:48 -0800
Message-ID: <027b01cab38b$81b0bcb0$bea66b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcqzZbrE26177zsIS0eGYIV1ZVQI5QAJZcnQ
In-Reply-To: <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: 'Andrew Sullivan' <ajs@shinkuro.com>, 'Cameron Byrne' <cb.list6@gmail.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 22 Feb 2010 06:49:52 -0000

=20

> -----Original Message-----
> From: Hui Deng [mailto:denghui02@gmail.com]=20
> Sent: Sunday, February 21, 2010 6:21 PM
> To: Dan Wing
> Cc: Cameron Byrne; Andrew Sullivan; behave@ietf.org
> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>=20
> Dan,
>=20
> I guess that I used two No in that sentence, that is not correct.
>=20
> what I mean is that I would like to support NAT64 is prior to NAT44,
> secondly, if NAT64 could be used in dual stack network,=20
> that's also good.

Sorry, I still do not understand. =20

Earlier in this email thread, Andrew, Cameron, and I pointed out that
draft-cao-behave-dsdns64-00 does not fully describe its solution.  I =
look
forward to a more complete description so I can understand the proposal.

-d


> thanks
>=20
> -Hui
>=20
> 2010/2/22 Dan Wing <dwing@cisco.com>:
> > Hui,
> >
> > I don't understand. =A0Are you proposing changes to=20
> draft-cao-behave-dsdns64, or
> > discussing something else?
> >
> > -d
> >
> >
> >> -----Original Message-----
> >> From: Hui Deng [mailto:denghui02@gmail.com]
> >> Sent: Wednesday, February 17, 2010 12:10 AM
> >> To: Cameron Byrne
> >> Cc: Dan Wing; Andrew Sullivan; behave@ietf.org
> >> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
> >>
> >> if we could prefer NAT64 than NAT44, it really benefit for IPv6,
> >> IETF should prefer IPv6 friend solution other than IPv4
> >> friend solution
> >>
> >> I also don't think that assigning unlimited IPv4 address to UE and
> >> encouraging them continue to use NAT44 is not a good way=20
> to go, when
> >> will IPv6 come?
> >>
> >> if we prefer 6 to 4, than I believe NAT64 could also be=20
> used for dual
> >> stack connection.
> >>
> >> thanks
> >>
> >> -Hui
> >>
> >> 2010/2/13 Cameron Byrne <cb.list6@gmail.com>:
> >> > On Fri, Feb 12, 2010 at 12:27 PM, Dan Wing=20
> <dwing@cisco.com> wrote:
> >> >>
> >> >>
> >> >>> -----Original Message-----
> >> >>> From: behave-bounces@ietf.org
> >> >>> [mailto:behave-bounces@ietf.org] On Behalf Of Andrew Sullivan
> >> >>> Sent: Friday, February 12, 2010 11:52 AM
> >> >>> To: behave@ietf.org
> >> >>> Subject: [BEHAVE] draft-cao-behave-dsdns64-00
> >> >>>
> >> >>> Dear colleagues,
> >> >>>
> >> >>> I just read draft-cao-behave-dsdns64-00. =A0I confess that I am
> >> >>> completely mystified by it.
> >> >
> >> > I don't agree with the premise of the draft -- that traffic
> >> going via
> >> > a NAT64 is entirely bad. =A0In some environments maybe it is
> >> bad, but in
> >> > my environment 99% of the mobile phone / device traffic
> >> goes via NAT44
> >> > today. =A0NAT64 and NAT44 are very similar in function and=20
> cost to the
> >> > service provider. =A0If the flow goes via NAT44 or NAT64=20
> it does not
> >> > matter to me, either way the user can access the content
> >> they want and
> >> > the service provider has to support / scale =A0"state" in=20
> the network
> >> > for that session(s). =A0If the user receives a natural=20
> AAAA record, i
> >> > have less NAT state since a natural (non-DNS64=20
> synthesized) record
> >> > will bypass the NAT64 completely, thus saving me money=20
> since i don't
> >> > have to grow the NAT capacity for any native IPv6=20
> content (keep in
> >> > mind Google and Youtube are the largest content sources in
> >> the USA ..
> >> > and they service native IPv6)
> >> >
> >> > So, using today's model, if all my users were IPv6-only=20
> with NAT64
> >> > instead of IPv4 with NAT44, i would have much less cost in
> >> the network
> >> > since native AAAA flows would not go via the NAT.
> >> >
> >> >
> >> >>>
> >> >>> The central point of the draft appears to be that the=20
> DNS64 should
> >> >>> handle A queries normally.
> >> >>>
> >> >>> There is no explanation of how that would even=20
> possibly work. =A0The
> >> >>> DNS64 works by synthesizing AAAA out of A records. =A0It
> >> _can't_ return
> >> >>> an A record because it will return the AAAA first.
> >> >>>
> >> >>> If that assumption is violated, actually, the entire
> >> DNS64 project is
> >> >>> doomed as near as I can tell.
> >> >>>
> >> >>> Have I missed something?
> >> >>
> >> >> It should work if the policy table IPv6/IPv4 preference=20
> is inverted
> >> >> from the default. =A0That is, the host's RFC3484 policy
> >> table could be
> >> >> changed to prefer IPv4.
> >> >>
> >> >
> >> > And this is exactly what we DO NOT want to happen. =A0
> Since it means
> >> > that only IPv6-only systems will go to IPv6 content, thus
> >> perpetuating
> >> > the "chicken and egg" problem to new unforeseen levels of
> >> stale-mate.
> >> >
> >> >> That would have significant implications, though: =A0if a server
> >> >> is dual-stacked, the dual-stack client will always use=20
> IPv4. =A0That
> >> >> IPv4 traffic is likely to be NATted (due to impending IPv4
> >> >> exhaustion and the need for the ISP to conserve IPv4 addresses),
> >> >> which will harm the user's experience if they need more TCP
> >> >> ports than available on the NAT. =A0Some applications need a lot
> >> >> of TCP ports, as we know -- the canonical example is Google Maps
> >> >> but there are other applications that also use a lot of TCP
> >> >
> >> > This is a very important point and a powerful trend with AJAX
> >> > webpages, here is the citation for NTT's work on this=20
> topic of MANY
> >> > MANY session consuming a great deal of NAT resources.
> >> >
> >> >
> >> http://www.nttv6.jp/~miyakawa/IETF72/IETF-IAB-TECH-PLENARY-NTT
> >> -miyakawa.pdf
> >> >
> >> >> ports. =A0To avoid the poor user experience of running out of
> >> >> TCP ports on the NAT, the content provider has an incentive to
> >> >> enable IPv6. =A0However, if the dual-stack client continues to
> >> >> prefer IPv4, the IPv6 path isn't used, and the user experience
> >> >> continues to be poor. =A0With such an address preference, the
> >> >> user experience only improves when the A record is no longer
> >> >> in the DNS. =A0That also means thousands, or millions, of
> >> >
> >> > Right, this leads to the proverbial flag-day that the IETF
> >> said would
> >> > never exists, because it will also invariably partition=20
> portions of
> >> > the Internet on the flag day
> >> >
> >> >> clients would suddenly switch from using IPv4 to using IPv6
> >> >> which would be a difficult adjustment for the content provider.
> >> >>
> >> >> -d
> >> >>
> >> >>
> >> >>> Best regards,
> >> >>>
> >> >>> A
> >> >>>
> >> >>> --
> >> >>> Andrew Sullivan
> >> >>> ajs@shinkuro.com
> >> >>> Shinkuro, Inc.
> >> >>> _______________________________________________
> >> >>> 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
> >> >>
> >> > _______________________________________________
> >> > Behave mailing list
> >> > Behave@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/behave
> >> >
> >>
> >
> >


From matthijs@nlnetlabs.nl  Mon Feb 22 01:35:09 2010
Return-Path: <matthijs@nlnetlabs.nl>
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 8E38F3A82C2 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 01:35:09 -0800 (PST)
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 7rNwPtBYG0Kf for <behave@core3.amsl.com>; Mon, 22 Feb 2010 01:35:08 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id 5A52E3A80CA for <behave@ietf.org>; Mon, 22 Feb 2010 01:35:07 -0800 (PST)
Received: from [IPv6:2001:7b8:206:1:215:afff:fed2:e121] ([IPv6:2001:7b8:206:1:215:afff:fed2:e121]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.3/8.14.3) with ESMTP id o1M9b11c081631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <behave@ietf.org>; Mon, 22 Feb 2010 10:37:03 +0100 (CET) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4B825084.7010908@nlnetlabs.nl>
Date: Mon, 22 Feb 2010 10:38:12 +0100
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
Organization: NLnet Labs
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: behave@ietf.org
References: <20100215164502.935AB28C10C@core3.amsl.com>	<20100215164837.GQ25973@shinkuro.com>	<4B7D3C29.2000109@nlnetlabs.nl>	<201002182245.o1IMjsO1028957@drugs.dv.isc.org>	<4B7E9113.2050205@viagenie.ca> <201002192216.o1JMGT7q089538@drugs.dv.isc.org>
In-Reply-To: <201002192216.o1JMGT7q089538@drugs.dv.isc.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Mon, 22 Feb 2010 10:37:03 +0100 (CET)
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-06.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: Mon, 22 Feb 2010 09:35:09 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Andrews wrote:
>>From a implemention point of view you have success (NOERROR or
> NXDOMAIN) and failure of the AAAA query.  Requerying for A after
> failure made some sense 10 years ago but should have been removed
> about 5 years ago.  All it is doing now is causing extra work to
> be done for almost no benefit.

I was rereading the thread DNS64: 'SERVFAIL on AAAA query, but A record
available'
[http://www.ietf.org/mail-archive/web/behave/current/msg07668.html]

And this has all been discussed before. True: querying for A records
after a AAAA query failed increases extra work for almost no benefit.
The reason (I believe, correct me if I'm wrong) to put it in the draft
anyway is that dual-stack also, already makes that increase, so NAT64
can be just as 'gentle'. My first remark is that if you are going to do
this, you should also mention other failures (like time out).

Now, I don't think 'dual-stack is doing it' is a good reason to make
this decision. 'Additional work for almost no benefit' is a stronger
reason. So, only if the resolver believes that requerying benefits the
end user, it should do so. FORMERR, SERVFAIL, NXDOMAIN, NOTIMPL*,
REFUSED and time out are no valid reasons. NOERROR (no data) is.

In that case, I prefer section 5.1.2 from draft-ietf-behave-dns64-04.

Best regards,

Matthijs


* If NOTIMPL is being returned, you can argue that the name server does
not implement IPv6 address records. But, it should have handled the
query type as an unknown DNS RR type.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJLglB5AAoJEA8yVCPsQCW5uAoH/RCq+YXbxssSBKyocKY7gK1q
RwjziePdKD6k0tNz5aP0C5y4g59lAQliDEcIkR0C6LoLw09ppnQsugzgVyOq7hNv
HYMNric6rcC/04cz4TtwBcJzvNzKz87E5HG5io6cx71/UPCkuEdpKMl1FHfB+Z6j
Vln+7qnmTSuKhU3QrNi/ZMY97h0AY/OLx13lMYeNjPaGWaIgOdjChUBOm8d9pq6e
QWzxG89eqjU69wDG6J5J6UIPxBesyKGQQUqd6ui016P6auJbC8er8malvR3s7udn
WxMDxMtraTTajFeHvVoHKZZuKensF1Zs7+HnUEDy78Tq0DBWXoROcBIKJ/y7ZwE=
=Y6/f
-----END PGP SIGNATURE-----

From simon.perreault@viagenie.ca  Mon Feb 22 05:09:10 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 9EBF928C122 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 05:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 PtoCQnMgugvp for <behave@core3.amsl.com>; Mon, 22 Feb 2010 05:09:08 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id 1E1323A83CF for <behave@ietf.org>; Mon, 22 Feb 2010 05:09:08 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 06E292151F; Mon, 22 Feb 2010 08:11:03 -0500 (EST)
Message-ID: <4B828264.8060103@viagenie.ca>
Date: Mon, 22 Feb 2010 08:11:00 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: Reinaldo Penno <rpenno@juniper.net>
References: <C7A75009.13F7A%rpenno@juniper.net>
In-Reply-To: <C7A75009.13F7A%rpenno@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 22 Feb 2010 13:09:10 -0000

On 2010-02-22 00:03, Reinaldo Penno wrote:
> I think this text is fine.
>
>
> On 2/21/10 6:45 PM, "Senthil Sivakumar (ssenthil)"<ssenthil@cisco.com>
> wrote:
>
>> [Senthil] Should be,
>> "Translator should make sure that the packets belonging to the same flow
>> leave the translator in the same order in which they arrived".

+1 with s/should/SHOULD/

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

From dthaler@microsoft.com  Mon Feb 22 11:33:37 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 0CE513A8339 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 11:33:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.568
X-Spam-Level: 
X-Spam-Status: No, score=-110.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, 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 Bj90vlWQEe7p for <behave@core3.amsl.com>; Mon, 22 Feb 2010 11:33:36 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id EF5B53A832F for <behave@ietf.org>; Mon, 22 Feb 2010 11:33:35 -0800 (PST)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 22 Feb 2010 11:35:35 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 22 Feb 2010 11:35:22 -0800
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.92]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 22 Feb 2010 11:35:25 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: "behave@ietf.org" <behave@ietf.org>
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
Thread-Index: Acqv/u/cXiNWhOEBT4eja+K338Bj8QD8o6lw
Date: Mon, 22 Feb 2010 19:35:21 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF65138B1C51@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <047501caaffe$f01f5660$cf4a150a@cisco.com>
In-Reply-To: <047501caaffe$f01f5660$cf4a150a@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: "draft-ietf-behave-dns64@tools.ietf.org" <draft-ietf-behave-dns64@tools.ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
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, 22 Feb 2010 19:33:37 -0000

Almost all of my comments from the 1st WGLC were addressed.
Below are typos in -06 I found, along with one or two that
still remain from my previous comments.

Section 5.1.5:
> authortiative server, by examining its own results.  If this new A RR
  ^^^^^^^^^^^^^
Fix spelling of authoritative

Section 5.2:
> 96.  If one or more Pref64::/n are configured in the DNS64
> through any means in the DNS64 (such as manually configured, or
                    ^^^^^^^^^^^^
Delete duplicate phrase

> Well-Know Prefix).  If no prefix is available, the algorithm
       ^^^^
s/Know/Known/

> MUST use the Well-Known prefix 64:FF9B::/96 defined in
                          ^
Capitalize for consistency with rest of doc.

Section 5.3.1:
I didn't see my question answered regarding this text:
> If the address prefix matches any Pref64::/n used
> in the site, either a NSP or the Well-Known Prefix (i.e. 64:
> FF9B::/96), then the DNS64 server MAY answer the query using locally-
> appropriate RDATA.                ^^^

Since MAY is defined as completely optional, what would the
alternative be if an implementation opted not to follow this
MAY?  Not answer the query?   I suspect a "MUST" was intended
instead of "MAY" but I can't tell for sure.

Section 5.3.3:
> If the DNS64 is in recursive resolver mode, then considerations
                               ^^^^^^^^

Section 2 defined "DNS64 in DNS recursive mode" (not
"recursive resolver mode".  Be consistent.

Section 5.5:
> 5.5.  DNSSEC processing: DNS64 in recursive server mode
                                              ^^^^^^
Same comment.

Section 7.1:
> A IPv6/IPv4 Translator connects the IPv6 network to the IPv4
              ^
Lower-case t for consistency with rest of doc.
(2 occurrences)

Section 8:
>   section 3, section 5.5, and section 6.2. .
                                             ^
Delete extra period

Appendix A:
> Appendix A.  Motivations and Implications of synthesizing AAAA RR when
>            real AAAA RR exists

OLD: "RR when real AAAA RR exists"
NEW: "RRs when real AAAA RRs exist"

> The motivation for synthesizing AAAA RRs when a real AAAA RRs exist
                                                ^
s/a//

> The implication of including synthetic AAAA RR when real AAAA RR
s/RR/RRs/ (twice)

> In "An IPv6 network to the IPv4 Internet" scenario , the host will
    ^                                               ^
Insert "the"						Delete space


-Dave

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dan Wing
> Sent: Wednesday, February 17, 2010 10:28 AM
> To: behave@ietf.org
> Cc: draft-ietf-behave-dns64@tools.ietf.org
> Subject: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
>=20
> ** We need at least 5 reviewers to tell us this document is ready
> ** for submission to IESG.  Please email behave-chairs@tools.ietf.org
> ** with a subject line containing the document name, and "ready
> ** to submit to IESG" or "not ready to submit to IESG" in the
> ** message body.  If not ready to submit, please propose new text.
>=20
> This email starts the 2nd WGLC for draft-ietf-behave-dns64-06, ending
> in one week (Wednesday, February 24).  For reference, the first
> WGLC was for draft-ietf-behave-v6v4-framework-05.
>=20
> Differences from -05 (first WGLC) and -06 (2nd WGLC),
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-behave-dns64-06.txt
>=20
> -d
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From ajs@shinkuro.com  Mon Feb 22 12:12:50 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 1EF4A28C397 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 12:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[AWL=0.602,  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 vAqUqkySErfc for <behave@core3.amsl.com>; Mon, 22 Feb 2010 12:12:48 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id E5AE028C154 for <behave@ietf.org>; Mon, 22 Feb 2010 12:12:47 -0800 (PST)
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 D226B1ECB4E8; Mon, 22 Feb 2010 20:14:46 +0000 (UTC)
Date: Mon, 22 Feb 2010 15:14:45 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: Dave Thaler <dthaler@microsoft.com>
Message-ID: <20100222201444.GS64954@shinkuro.com>
References: <047501caaffe$f01f5660$cf4a150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF65138B1C51@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF65138B1C51@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "behave@ietf.org" <behave@ietf.org>, "draft-ietf-behave-dns64@tools.ietf.org" <draft-ietf-behave-dns64@tools.ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
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, 22 Feb 2010 20:12:51 -0000

On Mon, Feb 22, 2010 at 07:35:21PM +0000, Dave Thaler wrote:
> Almost all of my comments from the 1st WGLC were addressed.
> Below are typos in -06 I found, along with one or two that
> still remain from my previous comments.

Thanks for these.  I didn't miss your previous comments (see my
response at
http://www.ietf.org/mail-archive/web/behave/current/msg08038.html -- I
never saw a response to those, so I assumed they were ok).

> Section 5.3.1:
> I didn't see my question answered regarding this text:
> > If the address prefix matches any Pref64::/n used
> > in the site, either a NSP or the Well-Known Prefix (i.e. 64:
> > FF9B::/96), then the DNS64 server MAY answer the query using locally-
> > appropriate RDATA.                ^^^
> 
> Since MAY is defined as completely optional, what would the
> alternative be if an implementation opted not to follow this
> MAY?  Not answer the query?   I suspect a "MUST" was intended
> instead of "MAY" but I can't tell for sure.

It's supposed to be MAY.  The paragraph starts "The first option" and
the next paragraph says "The other option".  The idea is that you can
do either, but you have to pick one.

We can't possibly make this MUST.  We can't get the DNS community to
agree that the reverse tree even needs to be maintained.  I tried at
one point to get a document through DNSOP on this topic, and it went
nowhere.

> Section 5.3.3:
> > If the DNS64 is in recursive resolver mode, then considerations
>                                ^^^^^^^^
> 
> Section 2 defined "DNS64 in DNS recursive mode" (not
> "recursive resolver mode".  Be consistent.

Section 2 doesn't have the definitions, strictly; section 4 does.  I
added this to section 4 between -05 and -06:

   DNS64 recursor:  A recursive resolver that provides the DNS64
      functionality as part of its operation.  This is the same thing as
      "DNS64 in recursive resolver mode".

But obviously, the word "resolver" is missing in Section 2.  I missed
that and the word "server" in section 5.  Thanks for catching.

More generally, did the additions to the definitions section help?

Thanks,

A

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

From brian.e.carpenter@gmail.com  Mon Feb 22 12:42:57 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 3363F28C1F8 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 12:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.693
X-Spam-Level: 
X-Spam-Status: No, score=-2.693 tagged_above=-999 required=5 tests=[AWL=-0.094, 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 1jSaSpbR0vbK for <behave@core3.amsl.com>; Mon, 22 Feb 2010 12:42:56 -0800 (PST)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id 7999B28C1DE for <behave@ietf.org>; Mon, 22 Feb 2010 12:42:56 -0800 (PST)
Received: by pzk33 with SMTP id 33so297179pzk.5 for <behave@ietf.org>; Mon, 22 Feb 2010 12:44:56 -0800 (PST)
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=xrBqmb4nq4k84c2u6k/e9JgK+eu1g+hL7jcJVsP+ce4=; b=Ai80HBuzAwZtJ2tp8kCaW0FwQVJsOItsHuJeQKoK/6tRfo4iESscE2ZXdf9DsVMjhE yh+ldwBIGOHNUxjl+7y7Yo2AQAXP1oq9u6O92UXrL/M6V56/hwUDW2LbD3nwz++gdBmj xh2ivkrDI9NXo8lfRHytljjH2x3XfpYG+DWwU=
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=iLFB7G2BuQJ/iHm2GDrC+aIIwlFCqxpbfbqVl84tBt191fpQOV/CiByBbgn1jGVA5h 7wvDYsSypEnr4OuAN6WNTI4Y0HgrV5OBrkezdEmm6YwiW1PzmAJ3QqvZO3sFIKlkrlXo 8vBZJN7xYeGEW0jPgX8DBM/+eJyPvUKErJLNc=
Received: by 10.142.3.33 with SMTP id 33mr1349754wfc.275.1266871495393; Mon, 22 Feb 2010 12:44:55 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 22sm283017pzk.13.2010.02.22.12.44.53 (version=SSLv3 cipher=RC4-MD5); Mon, 22 Feb 2010 12:44:54 -0800 (PST)
Message-ID: <4B82ECC3.6010809@gmail.com>
Date: Tue, 23 Feb 2010 09:44:51 +1300
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: Kentaro Ebisawa <ebisawa@sablenetworks.net>
References: <85B2F271FDF6B949B3672BA5A7BB62FB09721D67@xmb-sjc-236.amer.cisco.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721D68@xmb-sjc-236.amer.cisco.com> <20100222124153.58E7.B01659E3@sablenetworks.net>
In-Reply-To: <20100222124153.58E7.B01659E3@sablenetworks.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 22 Feb 2010 20:42:57 -0000

On 2010-02-22 16:52, Kentaro Ebisawa wrote:
> Hi,
> 
>> [Senthil] Should be, 
>> "Translator should make sure that the packets belonging to the same flow
>> leave the translator in the same order in which they arrived".
>>
>> But this will have some issues with translators doing ALG functionality,
>> but that would be a separate discussion.
> 
> I think exception to this is when handling fragmented packets.
> In compliance to Section 3.4. Page 19, implementation should have
> freedom to queue and sort fragments in order or translate packets
> as they arrive.

That's why it can only be a SHOULD and not a MUST.

I'm fine with Senthil's version; obviously one stateless translator
cannot guess what is happening in another one, or what has happened
in the past.

    Brian

From rpenno@juniper.net  Mon Feb 22 15:01:21 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 25BE828C430 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 15:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.141
X-Spam-Level: 
X-Spam-Status: No, score=-6.141 tagged_above=-999 required=5 tests=[AWL=0.458,  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 JrRxtbfjZ4LQ for <behave@core3.amsl.com>; Mon, 22 Feb 2010 15:01:20 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by core3.amsl.com (Postfix) with ESMTP id 63B303A7B73 for <behave@ietf.org>; Mon, 22 Feb 2010 15:01:19 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKS4MNNzDBjjEDE8VkdY8hi3nSnU0wNj4f@postini.com; Mon, 22 Feb 2010 15:03:20 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.1.393.1; Mon, 22 Feb 2010 15:01:16 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Mon, 22 Feb 2010 18:01:15 -0500
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, "behave@ietf.org" <behave@ietf.org>
Date: Mon, 22 Feb 2010 18:01:13 -0500
Thread-Topic: Comment on draft-ietf-behave-v6v4-framework-06
Thread-Index: AcqsGQIgMZ0KBN1JQLaTpL1EvghGQgH+evz6
Message-ID: <C7A84CB9.14165%rpenno@juniper.net>
In-Reply-To: <13a701caac19$025e3a10$c4f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.3.0.091002
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [BEHAVE] Comment on draft-ietf-behave-v6v4-framework-06
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, 22 Feb 2010 23:01:21 -0000

Small comment:

"   o  Users of the new architecture that don't support the old protocol,
      and those users are unable to use the services of the underlying
      infrastructure - it is just bandwidth, and"

This sentence reads strange. Who are 'those users'?

Thanks,


On 2/12/10 11:24 AM, "Dan Wing" <dwing@cisco.com> wrote:

> As you just saw my 4 posts, we started the 2nd WGLC for 4 (of our 6)
> translation documents.  The 2nd WGLC is only a week long.  As stated, we =
need
> 5 reviewers to say "looks good" before submitting to IESG.
>=20
> 2nd WGLC finishes Feb-19:
>   draft-ietf-behave-v6v4-framework-06
>   draft-ietf-behave-v6v4-xlate-09
>   draft-ietf-behave-v6v4-xlate-stateful-08=20
>   draft-ietf-behave-address-format-04=20
>=20
> waiting for new versions from authors:
>   draft-ietf-behave-dns64-06, awaiting version -06 from authors
>   draft-ietf-behave-ftp64-01, awaiting version -01 from author
>=20
>=20
> which is also shown at http://trac.tools.ietf.org/wg/behave/trac/wiki
>=20
> -d
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From ietfdbh@comcast.net  Mon Feb 22 16:28:11 2010
Return-Path: <ietfdbh@comcast.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 040CF28C46F for <behave@core3.amsl.com>; Mon, 22 Feb 2010 16:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level: 
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105,  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 Q4iuCSKhBRoE for <behave@core3.amsl.com>; Mon, 22 Feb 2010 16:28:10 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id 1A0C328C488 for <behave@ietf.org>; Mon, 22 Feb 2010 16:28:10 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta12.westchester.pa.mail.comcast.net with comcast id kzfg1d00627AodY5CCWBUi; Tue, 23 Feb 2010 00:30:11 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta19.westchester.pa.mail.comcast.net with comcast id lCY41d005284sdk3fCY46Q; Tue, 23 Feb 2010 00:32:04 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Simon Perreault'" <simon.perreault@viagenie.ca>, <behave@ietf.org>
References: <4B7EA135.4060703@viagenie.ca>	<4B7EAC75.4020002@it.uc3m.es>	<4B7EB1AB.4020103@viagenie.ca>	<4B7EBB3D.70205@it.uc3m.es><4B7EBE84.8040301@viagenie.ca>	<4B7EFC98.7050602@gmail.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721A90@xmb-sjc-236.amer.cisco.com>	<4B7F4B3F.9050607@cernet.edu.cn>	<4B7F5D63.1070409@gmail.com><4B7F7582.8000700@cernet.edu.cn> <4B7FF5C9.1080208@viagenie.ca>
Date: Mon, 22 Feb 2010 19:30:09 -0500
Message-ID: <13be01cab41f$5b60d920$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4B7FF5C9.1080208@viagenie.ca>
Thread-Index: AcqyO4uynzGyEHOfSVGSBiUtad1PxwB44/9w
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 23 Feb 2010 00:28:11 -0000

 
> > Translators SHOULD be designed to avoid packet reordering as much
> > as possible.

doesn't "Translators SHOULD be designed to avoid packet reordering"
suffice?
or even "Translators SHOULD avoid packet reordering"?

dbh


From dthaler@microsoft.com  Mon Feb 22 18:02:56 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 4E2EB28C4E8 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 18:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.57
X-Spam-Level: 
X-Spam-Status: No, score=-110.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, 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 AhKqwbgpDfIB for <behave@core3.amsl.com>; Mon, 22 Feb 2010 18:02:55 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 9DB7228C4DB for <behave@ietf.org>; Mon, 22 Feb 2010 18:02:55 -0800 (PST)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 22 Feb 2010 18:04:56 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.0.639.21; Mon, 22 Feb 2010 18:04:51 -0800
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.92]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Mon, 22 Feb 2010 18:04:50 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Andrew Sullivan <ajs@shinkuro.com>
Thread-Topic: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
Thread-Index: Acqv/u/cXiNWhOEBT4eja+K338Bj8QD8o6lwABNPGYAABIxYoA==
Date: Tue, 23 Feb 2010 02:04:49 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF65138B2A5D@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <047501caaffe$f01f5660$cf4a150a@cisco.com> <9B57C850BB53634CACEC56EF4853FF65138B1C51@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <20100222201444.GS64954@shinkuro.com>
In-Reply-To: <20100222201444.GS64954@shinkuro.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>, "draft-ietf-behave-dns64@tools.ietf.org" <draft-ietf-behave-dns64@tools.ietf.org>
Subject: Re: [BEHAVE] 2nd WGLC, draft-ietf-behave-dns64-06
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, 23 Feb 2010 02:02:56 -0000

[...]
> More generally, did the additions to the definitions section help?

Absolutely.

Thanks,
-Dave

From xing@cernet.edu.cn  Mon Feb 22 22:27:54 2010
Return-Path: <xing@cernet.edu.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 5A79A3A8411 for <behave@core3.amsl.com>; Mon, 22 Feb 2010 22:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.212
X-Spam-Level: 
X-Spam-Status: No, score=0.212 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 YsBZYTXu986l for <behave@core3.amsl.com>; Mon, 22 Feb 2010 22:27:44 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 54D8028C214 for <behave@ietf.org>; Mon, 22 Feb 2010 22:27:42 -0800 (PST)
Received: from [192.168.1.101]([112.67.10.153]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b83eeae; Tue, 23 Feb 2010 14:29:40 +0800
Message-ID: <4B8375D9.6000607@cernet.edu.cn>
Date: Tue, 23 Feb 2010 14:29:45 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <85B2F271FDF6B949B3672BA5A7BB62FB09721D67@xmb-sjc-236.amer.cisco.com>	<85B2F271FDF6B949B3672BA5A7BB62FB09721D68@xmb-sjc-236.amer.cisco.com>	<20100222124153.58E7.B01659E3@sablenetworks.net> <4B82ECC3.6010809@gmail.com>
In-Reply-To: <4B82ECC3.6010809@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: AQGRojXB
Cc: Kentaro Ebisawa <ebisawa@sablenetworks.net>, behave@ietf.org
Subject: Re: [BEHAVE] NAT64: Out of order session handling
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, 23 Feb 2010 06:27:54 -0000

Brian E Carpenter 写道:
> On 2010-02-22 16:52, Kentaro Ebisawa wrote:
>   
>> Hi,
>>
>>     
>>> [Senthil] Should be, 
>>> "Translator should make sure that the packets belonging to the same flow
>>> leave the translator in the same order in which they arrived".
>>>
>>> But this will have some issues with translators doing ALG functionality,
>>> but that would be a separate discussion.
>>>       
>> I think exception to this is when handling fragmented packets.
>> In compliance to Section 3.4. Page 19, implementation should have
>> freedom to queue and sort fragments in order or translate packets
>> as they arrive.
>>     
>
> That's why it can only be a SHOULD and not a MUST.
>
> I'm fine with Senthil's version; obviously one stateless translator
> cannot guess what is happening in another one, or what has happened
> in the past.
>   

Thanks. xing


>     Brian
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>
>   


From xing@cernet.edu.cn  Mon Feb 22 23:25:45 2010
Return-Path: <xing@cernet.edu.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 3645728C24C for <behave@core3.amsl.com>; Mon, 22 Feb 2010 23:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.205
X-Spam-Level: 
X-Spam-Status: No, score=0.205 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
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 AADHRqchA6ER for <behave@core3.amsl.com>; Mon, 22 Feb 2010 23:25:44 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id C7EEA28C53E for <behave@ietf.org>; Mon, 22 Feb 2010 23:25:43 -0800 (PST)
Received: from [192.168.1.101]([112.67.10.153]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b83fc49; Tue, 23 Feb 2010 15:27:43 +0800
Message-ID: <4B838370.8010601@cernet.edu.cn>
Date: Tue, 23 Feb 2010 15:27:44 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Reinaldo Penno <rpenno@juniper.net>
References: <C7A84CB9.14165%rpenno@juniper.net>
In-Reply-To: <C7A84CB9.14165%rpenno@juniper.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: ADRLpjXB
Cc: "behave@ietf.org" <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Comment on draft-ietf-behave-v6v4-framework-06
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, 23 Feb 2010 07:25:45 -0000

Reinaldo Penno 写道:
> Small comment:
>
> "   o  Users of the new architecture that don't support the old protocol,
>       and those users are unable to use the services of the underlying
>       infrastructure - it is just bandwidth, and"
>   

Thanks.

   o  Users of the new architecture are unable to use the services of
      the underlying infrastructure - it is just bandwidth, and


Regards,

xing



> This sentence reads strange. Who are 'those users'?
>
> Thanks,
>
>
> On 2/12/10 11:24 AM, "Dan Wing" <dwing@cisco.com> wrote:
>
>   
>> As you just saw my 4 posts, we started the 2nd WGLC for 4 (of our 6)
>> translation documents.  The 2nd WGLC is only a week long.  As stated, we need
>> 5 reviewers to say "looks good" before submitting to IESG.
>>
>> 2nd WGLC finishes Feb-19:
>>   draft-ietf-behave-v6v4-framework-06
>>   draft-ietf-behave-v6v4-xlate-09
>>   draft-ietf-behave-v6v4-xlate-stateful-08 
>>   draft-ietf-behave-address-format-04 
>>
>> waiting for new versions from authors:
>>   draft-ietf-behave-dns64-06, awaiting version -06 from authors
>>   draft-ietf-behave-ftp64-01, awaiting version -01 from author
>>
>>
>> which is also shown at http://trac.tools.ietf.org/wg/behave/trac/wiki
>>
>> -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 zehn.cao@gmail.com  Tue Feb 23 02:52:13 2010
Return-Path: <zehn.cao@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 1D99B28C29A for <behave@core3.amsl.com>; Tue, 23 Feb 2010 02:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 x1jOiJtNRGdg for <behave@core3.amsl.com>; Tue, 23 Feb 2010 02:52:12 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 32CF128C298 for <behave@ietf.org>; Tue, 23 Feb 2010 02:52:12 -0800 (PST)
Received: by gwb10 with SMTP id 10so946738gwb.31 for <behave@ietf.org>; Tue, 23 Feb 2010 02:54:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=c7p0Aimfy27gczz7P7nDUMZY4Qmub+So23RYDeTwBw8=; b=YrwM3uQBI8tZcatNNU0CnddqSdQZqkXgrmtt0hYn05+0vq5aMRihvdXuugn9bFEt1Q zOkbwFLYwUstRGc9dWQHPesbi+IbQ9+3ibIzuitzYN+S/jLSuqx528sZvHMj5HxXMmlI yBo9kj9jMK4KvgmtZ0UAyPTx10CwqHHE4+dAI=
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 :cc:content-type:content-transfer-encoding; b=wZPp2Nld/CM6oTqHp1e7R8eGjrdTMG5UNh7O+rLNNtVMd+t/+rBCTZD6nJ4UKQqwFq SiSHP5bWF0Dp3ER8VcfG3BjXjiRGIZZPexJUcC0hTuHmYP7HhWtE2Y7y1DYImQxhZ/nU jxqRco3zLSG1JiTgj57/8B1CsRD3uzIAS9uww=
MIME-Version: 1.0
Received: by 10.101.178.18 with SMTP id f18mr9109484anp.51.1266922450849; Tue,  23 Feb 2010 02:54:10 -0800 (PST)
In-Reply-To: <027b01cab38b$81b0bcb0$bea66b80@cisco.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com> <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com> <027b01cab38b$81b0bcb0$bea66b80@cisco.com>
Date: Tue, 23 Feb 2010 18:54:10 +0800
Message-ID: <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Hui Deng <denghui02@gmail.com>, Andrew Sullivan <ajs@shinkuro.com>, Cameron Byrne <cb.list6@gmail.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 10:52:13 -0000

On Mon, Feb 22, 2010 at 2:51 PM, Dan Wing <dwing@cisco.com> wrote:
>
>
>> -----Original Message-----
>> From: Hui Deng [mailto:denghui02@gmail.com]
>> Sent: Sunday, February 21, 2010 6:21 PM
>> To: Dan Wing
>> Cc: Cameron Byrne; Andrew Sullivan; behave@ietf.org
>> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>>
>> Dan,
>>
>> I guess that I used two No in that sentence, that is not correct.
>>
>> what I mean is that I would like to support NAT64 is prior to NAT44,
>> secondly, if NAT64 could be used in dual stack network,
>> that's also good.
>
> Sorry, I still do not understand.
>
> Earlier in this email thread, Andrew, Cameron, and I pointed out that
> draft-cao-behave-dsdns64-00 does not fully describe its solution. =A0I lo=
ok
> forward to a more complete description so I can understand the proposal.
>
> -d

In draft-wing-behave-dns64-config-01, section 3.4, there introduces a
solution based on host modification to avoid traversal of NAT64.  If
the DNS64 cannot support type "A" request, this feature cannot be
supported?  Actually my draft-cao-behave-dsdns64-00 would like to
clarify this issue in a simple and tentative way.

Thanks,
Cao Zhen

From dwing@cisco.com  Tue Feb 23 07:30:50 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 9F9CE3A77D0 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 07:30:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level: 
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 RBWBoQsmPagL for <behave@core3.amsl.com>; Tue, 23 Feb 2010 07:30:49 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id E3EB43A7B31 for <behave@ietf.org>; Tue, 23 Feb 2010 07:30:47 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMHAPyDg0urR7Hu/2dsb2JhbACHTIESki1zpTWYXoRsBIMV
X-IronPort-AV: E=Sophos;i="4.49,526,1262563200"; d="scan'208";a="88252144"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by rtp-iport-2.cisco.com with ESMTP; 23 Feb 2010 15:32:49 +0000
Received: from dwingwxp01 ([10.32.240.197]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o1NFWnjd018346; Tue, 23 Feb 2010 15:32:49 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Zhen Cao'" <zehn.cao@gmail.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com> <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com> <027b01cab38b$81b0bcb0$bea66b80@cisco.com> <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com>
Date: Tue, 23 Feb 2010 07:32:49 -0800
Message-ID: <08d401cab49d$74b2f1f0$bea66b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acq0domHu6ZTTpeVRjWq++ZHtYj4mgAJa2NA
In-Reply-To: <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: 'Hui Deng' <denghui02@gmail.com>, 'Andrew Sullivan' <ajs@shinkuro.com>, 'Cameron Byrne' <cb.list6@gmail.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 15:30:50 -0000

=20

> -----Original Message-----
> From: Zhen Cao [mailto:zehn.cao@gmail.com]=20
> Sent: Tuesday, February 23, 2010 2:54 AM
> To: Dan Wing
> Cc: Hui Deng; Andrew Sullivan; Cameron Byrne; behave@ietf.org
> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>=20
> On Mon, Feb 22, 2010 at 2:51 PM, Dan Wing <dwing@cisco.com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Hui Deng [mailto:denghui02@gmail.com]
> >> Sent: Sunday, February 21, 2010 6:21 PM
> >> To: Dan Wing
> >> Cc: Cameron Byrne; Andrew Sullivan; behave@ietf.org
> >> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
> >>
> >> Dan,
> >>
> >> I guess that I used two No in that sentence, that is not correct.
> >>
> >> what I mean is that I would like to support NAT64 is prior=20
> to NAT44,
> >> secondly, if NAT64 could be used in dual stack network,
> >> that's also good.
> >
> > Sorry, I still do not understand.
> >
> > Earlier in this email thread, Andrew, Cameron, and I=20
> pointed out that
> > draft-cao-behave-dsdns64-00 does not fully describe its=20
> solution. =A0I look
> > forward to a more complete description so I can understand=20
> the proposal.
> >
> > -d
>=20
> In draft-wing-behave-dns64-config-01, section 3.4, there introduces a
> solution based on host modification to avoid traversal of NAT64.=20

Yes, modification of the dual-stack host's RFC3484 table, so that
the IPv6/IPv4 translator is preferred least.  Example is in
http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.4.=
3

> If the DNS64 cannot support type "A" request, this feature cannot be
> supported?=20

Correct, the DNS64 needs to handle A requests. =20

But draft-ietf-behave-dns64 does not change the DNS64's behavior of A =
requests
or A responses, as stated in
http://tools.ietf.org/html/draft-ietf-behave-dns64-06#section-5.3.3 =
where it
reads:

  "5.3.3. Other records

   If the DNS64 is in recursive resolver mode, then considerations
   outlined in [I-D.ietf-dnsop-default-local-zones] may be relevant.

   All other RRs MUST be returned unchanged."

> Actually my draft-cao-behave-dsdns64-00 would like to
> clarify this issue in a simple and tentative way.

Looking forward to it.

-d


From edward.jankiewicz@sri.com  Tue Feb 23 07:30:56 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 88EB428C296; Tue, 23 Feb 2010 07:30:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level: 
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 EXu2Os0lupd7; Tue, 23 Feb 2010 07:30:55 -0800 (PST)
Received: from mail1.sri.com (mail1.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id 9B9B928C1F9; Tue, 23 Feb 2010 07:30:55 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [192.168.2.9] ([unknown] [72.68.71.162]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0KYA00MULWIXHAB0@mail.sri.com>; Tue, 23 Feb 2010 07:32:58 -0800 (PST)
Message-id: <4B83F531.90002@sri.com>
Date: Tue, 23 Feb 2010 10:33:05 -0500
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
To: IPv6 Operations <v6ops@ops.ietf.org>, ipsec@ietf.org, Behave WG <behave@ietf.org>, "nav6tf@ipv6forum.com" <nav6tf@ipv6forum.com>
Subject: [BEHAVE] FYI: NIST Publication "Guidelines for the secure deployment of IPv6"
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, 23 Feb 2010 15:30:56 -0000

I had nothing to do with this doc, and have not fully reviewed it yet, 
but thought it would be of interest to folks on these lists.

Please do not send your comments to me or post on these lists, but 
follow the instructions at the link to comment directly to the authors.  
I am sure NIST would appreciate any insight from additional folks who 
have not already contributed to discussion on the draft publication.

http://csrc.nist.gov/publications/PubsDrafts.html#SP-800-119

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


From zehn.cao@gmail.com  Tue Feb 23 07:56:54 2010
Return-Path: <zehn.cao@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 A486528C15C for <behave@core3.amsl.com>; Tue, 23 Feb 2010 07:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Bwh7v5rYHwvr for <behave@core3.amsl.com>; Tue, 23 Feb 2010 07:56:53 -0800 (PST)
Received: from mail-yx0-f188.google.com (mail-yx0-f188.google.com [209.85.210.188]) by core3.amsl.com (Postfix) with ESMTP id 9BBD828C1EC for <behave@ietf.org>; Tue, 23 Feb 2010 07:56:53 -0800 (PST)
Received: by yxe26 with SMTP id 26so561210yxe.29 for <behave@ietf.org>; Tue, 23 Feb 2010 07:58:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fce8vk9XS6yncX+1je5sxcwfw1Gf/p8/aF6v7+uBq3s=; b=ARvyI5/zqTD9DcDuryKIbeUxecstNvqP84sNLTHLn2NPSbQ4DIXIoyEv5W4hPimUIK WT5dkS/vs6p3LLXKYoXNaMsaJwKQAplgUQmZzD/sVSxdTlnmBqCyHHuISje1N2aFqdi8 Uye6Est+48bvD8DucwReyuvwwiQGGahEa75YE=
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 :cc:content-type:content-transfer-encoding; b=iTg1vdKx8ozxudFiRQI5uEwNn5z2zQY3X2KJckHdVdpa+uWFnbyd9LL7vBnMZGIXHn rHA74csXJ3sMp2HsJqOsQBAMUI1YBA+SkNFNmkZ0UKzhOJjhRlKE83qrhVIGCYJphrsF xWdH2col3hU5CUMKVAhv/7KvbXPtG2o+vSX0M=
MIME-Version: 1.0
Received: by 10.100.56.25 with SMTP id e25mr4532699ana.84.1266940733240; Tue,  23 Feb 2010 07:58:53 -0800 (PST)
In-Reply-To: <08d401cab49d$74b2f1f0$bea66b80@cisco.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com> <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com> <027b01cab38b$81b0bcb0$bea66b80@cisco.com> <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com> <08d401cab49d$74b2f1f0$bea66b80@cisco.com>
Date: Tue, 23 Feb 2010 23:58:53 +0800
Message-ID: <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Hui Deng <denghui02@gmail.com>, Andrew Sullivan <ajs@shinkuro.com>, Cameron Byrne <cb.list6@gmail.com>, behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 15:56:54 -0000

I thought normally DNS64 did not treat "A" query request. I think most
implementations do not implement that.

Thanks,
Zhen
On Tue, Feb 23, 2010 at 11:32 PM, Dan Wing <dwing@cisco.com> wrote:
>
>
>> -----Original Message-----
>> From: Zhen Cao [mailto:zehn.cao@gmail.com]
>> Sent: Tuesday, February 23, 2010 2:54 AM
>> To: Dan Wing
>> Cc: Hui Deng; Andrew Sullivan; Cameron Byrne; behave@ietf.org
>> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>>
>> On Mon, Feb 22, 2010 at 2:51 PM, Dan Wing <dwing@cisco.com> wrote:
>> >
>> >
>> >> -----Original Message-----
>> >> From: Hui Deng [mailto:denghui02@gmail.com]
>> >> Sent: Sunday, February 21, 2010 6:21 PM
>> >> To: Dan Wing
>> >> Cc: Cameron Byrne; Andrew Sullivan; behave@ietf.org
>> >> Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
>> >>
>> >> Dan,
>> >>
>> >> I guess that I used two No in that sentence, that is not correct.
>> >>
>> >> what I mean is that I would like to support NAT64 is prior
>> to NAT44,
>> >> secondly, if NAT64 could be used in dual stack network,
>> >> that's also good.
>> >
>> > Sorry, I still do not understand.
>> >
>> > Earlier in this email thread, Andrew, Cameron, and I
>> pointed out that
>> > draft-cao-behave-dsdns64-00 does not fully describe its
>> solution. =A0I look
>> > forward to a more complete description so I can understand
>> the proposal.
>> >
>> > -d
>>
>> In draft-wing-behave-dns64-config-01, section 3.4, there introduces a
>> solution based on host modification to avoid traversal of NAT64.
>
> Yes, modification of the dual-stack host's RFC3484 table, so that
> the IPv6/IPv4 translator is preferred least. =A0Example is in
> http://tools.ietf.org/html/draft-wing-behave-dns64-config-02#section-3.4.=
3
>
>> If the DNS64 cannot support type "A" request, this feature cannot be
>> supported?
>
> Correct, the DNS64 needs to handle A requests.
>
> But draft-ietf-behave-dns64 does not change the DNS64's behavior of A req=
uests
> or A responses, as stated in
> http://tools.ietf.org/html/draft-ietf-behave-dns64-06#section-5.3.3 where=
 it
> reads:
>
> =A0"5.3.3. Other records
>
> =A0 If the DNS64 is in recursive resolver mode, then considerations
> =A0 outlined in [I-D.ietf-dnsop-default-local-zones] may be relevant.
>
> =A0 All other RRs MUST be returned unchanged."
>
>> Actually my draft-cao-behave-dsdns64-00 would like to
>> clarify this issue in a simple and tentative way.
>
> Looking forward to it.
>
> -d
>
>

From ajs@shinkuro.com  Tue Feb 23 08:01:53 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 D701F3A8496 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level: 
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[AWL=0.581,  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 ZCRFK67PzQpJ for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:01:51 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 6F3173A849B for <behave@ietf.org>; Tue, 23 Feb 2010 08:01:51 -0800 (PST)
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 DEF821ECB4E8 for <behave@ietf.org>; Tue, 23 Feb 2010 16:03:50 +0000 (UTC)
Date: Tue, 23 Feb 2010 11:03:49 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20100223160348.GE55606@shinkuro.com>
References: <20100212195141.GR14996@shinkuro.com> <13e001caac21$d8b577b0$c4f0200a@cisco.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com> <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com> <027b01cab38b$81b0bcb0$bea66b80@cisco.com> <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com> <08d401cab49d$74b2f1f0$bea66b80@cisco.com> <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 16:01:54 -0000

On Tue, Feb 23, 2010 at 11:58:53PM +0800, Zhen Cao wrote:
> I thought normally DNS64 did not treat "A" query request. I think most
> implementations do not implement that.

Where did you get that idea?  If you query a DNS64 for an A record,
you'll get it back.

What DNS64 does is deal with A records specially if and only if it
tried to get a AAAA and didn't.  That's unrelated to what it does if
it tries to get A for other reasons.

A

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

From simon.perreault@viagenie.ca  Tue Feb 23 08:10:23 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 39F9428C300 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 hO-KW1yuwgt5 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:10:22 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id 28B7A28C2EF for <behave@ietf.org>; Tue, 23 Feb 2010 08:10:22 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 36C8721BDC for <behave@ietf.org>; Tue, 23 Feb 2010 11:12:24 -0500 (EST)
Message-ID: <4B83FE67.5030700@viagenie.ca>
Date: Tue, 23 Feb 2010 11:12:23 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <20100212195141.GR14996@shinkuro.com>	<13e001caac21$d8b577b0$c4f0200a@cisco.com>	<bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com>	<1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com>	<01eb01cab31b$dd9922d0$bea66b80@cisco.com>	<1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com>	<027b01cab38b$81b0bcb0$bea66b80@cisco.com>	<c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com>	<08d401cab49d$74b2f1f0$bea66b80@cisco.com> <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com>
In-Reply-To: <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 16:10:23 -0000

On 2010-02-23 10:58, Zhen Cao wrote:
> I thought normally DNS64 did not treat "A" query request. I think most
> implementations do not implement that.

Well, our three implementations do.

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

From zehn.cao@gmail.com  Tue Feb 23 08:15:13 2010
Return-Path: <zehn.cao@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 D399C28C307 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 JSK1VIs1XsaT for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:15:12 -0800 (PST)
Received: from mail-yx0-f188.google.com (mail-yx0-f188.google.com [209.85.210.188]) by core3.amsl.com (Postfix) with ESMTP id B389428C309 for <behave@ietf.org>; Tue, 23 Feb 2010 08:15:10 -0800 (PST)
Received: by yxe26 with SMTP id 26so573591yxe.29 for <behave@ietf.org>; Tue, 23 Feb 2010 08:17:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1s4Do4lUWTENNRMZ5e8U920Qkmko6Xs75IjmZmRgtf0=; b=NYkYCIH15REGT33haFT+3FMa4e7D8m37FpayK1zm19QAlpJZn1XTgUAlPPHl5CtjZ0 dK/8r0+nkKIICtq5/WOl6d/d3io5jwMZijFjWbklW/g58vq6vTwinPoo5uQoqC7S1Im1 cEjnr1z5oQeWfYepsnOvAylXe8cBE+DDTR4DA=
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 :cc:content-type:content-transfer-encoding; b=MooZgXMnWR/2Ws7QVwp7turm6h7Lz6WxQrGIcfeBX+MRqjJCztSdH87lMv308norcp 3tI6rQMpQwlMoE9owEgR8acb/QY8EJDUrYxMiE4I75nC4Kf2hIwZKYHr/wtK4JLS/AAx 3D+NWRVOPkMTcApfbyH2GuLn8qUNjm4dYjQWQ=
MIME-Version: 1.0
Received: by 10.101.130.13 with SMTP id h13mr4136720ann.47.1266941826369; Tue,  23 Feb 2010 08:17:06 -0800 (PST)
In-Reply-To: <4B83FE67.5030700@viagenie.ca>
References: <20100212195141.GR14996@shinkuro.com> <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com> <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com> <01eb01cab31b$dd9922d0$bea66b80@cisco.com> <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com> <027b01cab38b$81b0bcb0$bea66b80@cisco.com> <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com> <08d401cab49d$74b2f1f0$bea66b80@cisco.com> <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com> <4B83FE67.5030700@viagenie.ca>
Date: Wed, 24 Feb 2010 00:17:06 +0800
Message-ID: <c549bac51002230817k281797d0o6734db85467f060c@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, Andrew Sullivan <ajs@shinkuro.com>, Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 16:15:14 -0000

Hi, Simon,

I might misunderstand a previous discussion with you. You were
actually saying that DNS64 does not specify the behavior of A query
request.

Thanks,
Zhen
On Wed, Feb 24, 2010 at 12:12 AM, Simon Perreault
<simon.perreault@viagenie.ca> wrote:
> On 2010-02-23 10:58, Zhen Cao wrote:
>>
>> I thought normally DNS64 did not treat "A" query request. I think most
>> implementations do not implement that.
>
> Well, our three implementations do.
>
> Simon
> --
> NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
> STUN/TURN server =A0 =A0 =A0 =A0--> http://numb.viagenie.ca
> vCard 4.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --> http://www.vcarddav.org
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From simon.perreault@viagenie.ca  Tue Feb 23 08:27:03 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 BF20728C1D8 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:27:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 MmzC5Mk13ly6 for <behave@core3.amsl.com>; Tue, 23 Feb 2010 08:27:02 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by core3.amsl.com (Postfix) with ESMTP id E5A583A7F61 for <behave@ietf.org>; Tue, 23 Feb 2010 08:27:01 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E221921BA2; Tue, 23 Feb 2010 11:29:03 -0500 (EST)
Message-ID: <4B84024F.1080700@viagenie.ca>
Date: Tue, 23 Feb 2010 11:29:03 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
MIME-Version: 1.0
To: Zhen Cao <zehn.cao@gmail.com>
References: <20100212195141.GR14996@shinkuro.com>	 <bcff0fba1002121307k7fdd50ffg5b566cbf4926968@mail.gmail.com>	 <1d38a3351002170009s61721230p17fe4f15c160364a@mail.gmail.com>	 <01eb01cab31b$dd9922d0$bea66b80@cisco.com>	 <1d38a3351002211821u7d3e6351x7eb20dbb167fc164@mail.gmail.com>	 <027b01cab38b$81b0bcb0$bea66b80@cisco.com>	 <c549bac51002230254p1979affcv5b42e97c7dcabcf5@mail.gmail.com>	 <08d401cab49d$74b2f1f0$bea66b80@cisco.com>	 <c549bac51002230758g3d0c273ao2315cde00fe58c67@mail.gmail.com>	 <4B83FE67.5030700@viagenie.ca> <c549bac51002230817k281797d0o6734db85467f060c@mail.gmail.com>
In-Reply-To: <c549bac51002230817k281797d0o6734db85467f060c@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Andrew Sullivan <ajs@shinkuro.com>, behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] draft-cao-behave-dsdns64-00
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, 23 Feb 2010 16:27:04 -0000

On 2010-02-23 11:17, Zhen Cao wrote:
> I might misunderstand a previous discussion with you. You were
> actually saying that DNS64 does not specify the behavior of A query
> request.

Yes, that's what I said. I made a mistake, but I also think you 
misunderstood.

My mistake: In mathematical terms, I thought that the DNS64 function 
only had AAAA queries as its domain. It turns out that there is a 
sentence in the spec that extends the domain to include A queries, and 
defines the DNS64 function on them to be identical to the usual DNS 
function.

But it doesn't matter. I my mind, DNS64 doesn't touch A queries as they 
are handled by normal DNS. That's probably influenced by the 
implementations that I worked on, since that's how the code does it. 
Only AAAA queries will actually reach the DNS64 code. So our DNS64 code 
doesn't know how to handle A queries. It's not defined.

I did not imply that any of this needed to be specified or that 
implementations needed to do anything differently.

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

From xuxh@huawei.com  Tue Feb 23 18:28:19 2010
Return-Path: <xuxh@huawei.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 407C03A7F0A for <behave@core3.amsl.com>; Tue, 23 Feb 2010 18:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.909
X-Spam-Level: *
X-Spam-Status: No, score=1.909 tagged_above=-999 required=5 tests=[AWL=-0.385,  BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
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 lp1kyybmmF4R for <behave@core3.amsl.com>; Tue, 23 Feb 2010 18:28:17 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 777733A829D for <behave@ietf.org>; Tue, 23 Feb 2010 18:28:16 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYB000EKQYAVV@szxga03-in.huawei.com> for behave@ietf.org; Wed, 24 Feb 2010 10:30:11 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYB00DKSQYAKT@szxga03-in.huawei.com> for behave@ietf.org; Wed, 24 Feb 2010 10:30:10 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.13.9]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYB000H6QYAZ0@szxml04-in.huawei.com> for behave@ietf.org; Wed, 24 Feb 2010 10:30:10 +0800 (CST)
Date: Wed, 24 Feb 2010 10:30:10 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: behave@ietf.org
Message-id: <006f01cab4f9$49b31550$090d6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: Acq0bGqEp64FsOv/Qcm/aCQReEI83AAg/Frw
Subject: [BEHAVE] fwd: New Version Notification for draft-xu-behave-nat-state-sync-01
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, 24 Feb 2010 02:28:19 -0000

Hi all,

The updated version is posted now.=20

The difference between 00 version and 01 version is:
http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-xu-behave-=
nat-sta
te-sync-01.txt

Any comment is welcomed.=20

Best wishes,
Xiaohu

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]=20
=B7=A2=CB=CD=CA=B1=BC=E4: 2010=C4=EA2=D4=C223=C8=D5 17:39
=CA=D5=BC=FE=C8=CB: xuxh@huawei.com
=B3=AD=CB=CD: Chengd@huawei.com
=D6=F7=CC=E2: New Version Notification for =
draft-xu-behave-nat-state-sync-01


A new version of I-D, draft-xu-behave-nat-state-sync-01.txt has been
successfuly submitted by Xiaohu Xu and posted to the IETF repository.

Filename:	 draft-xu-behave-nat-state-sync
Revision:	 01
Title:		 NAT State Synchronization Using SCSP
Creation_date:	 2010-02-23
WG ID:		 Independent Submission
Number_of_pages: 11

Abstract:
To support NAT redundancy in hot standby mode [NAT-STANDBY] among a=20
group of NAT devices, the dynamic NAT entries created at the primary=20
NAT device should be synchronized consistently to the backup NAT=20
device.  This document describes a method of using the Server Cache=20
Synchronization Protocol (SCSP) for NAT state synchronization and=20
specifies the corresponding NAT specific components for this method.
=20



The IETF Secretariat.



From jsklein@gmail.com  Tue Feb 23 13:59:43 2010
Return-Path: <jsklein@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 7E0E928C37A; Tue, 23 Feb 2010 13:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=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 i7ryg18XKq+Z; Tue, 23 Feb 2010 13:59:42 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 66A4F28C382; Tue, 23 Feb 2010 13:59:42 -0800 (PST)
Received: by pwi3 with SMTP id 3so4374439pwi.31 for <multiple recipients>; Tue, 23 Feb 2010 14:01:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MLAEi2RFo3ulhnxCSuz99C6rmayoAqWx6bAb/VZb4fw=; b=c3ZmWTSpi9XjOUvr2uYfuBw9Irz5XfO0PvnwZOQLr1Uh9qU2LE0YdlT3TzaEcoCV3G 36P7JFSqiMZ2Z4lJT6H6c8C/94EIO+UuKMGXuZzG4Qf6OWo1D/tMpx+504PBNylFJ9i7 ZfruHUVGaYYtcuNYj5Gd5MyNuvdMpjfh1V+kg=
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 :cc:content-type:content-transfer-encoding; b=kOntdhWUSxGgtLL8lWKNZHzDbv+lOK8h3dscRD2HN/Fklv6L9iylQB0M0Qee/yQwya KGs6OwHWz51bKBJOkB+LUQpCvmeT9Ka1Kae1v2S5fdYDFcb5BiEvEG08l91NWy9fKxXZ J2ozAis6FBYAc6791awknDv9ogaRoPQ9YIE6Q=
MIME-Version: 1.0
Received: by 10.114.237.24 with SMTP id k24mr1459703wah.24.1266962503410; Tue,  23 Feb 2010 14:01:43 -0800 (PST)
In-Reply-To: <4B83F531.90002@sri.com>
References: <4B83F531.90002@sri.com>
Date: Tue, 23 Feb 2010 17:01:43 -0500
Message-ID: <882cf1911002231401t6b8d2492k5ddddeb0721f6b31@mail.gmail.com>
From: Joe Klein <jsklein@gmail.com>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 24 Feb 2010 09:30:25 -0800
Cc: IPv6 Operations <v6ops@ops.ietf.org>, ipsec@ietf.org, "nav6tf@ipv6forum.com" <nav6tf@ipv6forum.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [Nav6tf] FYI: NIST Publication "Guidelines for the secure deployment of IPv6"
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, 23 Feb 2010 21:59:43 -0000

Ed,

I started to review the NIST SP 800-119 today. My focus has been to
look at the document from both the defenders and attackers
prospective, as I did with the DOD IPv6 security standards.

As usual with documents from Sheila Frankel, it is well written,
annotated and filled allot of useful information.  I am also enjoying
additions from my "Hacking and Defending IPv6" course included in the
document.


Joe Klein
IPv6 Security Researcher
Cell: (703) 594-1419
jsklein@gmail.com



On Tue, Feb 23, 2010 at 10:33 AM, Ed Jankiewicz
<edward.jankiewicz@sri.com> wrote:
> I had nothing to do with this doc, and have not fully reviewed it yet,
> but thought it would be of interest to folks on these lists.
>
> Please do not send your comments to me or post on these lists, but
> follow the instructions at the link to comment directly to the authors.
> I am sure NIST would appreciate any insight from additional folks who
> have not already contributed to discussion on the draft publication.
>
> http://csrc.nist.gov/publications/PubsDrafts.html#SP-800-119
>
> --
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research
> Supporting DISA Standards Engineering Branch
> 732-389-1003 or =A0ed.jankiewicz@sri.com
>
> _______________________________________________
> Nav6tf mailing list
> Nav6tf@ipv6forum.com
> http://lists.ipv6forum.com/mailman/listinfo/nav6tf
>

From zhangdacheng@huawei.com  Sat Feb 27 00:16:03 2010
Return-Path: <zhangdacheng@huawei.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 EDF1428C39A for <behave@core3.amsl.com>; Sat, 27 Feb 2010 00:16:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.525
X-Spam-Level: *
X-Spam-Status: No, score=1.525 tagged_above=-999 required=5 tests=[AWL=3.239,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, 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 ZFitF3QGkbCt for <behave@core3.amsl.com>; Sat, 27 Feb 2010 00:16:03 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C0C2A3A8763 for <behave@ietf.org>; Sat, 27 Feb 2010 00:16:02 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYH004KVR25WF@szxga03-in.huawei.com> for behave@ietf.org; Sat, 27 Feb 2010 16:18:05 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KYH00MADR250G@szxga03-in.huawei.com> for behave@ietf.org; Sat, 27 Feb 2010 16:18:05 +0800 (CST)
Received: from z00133208 ([10.111.13.7]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KYH006RRR24JT@szxml06-in.huawei.com> for behave@ietf.org; Sat, 27 Feb 2010 16:18:05 +0800 (CST)
Date: Sat, 27 Feb 2010 16:18:03 +0800
From: Dacheng Zhang <zhangdacheng@huawei.com>
To: behave@ietf.org
Message-id: <019001cab785$62d06b80$070d6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_IfVVsCdkF3X4RQiNlTqtkg)"
Thread-index: Acq3hWDiPhSOgCmZS+iRRNm0BifuwQ==
Subject: [BEHAVE] two ideas
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: Sat, 27 Feb 2010 08:16:04 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_IfVVsCdkF3X4RQiNlTqtkg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hello, everybody:

 

After reading draft-wing-behave-dns64-config-02, I have two ideas here, and
hope to get your kindly comments:

 

1. In section 3.2, it is suggested to use DNSsec to disable DNS64. But in
order to deal with the circumstance where synthesized addresses have been
already encapsulated in AAAA records, maybe it is a good idea to specify a
new flag in the DNS answer containing an AAAA RR. The flag indicates that a
synthesized address is contained in the RR. An updated dual-stack host can
recognize it while conventional ones will just ignore the flag.

 

2. In the sections 3.5 and 3.6, solutions of using DHCP to identify dual
stack host are introduced. I want to know whether it is another feasible
solution to define an option for dual stack hosts. If such an option is
attached in a request from a host, the DHCP server will ensure that the host
has a dual-stack. 

 

What do you think of them?

 

BR ^_^

 

Dacheng


--Boundary_(ID_IfVVsCdkF3X4RQiNlTqtkg)
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:&#23435;&#20307;;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"FrutigerNext LT Regular";
	panose-1:2 11 5 3 4 5 4 2 2 4;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@&#23435;&#20307;";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Times New Roman";}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:"Times New Roman";}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:9.0pt;
	font-family:"Times New Roman";}
p.a, li.a, div.a
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"FrutigerNext LT Regular";
	layout-grid-mode:line;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01CAB7C8.6ED426E0") es;
	=
mso-endnote-continuation-separator:url("cid:header.htm\@01CAB7C8.6ED426E0=
") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-footer:url("cid:header.htm\@01CAB7C8.6ED426E0") f1;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</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=3DZH-CN link=3Dblue vlink=3Dpurple =
style=3D'text-justify-trim:punctuation'>

<div class=3DSection1 style=3D'layout-grid:15.6pt'>

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;line-height:12.0pt;
text-autospace:none'><font size=3D3 face=3D&#23435;&#20307;><span =
lang=3DEN-US style=3D'font-size:
12.0pt;font-family:&#23435;&#20307;'>Hello, =
everybody:<o:p></o:p></span></font></p>

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;line-height:12.0pt;
text-autospace:none'><font size=3D3 face=3D&#23435;&#20307;><span =
lang=3DEN-US style=3D'font-size:
12.0pt;font-family:&#23435;&#20307;'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;line-height:12.0pt;
text-autospace:none'><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'>After=
 reading
draft-wing-behave-dns64-config-02, I have two ideas here, and hope to =
get your
kindly comments:<o:p></o:p></span></font></p>

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;line-height:12.0pt;
text-autospace:none'><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'><o:p>=
&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;line-height:12.0pt;
text-autospace:none'><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'>1. =
In section 3.2, it is
suggested to use DNSsec to disable DNS64. But in order to deal with the
circumstance where synthesized addresses have been already encapsulated =
in AAAA
records, maybe it is a good idea to specify a new flag in the DNS answer
containing an AAAA RR. The flag indicates that a synthesized address is
contained in the RR. An updated dual-stack host can recognize it while =
conventional
ones will just ignore the flag.<o:p></o:p></span></font></p>

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;line-height:12.0pt;
text-autospace:none'><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'><o:p>=
&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'>2. =
In the sections 3.5 and
3.6, solutions of using DHCP to identify dual stack host are introduced. =
I want
to know whether it is another feasible solution to define an option for =
dual
stack hosts. If such an option is attached in a request from a host, the =
DHCP
server will ensure that the host has a dual-stack. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'><o:p>=
&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'>What =
do you think of them?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'><o:p>=
&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'>BR =
^_^<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'><o:p>=
&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3D&#23435;&#20307;><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:&#23435;&#20307;;color:black'>Dache=
ng</span></font><font
size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:Arial'><!--[if gte vml =
1]><v:shapetype=20
 id=3D"_x0000_t74" coordsize=3D"21600,21600" o:spt=3D"74" =
path=3D"m10860,2187c10451,1746,9529,1018,9015,730,7865,152,6685,,5415,,41=
75,152,2995,575,1967,1305,1150,2187,575,3222,242,4220,,5410,242,6560,575,=
7597l10860,21600,20995,7597v485,-1037,605,-2187,485,-3377c21115,3222,2042=
0,2187,19632,1305,18575,575,17425,152,16275,,15005,,13735,152,12705,730v-=
529,288,-1451,1016,-1845,1457xe">
 <v:stroke joinstyle=3D"miter" />
 <v:path gradientshapeok=3D"t" o:connecttype=3D"custom" =
o:connectlocs=3D"10860,2187;2928,10800;10860,21600;18672,10800"=20
  o:connectangles=3D"270,180,90,0" textboxrect=3D"5037,2277,16557,13677" =
/>
</v:shapetype><v:shape id=3D"DtsShapeName" o:spid=3D"_x0000_s1026" =
type=3D"#_x0000_t74"=20
 =
alt=3D"EUR1G9751E205B0G8487EB4C6@9CE1GC08:K@E;0M:d[11022319!!!BIHO@]{1102=
23191@7G1E16110D81@11D8COnsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!)"=20
 =
style=3D'position:absolute;left:0;text-align:left;margin-left:0;margin-to=
p:0;
 width:.05pt;height:.05pt;z-index:1;visibility:hidden;
 =
mso-position-horizontal-relative:text;mso-position-vertical-relative:text=
'>
 <w:anchorlock/>
</v:shape><![endif]--></span></font><font size=3D1 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial'><o:p></o:p></span></font></p>=


</div>

</body>

</html>

--Boundary_(ID_IfVVsCdkF3X4RQiNlTqtkg)--

From root@core3.amsl.com  Sat Feb 27 05:15:04 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 E572D28C0D7; Sat, 27 Feb 2010 05:15:03 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100227131503.E572D28C0D7@core3.amsl.com>
Date: Sat, 27 Feb 2010 05:15:03 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-framework-07.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: Sat, 27 Feb 2010 13:15:04 -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           : Framework for IPv4/IPv6 Translation
	Author(s)       : F. Baker, et al.
	Filename        : draft-ietf-behave-v6v4-framework-07.txt
	Pages           : 30
	Date            : 2010-02-27

This note describes a framework for IPv4/IPv6 translation.  This is
in the context of replacing NAT-PT, which was deprecated by RFC 4966,
and to enable networks to have IPv4 and IPv6 coexist in a somewhat
rational manner while transitioning to an IPv6 network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-framework-07.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-v6v4-framework-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Sat Feb 27 05:15:04 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 1D6F128C145; Sat, 27 Feb 2010 05:15:03 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100227131504.1D6F128C145@core3.amsl.com>
Date: Sat, 27 Feb 2010 05:15:03 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-10.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: Sat, 27 Feb 2010 13:15:04 -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           : IP/ICMP Translation Algorithm
	Author(s)       : X. Li, et al.
	Filename        : draft-ietf-behave-v6v4-xlate-10.txt
	Pages           : 31
	Date            : 2010-02-27

This document forms a replacement of the Stateless IP/ICMP
Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
translates between IPv4 and IPv6 packet headers (including ICMP
headers).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-10.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-v6v4-xlate-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xing@cernet.edu.cn  Sat Feb 27 06:31:21 2010
Return-Path: <xing@cernet.edu.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 24AA93A897E for <behave@core3.amsl.com>; Sat, 27 Feb 2010 06:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[AWL=-1.124,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696, MIME_CHARSET_FARAWAY=2.45]
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 aMMW26v9TOtS for <behave@core3.amsl.com>; Sat, 27 Feb 2010 06:31:20 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 6A4373A897C for <behave@ietf.org>; Sat, 27 Feb 2010 06:31:18 -0800 (PST)
Received: from [192.168.1.100]([123.112.66.135]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54b8994c4; Sat, 27 Feb 2010 22:33:34 +0800
Message-ID: <4B892D3A.5010009@cernet.edu.cn>
Date: Sat, 27 Feb 2010 22:33:30 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: behave@ietf.org
References: <20100227131503.E572D28C0D7@core3.amsl.com>
In-Reply-To: <20100227131503.E572D28C0D7@core3.amsl.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 2qajXlXB
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-framework-07.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: Sat, 27 Feb 2010 14:31:21 -0000

Hi, All,

We have uploaded a new version of framework draft based on the comments
received during 2nd WGLC.

Thanks.

xing, congxiao


Internet-Drafts@ietf.org дµÀ:
> 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           : Framework for IPv4/IPv6 Translation
> 	Author(s)       : F. Baker, et al.
> 	Filename        : draft-ietf-behave-v6v4-framework-07.txt
> 	Pages           : 30
> 	Date            : 2010-02-27
>
> This note describes a framework for IPv4/IPv6 translation.  This is
> in the context of replacing NAT-PT, which was deprecated by RFC 4966,
> and to enable networks to have IPv4 and IPv6 coexist in a somewhat
> rational manner while transitioning to an IPv6 network.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-framework-07.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.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From xing@cernet.edu.cn  Sat Feb 27 06:31:54 2010
Return-Path: <xing@cernet.edu.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 F26843A8983 for <behave@core3.amsl.com>; Sat, 27 Feb 2010 06:31:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.486
X-Spam-Level: *
X-Spam-Status: No, score=1.486 tagged_above=-999 required=5 tests=[AWL=-1.061,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696, MIME_CHARSET_FARAWAY=2.45]
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 nyr27zKZ6n5c for <behave@core3.amsl.com>; Sat, 27 Feb 2010 06:31:53 -0800 (PST)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 5D3103A8982 for <behave@ietf.org>; Sat, 27 Feb 2010 06:31:52 -0800 (PST)
Received: from [192.168.1.100]([123.112.66.135]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm1d4b8994e6; Sat, 27 Feb 2010 22:34:08 +0800
Message-ID: <4B892D63.3070002@cernet.edu.cn>
Date: Sat, 27 Feb 2010 22:34:11 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: behave@ietf.org
References: <20100227131504.1D6F128C145@core3.amsl.com>
In-Reply-To: <20100227131504.1D6F128C145@core3.amsl.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 2uIkXlXB
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-10.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: Sat, 27 Feb 2010 14:31:54 -0000

Hi, All,

We have uploaded a new version of xlate draft based on the comments
received during 2nd WGLC.

Thanks.

xing, congxiao

Internet-Drafts@ietf.org дµÀ:
> 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           : IP/ICMP Translation Algorithm
> 	Author(s)       : X. Li, et al.
> 	Filename        : draft-ietf-behave-v6v4-xlate-10.txt
> 	Pages           : 31
> 	Date            : 2010-02-27
>
> This document forms a replacement of the Stateless IP/ICMP
> Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
> translates between IPv4 and IPv6 packet headers (including ICMP
> headers).
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-10.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.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From rvaithia@cisco.com  Sat Feb 27 22:50:46 2010
Return-Path: <rvaithia@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 3CE033A8640 for <behave@core3.amsl.com>; Sat, 27 Feb 2010 22:50:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 iHbhde8bzc0c for <behave@core3.amsl.com>; Sat, 27 Feb 2010 22:50:45 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 6F2B63A8636 for <behave@ietf.org>; Sat, 27 Feb 2010 22:50:45 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACOhiUurRN+K/2dsb2JhbACDBZgYc6FuiBcBj0mBMYJdbQSDF4sg
X-IronPort-AV: E=Sophos;i="4.49,554,1262563200"; d="scan'208";a="489463525"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-6.cisco.com with ESMTP; 28 Feb 2010 06:50:45 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1S6ojNG006452; Sun, 28 Feb 2010 06:50:45 GMT
Received: from xmb-sjc-231.amer.cisco.com ([128.107.191.73]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 27 Feb 2010 22:50:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Date: Sat, 27 Feb 2010 22:50:44 -0800
Message-ID: <A0988C2F192F124FAFE3D70264C045870B09A60F@xmb-sjc-231.amer.cisco.com>
In-Reply-To: <4B892D63.3070002@cernet.edu.cn>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-10.txt
Thread-Index: Acq3ufIlrfyA0K+qR3O1MHbNMlcHwQAh+ZsA
References: <20100227131504.1D6F128C145@core3.amsl.com> <4B892D63.3070002@cernet.edu.cn>
From: "Ramji Vaithianathan (rvaithia)" <rvaithia@cisco.com>
To: "Xing Li" <xing@cernet.edu.cn>, <behave@ietf.org>
X-OriginalArrivalTime: 28 Feb 2010 06:50:45.0324 (UTC) FILETIME=[5A2580C0:01CAB842]
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-10.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: Sun, 28 Feb 2010 06:50:46 -0000

Hi,

In the section 3.1 on IPv4 --> IPv6 translation it is mentioned:

   If the DF bit is set and the packet is not a fragment (i.e., the MF
   flag is not set and the Fragment Offset is equal to zero) then the
   translator SHOULD NOT add a Fragment header to the resulting packet.

Will there ever be a case where DF bit is set and packet is still a fragment (MF flag set OR  FragOffset field is non-zero)?  
Generally if DF bit is set, packets should never be fragmented - right?  Assume we receive such packets, I guess the Translator should drop these packets as mal-formed or should it still translate the packet ignoring the DF bit?

If there is not going to be any such cases, should we just say -
   If the DF bit is set, then the translator SHOULD NOT add a Fragment header to the resuling packet

Thanks,

Ramji 

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of Xing Li
Sent: Saturday, February 27, 2010 8:04 PM
To: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-10.txt

Hi, All,

We have uploaded a new version of xlate draft based on the comments received during 2nd WGLC.

Thanks.

xing, congxiao

Internet-Drafts@ietf.org $B<LF;(J:
> 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           : IP/ICMP Translation Algorithm
> 	Author(s)       : X. Li, et al.
> 	Filename        : draft-ietf-behave-v6v4-xlate-10.txt
> 	Pages           : 31
> 	Date            : 2010-02-27
>
> This document forms a replacement of the Stateless IP/ICMP Translation 
> Algorithm (SIIT) described in RFC 2765.  The algorithm translates 
> between IPv4 and IPv6 packet headers (including ICMP headers).
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-10.tx
> t
>
> 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.
>   
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> 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 root@core3.amsl.com  Sun Feb 28 17:15:02 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 2AC613A7655; Sun, 28 Feb 2010 17:15:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100301011502.2AC613A7655@core3.amsl.com>
Date: Sun, 28 Feb 2010 17:15:02 -0800 (PST)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-turn-uri-10.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: Mon, 01 Mar 2010 01:15:02 -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           : Traversal Using Relays around NAT (TURN) Resolution Mechanism
	Author(s)       : M. Petit-Huguenin
	Filename        : draft-ietf-behave-turn-uri-10.txt
	Pages           : 15
	Date            : 2010-02-28

This document defines a resolution mechanism to generate a list of
server transport addresses that can be tried to create a Traversal
Using Relays around NAT (TURN) allocation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-turn-uri-10.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-turn-uri-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--
