From owner-v6ops@ops.ietf.org  Tue Nov  4 12:26:55 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0364F3A6C6F
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue,  4 Nov 2008 12:26:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level: 
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[AWL=-1.065,
	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 BIzclTlNq45z
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue,  4 Nov 2008 12:26:54 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 249583A6C65
	for <v6ops-archive@lists.ietf.org>; Tue,  4 Nov 2008 12:26:54 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KxSPD-0004US-Sm
	for v6ops-data@psg.com; Tue, 04 Nov 2008 20:21:39 +0000
Received: from [209.85.198.232] (helo=rv-out-0506.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <brian.e.carpenter@gmail.com>)
	id 1KxSP8-0004TH-8z
	for v6ops@ops.ietf.org; Tue, 04 Nov 2008 20:21:36 +0000
Received: by rv-out-0506.google.com with SMTP id b25so3303361rvf.41
        for <v6ops@ops.ietf.org>; Tue, 04 Nov 2008 12:21:33 -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=dZErejszBZHSE5lgIueURBLyq+sgR+cSzcJPup3FhbM=;
        b=BCAls4h2F7ziey/aFKFvHyh70kJlH1FjYPUXd491Fvzax4Onl6g89RRw4XezDVy4uC
         tst6px77l1oUXCt6VDHfKYIU2UUghcFrFvJ+q2fUqg9sD7nnYOhxL8TiUnRaVvXIaoUJ
         moB3CzBfbf3rqzhRIYrMxm0GsmLQpaEEgfNSA=
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=NArU35mKNqxcB+zQ9mtBVRjLZL3tS0nvpr9bxjvI1qDeLc54FwGe2mX4jnn18Bv1oP
         ZPIwhYSxqHHTbmdPZD0SsaRZi/tgqitla5z3nVKQsj2swIMGWZYhpBqAZM0fZsKDkANv
         r4wAJiufMjjt6EQJFHI/eghwfU3w5QCFweq8Q=
Received: by 10.140.188.19 with SMTP id l19mr9369rvf.79.1225830093082;
        Tue, 04 Nov 2008 12:21:33 -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 f21sm4552988rvb.5.2008.11.04.12.21.30
        (version=SSLv3 cipher=RC4-MD5);
        Tue, 04 Nov 2008 12:21:32 -0800 (PST)
Message-ID: <4910AEC8.6070505@gmail.com>
Date: Wed, 05 Nov 2008 09:21:28 +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: Sam Hartman <hartmans-ietf@mit.edu>
CC: Nathan Ward <v6ops@daork.net>, 
 Christian Huitema <huitema@windows.microsoft.com>,
 Dave Thaler <dthaler@windows.microsoft.com>, 
 Tim Polk <tim.polk@nist.gov>,
 "secdir@mit.edu" <secdir@mit.edu>, 
 Suresh Krishnan <suresh.krishnan@ericsson.com>,
 "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, 
 "Jim_Hoagland@symantec.com" <jim_hoagland@symantec.com>
Subject: Re: [secdir] SECDIR review: draft-ietf-v6ops-tunnel-concerns
References: <8B128AB2-BBD9-49B9-A837-F00DD80BF5D3@Isode.com>	<48F2C29B.8090900@ericsson.com>	<D6947E23-5209-4767-882A-7EBA645B3DCB@daork.net>	<48F8EE0D.4060307@ericsson.com> <48FB9A79.8040407@gmail.com>	<8EFB68EAE061884A8517F2A755E8B60A134A70E895@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>	<48FDFBCB.1090508@ericsson.com> <48FE4681.4070006@gmail.com>	<5333EA69-337F-4373-A247-1852B61D96C0@daork.net>	<48FF8AEC.9060708@gmail.com> <tsl8wrzvctw.fsf@mit.edu>
In-Reply-To: <tsl8wrzvctw.fsf@mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 2008-11-05 02:29, Sam Hartman wrote:
>>>>>> "Brian" == Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>     >>  Operating a Teredo server on site does not help unfortunately.
>     >> 
>     >> It helps an administrator filter outbound packets when sent to
>     >> an IPv6 address outside 2001::/32. It does not help an
>     >> administrator filter inbound packets, or packets to/from other
>     >> Teredo hosts.
> 
>     Brian> As far as I can see, there's a general problem in
>     Brian> attempting to detect and block Teredo packets (I mean
>     Brian> UDP/IPv4 packets in Teredo format). But it seems to me that
>     Brian> by running an internal Teredo server, a site is much better
>     Brian> placed to track and trace Teredo users. This is important
>     Brian> as Teredo users really need to be running an IPv6-savvy
>     Brian> host firewall.
> 
> Only if you can convince the users to use that teredo server rather
> than say the teredo server that is configured by default in their OS.

Agreed, most users will not spontaneously type
netsh interface ipv6 set teredo server foobar.
You could inject a /32 route into the local IGP.

> Unfortunately, by the time you've already reconfigured the computer
> you are probably in a position to either disable Teredo if you don't
> like it or install a reasonable firewall.

Agreed, for sites where the management has that much control
over hosts.

   Brian




From owner-v6ops@ops.ietf.org  Wed Nov  5 08:36:53 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5972B3A6BEC
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed,  5 Nov 2008 08:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.646
X-Spam-Level: 
X-Spam-Status: No, score=-4.646 tagged_above=-999 required=5
	tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 EikCGXgFDZrc
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed,  5 Nov 2008 08:36:52 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 870193A6A29
	for <v6ops-archive@lists.ietf.org>; Wed,  5 Nov 2008 08:36:51 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KxlIO-0002Gc-TC
	for v6ops-data@psg.com; Wed, 05 Nov 2008 16:31:52 +0000
Received: from [64.102.122.149] (helo=rtp-iport-2.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <wbeebee@cisco.com>)
	id 1KxlIH-0002FQ-Lv
	for v6ops@ops.ietf.org; Wed, 05 Nov 2008 16:31:49 +0000
X-IronPort-AV: E=Sophos;i="4.33,551,1220227200"; 
   d="scan'208,217";a="26816034"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
  by rtp-iport-2.cisco.com with ESMTP; 05 Nov 2008 16:31:44 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mA5GViN8009851;
	Wed, 5 Nov 2008 11:31:44 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mA5GViaa016191;
	Wed, 5 Nov 2008 16:31:44 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 5 Nov 2008 11:31:44 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93F63.FD56F553"
Subject: RE: [BEHAVE] Comments on the NAT66 draft
Date: Wed, 5 Nov 2008 11:31:43 -0500
Message-ID: <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <4911B9E7.8090108@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] Comments on the NAT66 draft
Thread-Index: Ack/WnCi/zGj7vvUTrecJF+8TSNSPQACJMQQ
References: <4911B9E7.8090108@free.fr>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>,
        "Margaret Wasserman" <mrw@lilacglade.org>
Cc: "Behave WG" <behave@ietf.org>, <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 05 Nov 2008 16:31:44.0340 (UTC) FILETIME=[FD753940:01C93F63]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=13430; t=1225902704; x=1226766704;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co
	m>
	|Subject:=20RE=3A=20[BEHAVE]=20Comments=20on=20the=20NAT66=
	20draft
	|Sender:=20
	|To:=20=3D?iso-8859-1?Q?R=3DE9mi_Despr=3DE9s?=3D=20<remi.de
	spres@free.fr>,=0A=20=20=20=20=20=20=20=20=22Margaret=20Wass
	erman=22=20<mrw@lilacglade.org>;
	bh=MYVxvnNXl2SPIsQAiiIziKoC+cfN/9QuEXSYZhfot+I=;
	b=mKMicygxqDkFVmp62aWiUGmjIKPz5h7EitplrMI4Uxb0X3XXdk6vD/P/5T
	PiK8pHnpcES1lZjJoUyqq8genmRuYhGTb5C/w3IWz72LrlJJE5wUPdfSMgji
	e8M7BX7XFa;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93F63.FD56F553
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I understand that NAT66 work on the details is being done in the BEHAVE =
Working Group - but shouldn't we also include a discussion at v6ops on =
whether NAT66 should be standardized?  After all, they're more privy to =
the discussions that created the Local Network Protection RFC...
=20
- Wes

________________________________

From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of R=E9mi Despr=E9s
Sent: Wednesday, November 05, 2008 10:21 AM
To: Margaret Wasserman
Cc: Behave WG
Subject: [BEHAVE] Comments on the NAT66 draft


Hi Margaret,=20

Sorry for so late an answer (I was too busy preparing my own draft =
before the deadline).=20
Here are my comments, section per section.=20

Sec. 3 - Motivation)
a. I _FULLY SUPPORT_ that IETF should standardize some ways to keep, in =
IPv6, appreciated benefits of NAT44s (and to avoid as much as possible =
their drawbacks).=20
b. In your list of NAT44 appreciated services (i.e. provider independent =
addressing, simplified site multihoming, topology hiding), "host =
privacy" should IMHO be added. This is the impossibility, from the =
outside, to see that several consecutive connections were initiated by =
the same host.=20
c. Concerning multihoming, a more detailed analysis of what NATs do, and =
don't do, would be a useful clarification. (In particular, they  are =
incompatible with multihoming of both Shim6 and SCTP. These the =
protocols, to take advantage of multihoming, exchange address =
information in payloads, protected by strong checksums.)=20

Sec. 4 - NAT66 overview
a. Since your proposed mechanism is only based on stateless and =
reversible  _mappings_, calling it a NAT leads, IMHO, to confusion: NATs =
are generally understood, and used, as NAPTs. They do  stateful and  =
non-reversible 1:n  _translations_.=20
b. With a different name than NAT for such a proposal, IETF could =
advertise that it _does not endorse NATs in IPv6_. This would IMHO =
increase  (or restore?) confidence in IPv6. "Mapping" instead of =
"translation"would be a logical word in such a name.

Sec. 5 - NAT66 Address Mapping Mechanisms=20
- Topology hiding is in fact possible without losing reversibility of =
the mapping. Cf the comment on 5.1.2.=20

Sec. 5.1 - Checksum-Neutral Mapping=20
- IMHO, it would be useful to make it clear in this section (like in the =
introduction) that the proposed mapping does not apply to addresses that =
are transmitted in payloads.  ALGs could be be added to convert =
addresses in TCP payloads TCP, as it is done in some NAT44s.  But it =
cannot be done not in SCTP payloads because of the stronger checksum =
algorithm.=20

Sec. 5.1.1 - Two-way Algorithmic Address Mapping=20
- The proposed limitation to /48 internal and external prefixes is =
stronger than necessary.=20
- A sufficient limitation is that external prefixes are not longer than =
internal ones. (If  the external prefix is shorter, a few 0 bits can be =
added to it, up to the  length to the internal one.) For example a /56 =
external with a /60 internal should be permitted.=20

Sec. 5.1.2 - Topology hiding Option=20
- For outgoing UDP and TCP connections, it is in fact possible to hide =
the internal topology without losing  reversibility of the mapping:  the =
algorithmic mapping is, for this, applied jointly to the subnet =
identifier AND to port bits (excluding port-bits 0 and 1 that must =
remain constant in dynamic ports). UDP and TCP checksums are then =
incrementally adjusted (like IP checksums).=20
- In addition to topology hiding, this mechanism provides _host privacy_ =
, as defined in the comment on sec. 3 :-) .=20

Sec 6. - Prefixes for Port Mapping=20
- I don't see the need for this section in this document. The mapping =
applies to internal and external  prefixes, independently of how they =
can be configured.=20

Sec 7 - A note on Port Mapping
- Agreed: address amplification should not be needed in IPv6. Agreed =
also: some transport layers that encrypt data are incompatible with port =
mapping. But this is not sufficient to abandon port mapping all-over. =
(See the comment on 5.1.2.)=20

Sec 8 - Security Considerations=20
- In TCP, DCCP, SCTP, packets that initiate connection establishments  =
can be individually recognized (SYN without ack in the case of TCP). =
Incoming connections  can therefore be blocked with stateless operation, =
but this is not the case for UDP (per-connection stateful operation is =
needed). Whether blocking UDP incoming connections is worth it, in =
global to local IPv6 gateways, is  therefore uncertain (hosts must =
anyway have their own blocking of undesirable incoming connections).=20

In summary:=20
- the document  introduces IMO a *very useful subject*.=20
- Before freezing any recommendation,  its relationship with other =
layers, in particular with other stateless address mappings, should be =
further studied.=20

Best regards,=20

RD=20


Margaret Wasserman   (1-12/1-31/200x) 10/27/08 7:59 PM:=20


	I have posted a NAT66 draft, so that we can have a better-grounded =
discussion of whether it makes sense to include NAT66 as a work item in =
the behave charter.  The draft can be found at the following URL:=20
=09
	http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt=20
=09
	Feedback would be greatly appreciated!=20


------_=_NextPart_001_01C93F63.FD56F553
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D325452416-05112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I understand that NAT66 work on the details is =
being done=20
in the BEHAVE Working Group - but shouldn't we also include a discussion =
at=20
v6ops on whether NAT66 should be standardized?&nbsp; After all, they're =
more=20
privy to the discussions that created the Local Network Protection=20
RFC...</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D325452416-05112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D325452416-05112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Wes</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> behave-bounces@ietf.org=20
[mailto:behave-bounces@ietf.org] <B>On Behalf Of </B>R=E9mi=20
Despr=E9s<BR><B>Sent:</B> Wednesday, November 05, 2008 10:21 =
AM<BR><B>To:</B>=20
Margaret Wasserman<BR><B>Cc:</B> Behave WG<BR><B>Subject:</B> [BEHAVE] =
Comments=20
on the NAT66 draft<BR></FONT><BR></DIV>
<DIV></DIV>Hi Margaret, <BR><BR>Sorry for so late an answer (I was too =
busy=20
preparing my own draft before the deadline). <BR>Here are my comments, =
section=20
per section. <BR><BR>Sec. 3 - Motivation)<BR>a. I <B =
class=3Dmoz-txt-star><SPAN=20
class=3Dmoz-txt-tag>_</SPAN>FULLY SUPPORT<SPAN =
class=3Dmoz-txt-tag>_</SPAN></B> that=20
IETF should standardize some ways to keep, in IPv6, appreciated benefits =
of=20
NAT44s (and to avoid as much as possible their drawbacks). <BR>b. In =
your list=20
of NAT44 appreciated services (i.e. provider independent addressing, =
simplified=20
site multihoming, topology hiding), "host privacy" should IMHO be added. =
This is=20
the impossibility, from the outside, to see that several consecutive =
connections=20
were initiated by the same host. <BR>c. Concerning multihoming, a more =
detailed=20
analysis of what NATs do, and don't do, would be a useful clarification. =
(In=20
particular, they&nbsp; are incompatible with multihoming of both Shim6 =
and SCTP.=20
These the protocols, to take advantage of multihoming, exchange address=20
information in payloads, protected by strong checksums.) <BR><BR>Sec. 4 =
- NAT66=20
overview<BR>a. Since your proposed mechanism is only based on stateless =
and=20
reversible <B class=3Dmoz-txt-star>&nbsp;<SPAN=20
class=3Dmoz-txt-tag></SPAN>_mapping<SPAN =
class=3Dmoz-txt-tag>s</SPAN></B>_, calling=20
it a NAT leads, IMHO, to confusion: NATs are generally understood, and =
used, as=20
NAPTs. They do&nbsp; stateful and&nbsp; non-reversible 1:n&nbsp; <SPAN=20
class=3Dmoz-txt-underscore><SPAN=20
class=3Dmoz-txt-tag>_</SPAN><B>translations</B><SPAN=20
class=3Dmoz-txt-tag>_</SPAN></SPAN>. <BR>b. With a different name than =
NAT for=20
such a proposal, IETF <SPAN class=3Dmoz-txt-star><SPAN=20
class=3Dmoz-txt-tag>could</SPAN></SPAN><B class=3Dmoz-txt-star><SPAN=20
class=3Dmoz-txt-tag> </SPAN></B><SPAN class=3Dmoz-txt-star><SPAN=20
class=3Dmoz-txt-tag>advertise that it </SPAN></SPAN><B =
class=3Dmoz-txt-star><SPAN=20
class=3Dmoz-txt-tag>_</SPAN>does not endorse<SPAN =
class=3Dmoz-txt-tag></SPAN></B>=20
<B>NATs in IPv6</B>_. This would IMHO increase&nbsp; (or restore?) =
confidence in=20
IPv6. "Mapping" instead of "translation"would be a logical word in such =
a=20
name.<BR><BR>Sec. 5 - NAT66 Address Mapping Mechanisms <BR>- Topology =
hiding is=20
in fact possible without losing reversibility of the mapping. Cf the =
comment on=20
5.1.2. <BR><BR>Sec. 5.1 - Checksum-Neutral Mapping <BR>- IMHO, it would =
be=20
useful to make it clear in this section (like in the introduction) that =
the=20
proposed mapping does not apply to addresses that are transmitted in=20
payloads.&nbsp; ALGs could be be added to convert addresses in TCP =
payloads TCP,=20
as it is done in some NAT44s.&nbsp; But it cannot be done not in SCTP =
payloads=20
because of the stronger checksum algorithm. <BR><BR>Sec. 5.1.1 - Two-way =

Algorithmic Address Mapping <BR>- The proposed limitation to /48 =
internal and=20
external prefixes is stronger than necessary. <BR>- A sufficient =
limitation is=20
that external prefixes are not longer than internal ones. (If&nbsp; the =
external=20
prefix is shorter, a few 0 bits can be added to it, up to the&nbsp; =
length to=20
the internal one.) For example a /56 external with a /60 internal should =
be=20
permitted. <BR><BR>Sec. 5.1.2 - Topology hiding Option <BR>- For =
outgoing UDP=20
and TCP connections, it is in fact possible to hide the internal =
topology=20
without losing&nbsp; reversibility of the mapping:&nbsp; the algorithmic =
mapping=20
is, for this, applied jointly to the subnet identifier AND to port bits=20
(excluding port-bits 0 and 1 that must remain constant in dynamic =
ports). UDP=20
and TCP checksums are then incrementally adjusted (like IP checksums). =
<BR>- In=20
addition to topology hiding, this mechanism provides _<B>host =
privac</B>y_ , as=20
defined in the comment on sec. 3<SPAN class=3Dmoz-smiley-s1><SPAN> :-)=20
</SPAN></SPAN>. <BR><BR>Sec 6. - Prefixes for Port Mapping <BR>- I don't =
see the=20
need for this section in this document. The mapping applies to internal =
and=20
external&nbsp; prefixes, independently of how they can be configured.=20
<BR><BR>Sec 7 - A note on Port Mapping<BR>- Agreed: address =
amplification should=20
not be needed in IPv6. Agreed also: some transport layers that encrypt =
data are=20
incompatible with port mapping. But this is not sufficient to abandon =
port=20
mapping all-over. (See the comment on 5.1.2.) <BR><BR>Sec 8 - Security=20
Considerations <BR>- In TCP, DCCP, SCTP, packets that initiate =
connection=20
establishments&nbsp; can be individually recognized (SYN without ack in =
the case=20
of TCP). Incoming connections&nbsp; can therefore be blocked with =
stateless=20
operation, but this is not the case for UDP (per-connection stateful =
operation=20
is needed). Whether blocking UDP incoming connections is worth it, in =
global to=20
local IPv6 gateways, is&nbsp; therefore uncertain (hosts must anyway =
have their=20
own blocking of undesirable incoming connections). <BR><BR>In summary: =
<BR>- the=20
document&nbsp; introduces IMO a <B class=3Dmoz-txt-star><SPAN=20
class=3Dmoz-txt-tag>*</SPAN>very useful subject<SPAN=20
class=3Dmoz-txt-tag>*</SPAN></B>. <BR>- Before freezing any =
recommendation,&nbsp;=20
its relationship with other layers, in particular with other stateless =
address=20
mappings, should be further studied. <BR><BR>Best regards, <BR><BR>RD=20
<BR><BR><BR>Margaret Wasserman&nbsp;&nbsp; (1-12/1-31/200x) 10/27/08 =
7:59 PM:=20
<BR>
<BLOCKQUOTE type=3D"cite">I have posted a NAT66 draft, so that we can =
have a=20
  better-grounded discussion of whether it makes sense to include NAT66 =
as a=20
  work item in the behave charter.&nbsp; The draft can be found at the =
following=20
  URL: <BR><BR><A class=3Dmoz-txt-link-freetext=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt=
">http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt</A>=20
  <BR><BR>Feedback would be greatly appreciated! =
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C93F63.FD56F553--



From owner-v6ops@ops.ietf.org  Thu Nov  6 03:06:23 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D29EF3A68EC
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 03:06:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level: 
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_13=0.6, 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 ZrsX+zZ8X3Bg
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 03:06:22 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 914293A6847
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 03:06:22 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Ky2b3-0003m3-Cu
	for v6ops-data@psg.com; Thu, 06 Nov 2008 11:00:17 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1Ky2av-0003kx-Iu
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 11:00:12 +0000
Received: (qmail 11337 invoked by uid 417); 6 Nov 2008 10:59:22 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 6 Nov 2008 10:59:22 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Thu, 06 Nov 2008 03:59:21 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> 
From: EricLKlein@softhome.net
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
Cc: "=?iso-8859-1?Q?R=E9mi=20Despr=E9s?=" <remi.despres@free.fr>,
  "Margaret Wasserman" <mrw@lilacglade.org>,
  "Behave WG" <behave@ietf.org>, v6ops@ops.ietf.org
Subject: Re: Comments on the NAT66 draft
Date: Thu, 06 Nov 2008 03:59:21 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.4912CE09.00003CB8@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Personally I am scared of anything that seems to make NAT suggestions for 
v6. 

That said, I think that section 3 could use a little more meat to explain 
some of the problems with NAT in terms of breaking connections etc rather 
than just pointing towards RFC 4864 as I am not sure that people will go and 
look at the cross reference. 

I would encourage discussion on this to see if there is a consensus for 
proceeding with giving hints or help to a concept that "IETF does not 
recommend" 

Eric 


Wes Beebee (wbeebee) writes: 

> I understand that NAT66 work on the details is being done in the BEHAVE Working Group - but shouldn't we also include a discussion at v6ops on whether NAT66 should be standardized?  After all, they're more privy to the discussions that created the Local Network Protection RFC...
>  
> - Wes 
> 
> ________________________________ 
> 
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of Rémi Després
> Sent: Wednesday, November 05, 2008 10:21 AM
> To: Margaret Wasserman
> Cc: Behave WG
> Subject: [BEHAVE] Comments on the NAT66 draft 
> 
> 
> Hi Margaret,  
> 
> Sorry for so late an answer (I was too busy preparing my own draft before the deadline). 
> Here are my comments, section per section.  
> 
> Sec. 3 - Motivation)
> a. I _FULLY SUPPORT_ that IETF should standardize some ways to keep, in IPv6, appreciated benefits of NAT44s (and to avoid as much as possible their drawbacks). 
> b. In your list of NAT44 appreciated services (i.e. provider independent addressing, simplified site multihoming, topology hiding), "host privacy" should IMHO be added. This is the impossibility, from the outside, to see that several consecutive connections were initiated by the same host. 
> c. Concerning multihoming, a more detailed analysis of what NATs do, and don't do, would be a useful clarification. (In particular, they  are incompatible with multihoming of both Shim6 and SCTP. These the protocols, to take advantage of multihoming, exchange address information in payloads, protected by strong checksums.)  
> 
> Sec. 4 - NAT66 overview
> a. Since your proposed mechanism is only based on stateless and reversible  _mappings_, calling it a NAT leads, IMHO, to confusion: NATs are generally understood, and used, as NAPTs. They do  stateful and  non-reversible 1:n  _translations_. 
> b. With a different name than NAT for such a proposal, IETF could advertise that it _does not endorse NATs in IPv6_. This would IMHO increase  (or restore?) confidence in IPv6. "Mapping" instead of "translation"would be a logical word in such a name. 
> 
> Sec. 5 - NAT66 Address Mapping Mechanisms 
> - Topology hiding is in fact possible without losing reversibility of the mapping. Cf the comment on 5.1.2.  
> 
> Sec. 5.1 - Checksum-Neutral Mapping 
> - IMHO, it would be useful to make it clear in this section (like in the introduction) that the proposed mapping does not apply to addresses that are transmitted in payloads.  ALGs could be be added to convert addresses in TCP payloads TCP, as it is done in some NAT44s.  But it cannot be done not in SCTP payloads because of the stronger checksum algorithm.  
> 
> Sec. 5.1.1 - Two-way Algorithmic Address Mapping 
> - The proposed limitation to /48 internal and external prefixes is stronger than necessary. 
> - A sufficient limitation is that external prefixes are not longer than internal ones. (If  the external prefix is shorter, a few 0 bits can be added to it, up to the  length to the internal one.) For example a /56 external with a /60 internal should be permitted.  
> 
> Sec. 5.1.2 - Topology hiding Option 
> - For outgoing UDP and TCP connections, it is in fact possible to hide the internal topology without losing  reversibility of the mapping:  the algorithmic mapping is, for this, applied jointly to the subnet identifier AND to port bits (excluding port-bits 0 and 1 that must remain constant in dynamic ports). UDP and TCP checksums are then incrementally adjusted (like IP checksums). 
> - In addition to topology hiding, this mechanism provides _host privacy_ , as defined in the comment on sec. 3 :-) .  
> 
> Sec 6. - Prefixes for Port Mapping 
> - I don't see the need for this section in this document. The mapping applies to internal and external  prefixes, independently of how they can be configured.  
> 
> Sec 7 - A note on Port Mapping
> - Agreed: address amplification should not be needed in IPv6. Agreed also: some transport layers that encrypt data are incompatible with port mapping. But this is not sufficient to abandon port mapping all-over. (See the comment on 5.1.2.)  
> 
> Sec 8 - Security Considerations 
> - In TCP, DCCP, SCTP, packets that initiate connection establishments  can be individually recognized (SYN without ack in the case of TCP). Incoming connections  can therefore be blocked with stateless operation, but this is not the case for UDP (per-connection stateful operation is needed). Whether blocking UDP incoming connections is worth it, in global to local IPv6 gateways, is  therefore uncertain (hosts must anyway have their own blocking of undesirable incoming connections).  
> 
> In summary: 
> - the document  introduces IMO a *very useful subject*. 
> - Before freezing any recommendation,  its relationship with other layers, in particular with other stateless address mappings, should be further studied.  
> 
> Best regards,  
> 
> RD  
> 
> 
> Margaret Wasserman   (1-12/1-31/200x) 10/27/08 7:59 PM:  
> 
> 
> 	I have posted a NAT66 draft, so that we can have a better-grounded discussion of whether it makes sense to include NAT66 as a work item in the behave charter.  The draft can be found at the following URL: 
> 	
> 	http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt 
> 	
> 	Feedback would be greatly appreciated!  
> 
 



From owner-v6ops@ops.ietf.org  Thu Nov  6 06:03:01 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7407D28C10A
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 06:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.646
X-Spam-Level: 
X-Spam-Status: No, score=-4.646 tagged_above=-999 required=5
	tests=[AWL=-0.751, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4,
	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 AehEg8pZ44kL
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 06:02:57 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2191F28C0F9
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 06:02:57 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Ky5OK-000KK1-DH
	for v6ops-data@psg.com; Thu, 06 Nov 2008 13:59:20 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <wbeebee@cisco.com>)
	id 1Ky5O4-000KHT-7m
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 13:59:17 +0000
X-IronPort-AV: E=Sophos;i="4.33,557,1220227200"; 
   d="scan'208";a="26959032"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
  by rtp-iport-1.cisco.com with ESMTP; 06 Nov 2008 13:59:02 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mA6Dx2lG013064;
	Thu, 6 Nov 2008 08:59:02 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mA6Dx2Rl014971;
	Thu, 6 Nov 2008 13:59:02 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 6 Nov 2008 08:59:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Comments on the NAT66 draft
Date: Thu, 6 Nov 2008 08:59:01 -0500
Message-ID: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <courier.4912CE09.00003CB8@softhome.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on the NAT66 draft
Thread-Index: Ack//takg3wgM6NHQfiB1PoYznAHMgAF84Ug
References: <4911B9E7.8090108@free.fr>            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: <EricLKlein@softhome.net>
Cc: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>,
        "Margaret Wasserman" <mrw@lilacglade.org>,
        "Behave WG" <behave@ietf.org>, <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 06 Nov 2008 13:59:02.0758 (UTC) FILETIME=[D3248060:01C94017]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7087; t=1225979942; x=1226843942;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co
	m>
	|Subject:=20RE=3A=20Comments=20on=20the=20NAT66=20draft
	|Sender:=20
	|To:=20<EricLKlein@softhome.net>;
	bh=Dl3x6mft/R1nOQEo+irAPNjMa9tFw4DiM9iS12iMKxI=;
	b=aH5R28qnUUJCispyFWykk+IKGobZ0cDbMgsGaQvsiWIp0k87JJQudE4yLM
	lJnL5W/9Eivbh9tIT68OI5Ufu9V6/Zo4jSjDbDi6F90o6gLI3j+8QVcN8IE8
	rRJkLKDeve;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

As we move to IPv6, NAT44, NAT64, and NAT46 will eventually go away.  =
The problem with helping NAT66 (even when that is not your intent) is =
that once it catches on, it'll be in the Internet forever and will never =
go away.

"NATs necessary for IPv6, says IETF chair"
http://www.networkworld.com/news/2008/072109-nat-housley-qna.html

Once NAT66 gets out, I can imagine even more damaging headlines (which =
conveniently miss all the subtleties of the message in section 3 of =
http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt): =
"IETF Standardizes IPv6-to-IPv6 NAT".

- Wes=20

-----Original Message-----
From: EricLKlein@softhome.net [mailto:EricLKlein@softhome.net]=20
Sent: Thursday, November 06, 2008 5:59 AM
To: Wes Beebee (wbeebee)
Cc: R=E9mi Despr=E9s; Margaret Wasserman; Behave WG; v6ops@ops.ietf.org
Subject: Re: Comments on the NAT66 draft

Personally I am scared of anything that seems to make NAT suggestions =
for v6.=20

That said, I think that section 3 could use a little more meat to =
explain some of the problems with NAT in terms of breaking connections =
etc rather than just pointing towards RFC 4864 as I am not sure that =
people will go and look at the cross reference.=20

I would encourage discussion on this to see if there is a consensus for =
proceeding with giving hints or help to a concept that "IETF does not =
recommend"=20

Eric=20


Wes Beebee (wbeebee) writes:=20

> I understand that NAT66 work on the details is being done in the =
BEHAVE Working Group - but shouldn't we also include a discussion at =
v6ops on whether NAT66 should be standardized?  After all, they're more =
privy to the discussions that created the Local Network Protection =
RFC...
> =20
> - Wes
>=20
> ________________________________
>=20
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On=20
> Behalf Of R=E9mi Despr=E9s
> Sent: Wednesday, November 05, 2008 10:21 AM
> To: Margaret Wasserman
> Cc: Behave WG
> Subject: [BEHAVE] Comments on the NAT66 draft
>=20
>=20
> Hi Margaret,
>=20
> Sorry for so late an answer (I was too busy preparing my own draft =
before the deadline).=20
> Here are my comments, section per section. =20
>=20
> Sec. 3 - Motivation)
> a. I _FULLY SUPPORT_ that IETF should standardize some ways to keep, =
in IPv6, appreciated benefits of NAT44s (and to avoid as much as =
possible their drawbacks).=20
> b. In your list of NAT44 appreciated services (i.e. provider =
independent addressing, simplified site multihoming, topology hiding), =
"host privacy" should IMHO be added. This is the impossibility, from the =
outside, to see that several consecutive connections were initiated by =
the same host.=20
> c. Concerning multihoming, a more detailed analysis of what NATs do,=20
> and don't do, would be a useful clarification. (In particular, they =20
> are incompatible with multihoming of both Shim6 and SCTP. These the=20
> protocols, to take advantage of multihoming, exchange address=20
> information in payloads, protected by strong checksums.)
>=20
> Sec. 4 - NAT66 overview
> a. Since your proposed mechanism is only based on stateless and =
reversible  _mappings_, calling it a NAT leads, IMHO, to confusion: NATs =
are generally understood, and used, as NAPTs. They do  stateful and  =
non-reversible 1:n  _translations_.=20
> b. With a different name than NAT for such a proposal, IETF could =
advertise that it _does not endorse NATs in IPv6_. This would IMHO =
increase  (or restore?) confidence in IPv6. "Mapping" instead of =
"translation"would be a logical word in such a name.=20
>=20
> Sec. 5 - NAT66 Address Mapping Mechanisms
> - Topology hiding is in fact possible without losing reversibility of =
the mapping. Cf the comment on 5.1.2. =20
>=20
> Sec. 5.1 - Checksum-Neutral Mapping
> - IMHO, it would be useful to make it clear in this section (like in =
the introduction) that the proposed mapping does not apply to addresses =
that are transmitted in payloads.  ALGs could be be added to convert =
addresses in TCP payloads TCP, as it is done in some NAT44s.  But it =
cannot be done not in SCTP payloads because of the stronger checksum =
algorithm. =20
>=20
> Sec. 5.1.1 - Two-way Algorithmic Address Mapping
> - The proposed limitation to /48 internal and external prefixes is =
stronger than necessary.=20
> - A sufficient limitation is that external prefixes are not longer =
than internal ones. (If  the external prefix is shorter, a few 0 bits =
can be added to it, up to the  length to the internal one.) For example =
a /56 external with a /60 internal should be permitted. =20
>=20
> Sec. 5.1.2 - Topology hiding Option
> - For outgoing UDP and TCP connections, it is in fact possible to hide =
the internal topology without losing  reversibility of the mapping:  the =
algorithmic mapping is, for this, applied jointly to the subnet =
identifier AND to port bits (excluding port-bits 0 and 1 that must =
remain constant in dynamic ports). UDP and TCP checksums are then =
incrementally adjusted (like IP checksums).=20
> - In addition to topology hiding, this mechanism provides _host =
privacy_ , as defined in the comment on sec. 3 :-) . =20
>=20
> Sec 6. - Prefixes for Port Mapping
> - I don't see the need for this section in this document. The mapping =
applies to internal and external  prefixes, independently of how they =
can be configured. =20
>=20
> Sec 7 - A note on Port Mapping
> - Agreed: address amplification should not be needed in IPv6. Agreed=20
> also: some transport layers that encrypt data are incompatible with=20
> port mapping. But this is not sufficient to abandon port mapping=20
> all-over. (See the comment on 5.1.2.)
>=20
> Sec 8 - Security Considerations
> - In TCP, DCCP, SCTP, packets that initiate connection establishments  =
can be individually recognized (SYN without ack in the case of TCP). =
Incoming connections  can therefore be blocked with stateless operation, =
but this is not the case for UDP (per-connection stateful operation is =
needed). Whether blocking UDP incoming connections is worth it, in =
global to local IPv6 gateways, is  therefore uncertain (hosts must =
anyway have their own blocking of undesirable incoming connections). =20
>=20
> In summary:=20
> - the document  introduces IMO a *very useful subject*.=20
> - Before freezing any recommendation,  its relationship with other =
layers, in particular with other stateless address mappings, should be =
further studied. =20
>=20
> Best regards,
>=20
> RD
>=20
>=20
> Margaret Wasserman   (1-12/1-31/200x) 10/27/08 7:59 PM: =20
>=20
>=20
> 	I have posted a NAT66 draft, so that we can have a better-grounded =
discussion of whether it makes sense to include NAT66 as a work item in =
the behave charter.  The draft can be found at the following URL:=20
> =09
> 	http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt
> =09
> 	Feedback would be greatly appreciated! =20
>=20
=20



From owner-v6ops@ops.ietf.org  Thu Nov  6 06:18:03 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D7FB93A6A24
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 06:18:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,
	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 SYPwVcFKgDTP
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 06:18:03 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id EE2363A69DB
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 06:18:02 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Ky5dm-000LqN-62
	for v6ops-data@psg.com; Thu, 06 Nov 2008 14:15:18 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <iljitsch@muada.com>)
	id 1Ky5dc-000LoB-Ff
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 14:15:11 +0000
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.224])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id mA6EE7B9084534
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 6 Nov 2008 15:14:08 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Cc: <EricLKlein@softhome.net>, Margaret Wasserman <mrw@lilacglade.org>,
        v6ops@ops.ietf.org, Behave WG <behave@ietf.org>
Message-Id: <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Wes Beebee (wbeebee) <wbeebee@cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: [BEHAVE] Comments on the NAT66 draft
Date: Thu, 6 Nov 2008 15:14:37 +0100
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 6 nov 2008, at 14:59, Wes Beebee (wbeebee) wrote:

> As we move to IPv6, NAT44, NAT64, and NAT46 will eventually go  
> away.  The problem with helping NAT66 (even when that is not your  
> intent) is that once it catches on, it'll be in the Internet forever  
> and will never go away.

> "NATs necessary for IPv6, says IETF chair"
> http://www.networkworld.com/news/2008/072109-nat-housley-qna.html

> Once NAT66 gets out, I can imagine even more damaging headlines  
> (which conveniently miss all the subtleties of the message in  
> section 3 of http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt) 
> : "IETF Standardizes IPv6-to-IPv6 NAT".

Well, if that's what we want to avoid, we shouldn't be coy and come  
out and say that IPv6 NAT won't be accommodated in IETF protocols.

What seems to be happening today is that we all look the other way and  
pretend the issue doesn't exist, because we either assume that of  
course there won't be any IPv6 NAT or of course there will. So we are  
on our way ending up with the same situation that we encountered with  
IPv4: suddenly, it's no longer realistically possible to deploy a  
protocol that isn't NAT-friendly, but there are so many different NATs  
that it's impossible to be friendly to them all, and many of them  
operate is very suboptimal ways that could have been avoided with some  
forethought.



From owner-v6ops@ops.ietf.org  Thu Nov  6 06:41:45 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3E7B3A6859
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 06:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.927
X-Spam-Level: 
X-Spam-Status: No, score=-4.927 tagged_above=-999 required=5
	tests=[AWL=-0.432, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 2lWqXkj16qTI
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 06:41:44 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 9C4CE3A69DB
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 06:41:44 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Ky62Y-000OOR-Ac
	for v6ops-data@psg.com; Thu, 06 Nov 2008 14:40:54 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <wbeebee@cisco.com>)
	id 1Ky62G-000OMm-N0
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 14:40:48 +0000
X-IronPort-AV: E=Sophos;i="4.33,557,1220227200"; 
   d="scan'208";a="26964343"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
  by rtp-iport-1.cisco.com with ESMTP; 06 Nov 2008 14:40:35 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mA6EeZIj004355;
	Thu, 6 Nov 2008 09:40:35 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mA6EeZ9l028903;
	Thu, 6 Nov 2008 14:40:35 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 6 Nov 2008 09:40:35 -0500
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
Subject: RE: [BEHAVE] Comments on the NAT66 draft
Date: Thu, 6 Nov 2008 09:40:34 -0500
Message-ID: <BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] Comments on the NAT66 draft
Thread-Index: AclAGgz79fW18UBCTqKrZp2m6NqlAgAAbK4Q
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <EricLKlein@softhome.net>, "Margaret Wasserman" <mrw@lilacglade.org>,
        <v6ops@ops.ietf.org>, "Behave WG" <behave@ietf.org>
X-OriginalArrivalTime: 06 Nov 2008 14:40:35.0633 (UTC) FILETIME=[A1030A10:01C9401D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2302; t=1225982435; x=1226846435;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co
	m>
	|Subject:=20RE=3A=20[BEHAVE]=20Comments=20on=20the=20NAT66=
	20draft
	|Sender:=20
	|To:=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com
	>;
	bh=gc+JkGMfhD1OxstrOS4B4Li/msSkUDkuM1AHDkjhWak=;
	b=JYHmmE5G8/Qk+oLuBf/DlFVpgiZaSj2ilbpz68rvlSvG/acaJgqduhX64U
	f7PwDC1/+8MafmbIsSlmT2+4UI8zFvfCyWNdjklxZVxc1FYuimI5oKoFSPaE
	WyeGI8EdQm;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

I guess RFC 4864 doesn't go quite far enough - it says (paraphrasing):=20
You shouldn't need NAT66 because there are other ways to accomplish your
goals which may be existing or under development at IETF. =20

Are we prepared to make a stronger statement here?  Are we prepared to
say:=20
If you use NAT66, then be prepared for interoperability problems with
IETF specifications because we WILL NOT design around your box, and,
furthermore, that all the reasons you would want such a box have been
fully accomodated through other means which are all in a good enough
state for you to deploy today.

- Wes

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]=20
Sent: Thursday, November 06, 2008 9:15 AM
To: Wes Beebee (wbeebee)
Cc: EricLKlein@softhome.net; Margaret Wasserman; v6ops@ops.ietf.org;
Behave WG
Subject: Re: [BEHAVE] Comments on the NAT66 draft

On 6 nov 2008, at 14:59, Wes Beebee (wbeebee) wrote:

> As we move to IPv6, NAT44, NAT64, and NAT46 will eventually go away. =20
> The problem with helping NAT66 (even when that is not your
> intent) is that once it catches on, it'll be in the Internet forever=20
> and will never go away.

> "NATs necessary for IPv6, says IETF chair"
> http://www.networkworld.com/news/2008/072109-nat-housley-qna.html

> Once NAT66 gets out, I can imagine even more damaging headlines (which

> conveniently miss all the subtleties of the message in section 3 of=20
> http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt)
> : "IETF Standardizes IPv6-to-IPv6 NAT".

Well, if that's what we want to avoid, we shouldn't be coy and come out
and say that IPv6 NAT won't be accommodated in IETF protocols.

What seems to be happening today is that we all look the other way and
pretend the issue doesn't exist, because we either assume that of course
there won't be any IPv6 NAT or of course there will. So we are on our
way ending up with the same situation that we encountered with
IPv4: suddenly, it's no longer realistically possible to deploy a
protocol that isn't NAT-friendly, but there are so many different NATs
that it's impossible to be friendly to them all, and many of them
operate is very suboptimal ways that could have been avoided with some
forethought.



From owner-v6ops@ops.ietf.org  Thu Nov  6 06:41:57 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEE7A3A6A0A
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 06:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.507
X-Spam-Level: 
X-Spam-Status: No, score=0.507 tagged_above=-999 required=5 tests=[AWL=-1.153,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3,
	MIME_HTML_ONLY=1.457, 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 7oYMCdKDT186
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 06:41:53 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 4A0DC3A6850
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 06:41:53 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Ky61p-000OLP-Rg
	for v6ops-data@psg.com; Thu, 06 Nov 2008 14:40:09 +0000
Received: from [212.27.42.27] (helo=smtp1-g19.free.fr)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <remi.despres@free.fr>)
	id 1Ky61h-000OJc-Lt
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 14:40:05 +0000
Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp1-g19.free.fr (Postfix) with ESMTP id BD2441AB2DC;
	Thu,  6 Nov 2008 15:40:00 +0100 (CET)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp1-g19.free.fr (Postfix) with ESMTP id 5622A1AB31C;
	Thu,  6 Nov 2008 15:39:58 +0100 (CET)
Message-ID: <49130161.9010902@free.fr>
Date: Thu, 06 Nov 2008 15:38:25 +0100
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
CC: EricLKlein@softhome.net, Margaret Wasserman <mrw@lilacglade.org>, 
 Behave WG <behave@ietf.org>,
 v6ops@ops.ietf.org
Subject: Re: Comments on the NAT66 draft
References: <4911B9E7.8090108@free.fr>            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Wes Beebee (wbeebee)&nbsp;&nbsp; (1-12/1-31/200x) 11/6/08 2:59 PM:
<blockquote
 cite="mid:BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com"
 type="cite">
  <pre wrap="">As we move to IPv6, NAT44, NAT64, and NAT46 will eventually go away.  The problem with helping NAT66 (even when that is not your intent) is that once it catches on, it'll be in the Internet forever and will never go away.

"NATs necessary for IPv6, says IETF chair"
<a class="moz-txt-link-freetext" href="http://www.networkworld.com/news/2008/072109-nat-housley-qna.html">http://www.networkworld.com/news/2008/072109-nat-housley-qna.html</a>
  </pre>
</blockquote>
There will indeed be NAT64s, and possibly NAT46s: they are necessary to
satisfy some specific requirements. This justifies the chair's message.<br>
<br>
But this does not imply that NAT66s are ALSO necessary: provided
appropriate mapping based solutions are
deployed for v6-v6, there are only negative effects to be expected from
real NAT66s.<br>
<blockquote
 cite="mid:BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com"
 type="cite">
  <pre wrap="">Once NAT66 gets out, I can imagine even more damaging headlines (which conveniently miss all the subtleties of the message in section 3 of <a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt">http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt</a>): "IETF Standardizes IPv6-to-IPv6 NAT".
  </pre>
</blockquote>
This is precisely what can be avoided by using a more appropriate
terminology: in Margaret's document, "mapping" appears 46 times;&nbsp;
"translation"&nbsp;
appears 4 times (3 times to define NAT66, and 1 time where mapping
could have&nbsp; been used as well).<br>
<br>
Regards,<br>
RD
<blockquote
 cite="mid:BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com"
 type="cite">
  <pre wrap="">
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:EricLKlein@softhome.net">EricLKlein@softhome.net</a> [<a class="moz-txt-link-freetext" href="mailto:EricLKlein@softhome.net">mailto:EricLKlein@softhome.net</a>] 
Sent: Thursday, November 06, 2008 5:59 AM
To: Wes Beebee (wbeebee)
Cc: R&eacute;mi Despr&eacute;s; Margaret Wasserman; Behave WG; <a class="moz-txt-link-abbreviated" href="mailto:v6ops@ops.ietf.org">v6ops@ops.ietf.org</a>
Subject: Re: Comments on the NAT66 draft

Personally I am scared of anything that seems to make NAT suggestions for v6. 

That said, I think that section 3 could use a little more meat to explain some of the problems with NAT in terms of breaking connections etc rather than just pointing towards RFC 4864 as I am not sure that people will go and look at the cross reference. 

I would encourage discussion on this to see if there is a consensus for proceeding with giving hints or help to a concept that "IETF does not recommend" 

Eric 


Wes Beebee (wbeebee) writes: 

  </pre>
  <blockquote type="cite">
    <pre wrap="">I understand that NAT66 work on the details is being done in the BEHAVE Working Group - but shouldn't we also include a discussion at v6ops on whether NAT66 should be standardized?  After all, they're more privy to the discussions that created the Local Network Protection RFC...
 
- Wes

________________________________

From: <a class="moz-txt-link-abbreviated" href="mailto:behave-bounces@ietf.org">behave-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:behave-bounces@ietf.org">mailto:behave-bounces@ietf.org</a>] On 
Behalf Of R&eacute;mi Despr&eacute;s
Sent: Wednesday, November 05, 2008 10:21 AM
To: Margaret Wasserman
Cc: Behave WG
Subject: [BEHAVE] Comments on the NAT66 draft


Hi Margaret,

Sorry for so late an answer (I was too busy preparing my own draft before the deadline). 
Here are my comments, section per section.  

Sec. 3 - Motivation)
a. I _FULLY SUPPORT_ that IETF should standardize some ways to keep, in IPv6, appreciated benefits of NAT44s (and to avoid as much as possible their drawbacks). 
b. In your list of NAT44 appreciated services (i.e. provider independent addressing, simplified site multihoming, topology hiding), "host privacy" should IMHO be added. This is the impossibility, from the outside, to see that several consecutive connections were initiated by the same host. 
c. Concerning multihoming, a more detailed analysis of what NATs do, 
and don't do, would be a useful clarification. (In particular, they  
are incompatible with multihoming of both Shim6 and SCTP. These the 
protocols, to take advantage of multihoming, exchange address 
information in payloads, protected by strong checksums.)

Sec. 4 - NAT66 overview
a. Since your proposed mechanism is only based on stateless and reversible  _mappings_, calling it a NAT leads, IMHO, to confusion: NATs are generally understood, and used, as NAPTs. They do  stateful and  non-reversible 1:n  _translations_. 
b. With a different name than NAT for such a proposal, IETF could advertise that it _does not endorse NATs in IPv6_. This would IMHO increase  (or restore?) confidence in IPv6. "Mapping" instead of "translation"would be a logical word in such a name. 

Sec. 5 - NAT66 Address Mapping Mechanisms
- Topology hiding is in fact possible without losing reversibility of the mapping. Cf the comment on 5.1.2.  

Sec. 5.1 - Checksum-Neutral Mapping
- IMHO, it would be useful to make it clear in this section (like in the introduction) that the proposed mapping does not apply to addresses that are transmitted in payloads.  ALGs could be be added to convert addresses in TCP payloads TCP, as it is done in some NAT44s.  But it cannot be done not in SCTP payloads because of the stronger checksum algorithm.  

Sec. 5.1.1 - Two-way Algorithmic Address Mapping
- The proposed limitation to /48 internal and external prefixes is stronger than necessary. 
- A sufficient limitation is that external prefixes are not longer than internal ones. (If  the external prefix is shorter, a few 0 bits can be added to it, up to the  length to the internal one.) For example a /56 external with a /60 internal should be permitted.  

Sec. 5.1.2 - Topology hiding Option
- For outgoing UDP and TCP connections, it is in fact possible to hide the internal topology without losing  reversibility of the mapping:  the algorithmic mapping is, for this, applied jointly to the subnet identifier AND to port bits (excluding port-bits 0 and 1 that must remain constant in dynamic ports). UDP and TCP checksums are then incrementally adjusted (like IP checksums). 
- In addition to topology hiding, this mechanism provides _host privacy_ , as defined in the comment on sec. 3 :-) .  

Sec 6. - Prefixes for Port Mapping
- I don't see the need for this section in this document. The mapping applies to internal and external  prefixes, independently of how they can be configured.  

Sec 7 - A note on Port Mapping
- Agreed: address amplification should not be needed in IPv6. Agreed 
also: some transport layers that encrypt data are incompatible with 
port mapping. But this is not sufficient to abandon port mapping 
all-over. (See the comment on 5.1.2.)

Sec 8 - Security Considerations
- In TCP, DCCP, SCTP, packets that initiate connection establishments  can be individually recognized (SYN without ack in the case of TCP). Incoming connections  can therefore be blocked with stateless operation, but this is not the case for UDP (per-connection stateful operation is needed). Whether blocking UDP incoming connections is worth it, in global to local IPv6 gateways, is  therefore uncertain (hosts must anyway have their own blocking of undesirable incoming connections).  

In summary: 
- the document  introduces IMO a *very useful subject*. 
- Before freezing any recommendation,  its relationship with other layers, in particular with other stateless address mappings, should be further studied.  

Best regards,

RD


Margaret Wasserman   (1-12/1-31/200x) 10/27/08 7:59 PM:  


	I have posted a NAT66 draft, so that we can have a better-grounded discussion of whether it makes sense to include NAT66 as a work item in the behave charter.  The draft can be found at the following URL: 
	
	<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt">http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt</a>
	
	Feedback would be greatly appreciated!  

    </pre>
  </blockquote>
  <pre wrap=""><!----> 


  </pre>
</blockquote>
<br>
</body>
</html>



From owner-v6ops@ops.ietf.org  Thu Nov  6 12:29:47 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A51B3A696C
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 12:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.522
X-Spam-Level: 
X-Spam-Status: No, score=-1.522 tagged_above=-999 required=5
	tests=[AWL=-1.027, 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 YIpPzlTYnI97
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 12:29:46 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E9A133A6950
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 12:29:45 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyBPS-0001ZA-CS
	for v6ops-data@psg.com; Thu, 06 Nov 2008 20:24:54 +0000
Received: from [209.85.198.227] (helo=rv-out-0506.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <brian.e.carpenter@gmail.com>)
	id 1KyBPN-0001YL-8L
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 20:24:51 +0000
Received: by rv-out-0506.google.com with SMTP id b25so821653rvf.41
        for <v6ops@ops.ietf.org>; Thu, 06 Nov 2008 12:24:47 -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=INKZ54TssTW8boE+JDb9n/z08NIG69HqXyZizfodwk8=;
        b=t78Z4E0CpcnUgH8MYwWJ8Zm4sGiX8kGb7a4WGrntnQOTZohYUFQ4fYCgmVQ7Rkg8uI
         VxN5nPfDBJRjp/xGPq0JJ5ZR1R5wdz4Tc7tL86Z5pkkv3x0GvghEKZ5cu/fCoE3k+A14
         uhnguY7gM9tiFuyrSKGZXddhs1s8DORvVypU8=
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=tAVBR2BeUwOgSvy84tpUGyXYKFQkN3L+bKYBEmQ7z9wCW5+G+48e5UwtxlIN5YM2PS
         /r1EHcbAaScZ+lZkHFNqkqr863X+wa04DQMhnAWjwj9V8MSQFRrvAKBg92M6xemKxjXP
         LF7BPy07m5sLWwwlrvQqvkc84fyZRctoo32G4=
Received: by 10.141.76.21 with SMTP id d21mr1442953rvl.154.1226003087632;
        Thu, 06 Nov 2008 12:24:47 -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 l31sm5584780rvb.2.2008.11.06.12.24.45
        (version=SSLv3 cipher=RC4-MD5);
        Thu, 06 Nov 2008 12:24:47 -0800 (PST)
Message-ID: <4913528C.2000207@gmail.com>
Date: Fri, 07 Nov 2008 09:24:44 +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: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, 
 Margaret Wasserman <mrw@lilacglade.org>,
  v6ops@ops.ietf.org, Behave WG <behave@ietf.org>, 
 EricLKlein@softhome.net
Subject: Re: [BEHAVE] Comments on the NAT66 draft
References: <4911B9E7.8090108@free.fr>	<BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>	<courier.4912CE09.00003CB8@softhome.net>	<BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>	<6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Wes,

On 2008-11-07 03:40, Wes Beebee (wbeebee) wrote:
> I guess RFC 4864 doesn't go quite far enough - it says (paraphrasing): 
> You shouldn't need NAT66 because there are other ways to accomplish your
> goals which may be existing or under development at IETF.  

And the weakness in that is that although we have the gap analysis
in 4864, we do *not* have an adequate work plan to fill those gaps.
(ADs: I hope you are reading this.) Until we do, the emperor is
missing a few vital items of clothing.

> 
> Are we prepared to make a stronger statement here?  Are we prepared to
> say: 
> If you use NAT66, then be prepared for interoperability problems with
> IETF specifications because we WILL NOT design around your box, and,
> furthermore, that all the reasons you would want such a box have been
> fully accomodated through other means which are all in a good enough
> state for you to deploy today.

I think it's unrealistic to say that. We can put strong health warnings
in the draft, but we can't assert that other means exist for everything
until that becomes true (see above). We know very well that we can't
make that 'WILL NOT' assertion, because that isn't how our industry,
or the IETF, works. I'm unhappy about this but we have to be realistic.

MAT66 works for me because it makes it clear that this is not NAPT66.

   Brian

> 
> - Wes
> 
> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com] 
> Sent: Thursday, November 06, 2008 9:15 AM
> To: Wes Beebee (wbeebee)
> Cc: EricLKlein@softhome.net; Margaret Wasserman; v6ops@ops.ietf.org;
> Behave WG
> Subject: Re: [BEHAVE] Comments on the NAT66 draft
> 
> On 6 nov 2008, at 14:59, Wes Beebee (wbeebee) wrote:
> 
>> As we move to IPv6, NAT44, NAT64, and NAT46 will eventually go away.  
>> The problem with helping NAT66 (even when that is not your
>> intent) is that once it catches on, it'll be in the Internet forever 
>> and will never go away.
> 
>> "NATs necessary for IPv6, says IETF chair"
>> http://www.networkworld.com/news/2008/072109-nat-housley-qna.html
> 
>> Once NAT66 gets out, I can imagine even more damaging headlines (which
> 
>> conveniently miss all the subtleties of the message in section 3 of 
>> http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt)
>> : "IETF Standardizes IPv6-to-IPv6 NAT".
> 
> Well, if that's what we want to avoid, we shouldn't be coy and come out
> and say that IPv6 NAT won't be accommodated in IETF protocols.
> 
> What seems to be happening today is that we all look the other way and
> pretend the issue doesn't exist, because we either assume that of course
> there won't be any IPv6 NAT or of course there will. So we are on our
> way ending up with the same situation that we encountered with
> IPv4: suddenly, it's no longer realistically possible to deploy a
> protocol that isn't NAT-friendly, but there are so many different NATs
> that it's impossible to be friendly to them all, and many of them
> operate is very suboptimal ways that could have been avoided with some
> forethought.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 



From owner-v6ops@ops.ietf.org  Thu Nov  6 12:40:29 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D01C23A6AAA
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu,  6 Nov 2008 12:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.067
X-Spam-Level: 
X-Spam-Status: No, score=-1.067 tagged_above=-999 required=5
	tests=[AWL=-1.564, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_13=0.6,
	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 TnstrmP5AGoS
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu,  6 Nov 2008 12:40:28 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 755CB3A696C
	for <v6ops-archive@lists.ietf.org>; Thu,  6 Nov 2008 12:40:28 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyBdL-0002T0-At
	for v6ops-data@psg.com; Thu, 06 Nov 2008 20:39:15 +0000
Received: from [69.33.111.75] (helo=sirocco.sandstorm.net)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <mrw@lilacglade.org>)
	id 1KyBdD-0002SF-FW
	for v6ops@ops.ietf.org; Thu, 06 Nov 2008 20:39:11 +0000
Received: from [10.2.0.63] (ip-69-33-111-74.bos.megapath.net [69.33.111.74])
	(authenticated bits=0)
	by sirocco.sandstorm.net (8.13.8/8.13.3) with ESMTP id mA6Kc2j6030333
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 6 Nov 2008 15:38:05 -0500 (EST)
	(envelope-from mrw@lilacglade.org)
Cc: IPv6 Operations <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Message-Id: <4ECF9F45-314E-4877-BB75-6D9EAB87B970@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Wes Beebee (wbeebee) <wbeebee@cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: [BEHAVE] Comments on the NAT66 draft
Date: Thu, 6 Nov 2008 15:38:02 -0500
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


Hi Wes,

Hosting this discussion on the behave WG mailing list is certainly not =20=

an attempt to avoid folks in v6ops having feedback on the work, it is =20=

just that behave seems like the right place to work on the actual =20
specification.  With all of the v4v6 translation discussion happening =20=

in behave, I think we've been hoping that the v6 folks will show up in =20=

behave and have this discussion, and do this work, there.

I'm sure that the v6ops chairs are aware of this work -- my co-author =20=

Fred Baker is one of them.  If they think that it would be useful to =20
discuss NAT66 in v6ops, I'd certainly be happy to come to the v6ops =20
meeting and talk about it.

Personally, though, I'd rather that we discuss this in one forum =20
(behave) and that interested people bring their thoughts, opinions and =20=

feedback to that forum.

Margaret


On Nov 5, 2008, at 11:31 AM, Wes Beebee (wbeebee) wrote:

> I understand that NAT66 work on the details is being done in the =20
> BEHAVE Working Group - but shouldn't we also include a discussion at =20=

> v6ops on whether NAT66 should be standardized?  After all, they're =20
> more privy to the discussions that created the Local Network =20
> Protection RFC...
>
> - Wes
>
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On =20
> Behalf Of R=E9mi Despr=E9s
> Sent: Wednesday, November 05, 2008 10:21 AM
> To: Margaret Wasserman
> Cc: Behave WG
> Subject: [BEHAVE] Comments on the NAT66 draft
>
> Hi Margaret,
>
> Sorry for so late an answer (I was too busy preparing my own draft =20
> before the deadline).
> Here are my comments, section per section.
>
> Sec. 3 - Motivation)
> a. I _FULLY SUPPORT_ that IETF should standardize some ways to keep, =20=

> in IPv6, appreciated benefits of NAT44s (and to avoid as much as =20
> possible their drawbacks).
> b. In your list of NAT44 appreciated services (i.e. provider =20
> independent addressing, simplified site multihoming, topology =20
> hiding), "host privacy" should IMHO be added. This is the =20
> impossibility, from the outside, to see that several consecutive =20
> connections were initiated by the same host.
> c. Concerning multihoming, a more detailed analysis of what NATs do, =20=

> and don't do, would be a useful clarification. (In particular, they  =20=

> are incompatible with multihoming of both Shim6 and SCTP. These the =20=

> protocols, to take advantage of multihoming, exchange address =20
> information in payloads, protected by strong checksums.)
>
> Sec. 4 - NAT66 overview
> a. Since your proposed mechanism is only based on stateless and =20
> reversible  _mappings_, calling it a NAT leads, IMHO, to confusion: =20=

> NATs are generally understood, and used, as NAPTs. They do  stateful =20=

> and  non-reversible 1:n  _translations_.
> b. With a different name than NAT for such a proposal, IETF could =20
> advertise that it _does not endorse NATs in IPv6_. This would IMHO =20
> increase  (or restore?) confidence in IPv6. "Mapping" instead of =20
> "translation"would be a logical word in such a name.
>
> Sec. 5 - NAT66 Address Mapping Mechanisms
> - Topology hiding is in fact possible without losing reversibility =20
> of the mapping. Cf the comment on 5.1.2.
>
> Sec. 5.1 - Checksum-Neutral Mapping
> - IMHO, it would be useful to make it clear in this section (like in =20=

> the introduction) that the proposed mapping does not apply to =20
> addresses that are transmitted in payloads.  ALGs could be be added =20=

> to convert addresses in TCP payloads TCP, as it is done in some =20
> NAT44s.  But it cannot be done not in SCTP payloads because of the =20
> stronger checksum algorithm.
>
> Sec. 5.1.1 - Two-way Algorithmic Address Mapping
> - The proposed limitation to /48 internal and external prefixes is =20
> stronger than necessary.
> - A sufficient limitation is that external prefixes are not longer =20
> than internal ones. (If  the external prefix is shorter, a few 0 =20
> bits can be added to it, up to the  length to the internal one.) For =20=

> example a /56 external with a /60 internal should be permitted.
>
> Sec. 5.1.2 - Topology hiding Option
> - For outgoing UDP and TCP connections, it is in fact possible to =20
> hide the internal topology without losing  reversibility of the =20
> mapping:  the algorithmic mapping is, for this, applied jointly to =20
> the subnet identifier AND to port bits (excluding port-bits 0 and 1 =20=

> that must remain constant in dynamic ports). UDP and TCP checksums =20
> are then incrementally adjusted (like IP checksums).
> - In addition to topology hiding, this mechanism provides _host =20
> privacy_ , as defined in the comment on sec. 3 :-) .
>
> Sec 6. - Prefixes for Port Mapping
> - I don't see the need for this section in this document. The =20
> mapping applies to internal and external  prefixes, independently of =20=

> how they can be configured.
>
> Sec 7 - A note on Port Mapping
> - Agreed: address amplification should not be needed in IPv6. Agreed =20=

> also: some transport layers that encrypt data are incompatible with =20=

> port mapping. But this is not sufficient to abandon port mapping all-=20=

> over. (See the comment on 5.1.2.)
>
> Sec 8 - Security Considerations
> - In TCP, DCCP, SCTP, packets that initiate connection =20
> establishments  can be individually recognized (SYN without ack in =20
> the case of TCP). Incoming connections  can therefore be blocked =20
> with stateless operation, but this is not the case for UDP (per-=20
> connection stateful operation is needed). Whether blocking UDP =20
> incoming connections is worth it, in global to local IPv6 gateways, =20=

> is  therefore uncertain (hosts must anyway have their own blocking =20
> of undesirable incoming connections).
>
> In summary:
> - the document  introduces IMO a *very useful subject*.
> - Before freezing any recommendation,  its relationship with other =20
> layers, in particular with other stateless address mappings, should =20=

> be further studied.
>
> Best regards,
>
> RD
>
>
> Margaret Wasserman   (1-12/1-31/200x) 10/27/08 7:59 PM:
>> I have posted a NAT66 draft, so that we can have a better-grounded =20=

>> discussion of whether it makes sense to include NAT66 as a work =20
>> item in the behave charter.  The draft can be found at the =20
>> following URL:
>>
>> http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt
>>
>> Feedback would be greatly appreciated!




From owner-v6ops@ops.ietf.org  Fri Nov  7 07:57:52 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 107DB28C12A
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 07:57:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.899
X-Spam-Level: 
X-Spam-Status: No, score=0.899 tagged_above=-999 required=5 tests=[AWL=-1.401,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457,
	RDNS_NONE=0.1, SARE_LWSHORTT=1.24]
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 OedssLpXBjeO
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 07:57:51 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 13DDE28C118
	for <v6ops-archive@lists.ietf.org>; Fri,  7 Nov 2008 07:57:51 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyTc7-000Hrs-8J
	for v6ops-data@psg.com; Fri, 07 Nov 2008 15:51:11 +0000
Received: from [212.27.42.64] (helo=smtp7-g19.free.fr)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <remi.despres@free.fr>)
	id 1KyTc1-000Hqn-ES
	for v6ops@ops.ietf.org; Fri, 07 Nov 2008 15:51:08 +0000
Received: from smtp7-g19.free.fr (localhost [127.0.0.1])
	by smtp7-g19.free.fr (Postfix) with ESMTP id A910FB0144;
	Fri,  7 Nov 2008 16:51:04 +0100 (CET)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp7-g19.free.fr (Postfix) with ESMTP id 9E1EFB0134;
	Fri,  7 Nov 2008 16:51:03 +0100 (CET)
Message-ID: <4914638A.80301@free.fr>
Date: Fri, 07 Nov 2008 16:49:30 +0100
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, 
 Margaret Wasserman <mrw@lilacglade.org>,
 v6ops@ops.ietf.org, Behave WG <behave@ietf.org>, 
 EricLKlein@softhome.net
Subject: Re: [BEHAVE] Comments on the NAT66 draft
References: <4911B9E7.8090108@free.fr>	<BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>	<courier.4912CE09.00003CB8@softhome.net>	<BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>	<6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>	<BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com> <4913528C.2000207@gmail.com>
In-Reply-To: <4913528C.2000207@gmail.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Brian E Carpenter&nbsp;&nbsp; (1-12/1-31/200x) 11/6/08 9:24 PM:
<blockquote cite="mid:4913528C.2000207@gmail.com" type="cite">
  <pre wrap="">Wes,

On 2008-11-07 03:40, Wes Beebee (wbeebee) wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I guess RFC 4864 doesn't go quite far enough - it says (paraphrasing): 
You shouldn't need NAT66 because there are other ways to accomplish your
goals which may be existing or under development at IETF.  
    </pre>
  </blockquote>
  <pre wrap=""><!---->
And the weakness in that is that although we have the gap analysis
in 4864, we do *not* have an adequate work plan to fill those gaps.
(ADs: I hope you are reading this.) Until we do, the emperor is
missing a few vital items of clothing.
  </pre>
</blockquote>
Full agreement on the need for a short term gap filling plan.<br>
<br>
IMHO, a combination of the best of my SAM proposal, of Margaret's NAT66
proposal (renamed to avoid the word NAT, I hope), and of DHCP based
port range assignments of Boucadair's and Bajko's drafts, could be an
adequate gap filling solution.<br>
<br>
Regards,<br>
<br>
RD<br>
<br>
<br>
<br>
</body>
</html>



From owner-v6ops@ops.ietf.org  Fri Nov  7 07:57:55 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F4C73A6941
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 07:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.076
X-Spam-Level: 
X-Spam-Status: No, score=-0.076 tagged_above=-999 required=5
	tests=[AWL=-0.278, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3,
	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 Ybcmtp8ogpaX
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 07:57:55 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C58563A67AA
	for <v6ops-archive@lists.ietf.org>; Fri,  7 Nov 2008 07:57:54 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyThG-000ITz-3g
	for v6ops-data@psg.com; Fri, 07 Nov 2008 15:56:30 +0000
Received: from [212.27.42.27] (helo=smtp1-g19.free.fr)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <remi.despres@free.fr>)
	id 1KyThA-000IT9-AG
	for v6ops@ops.ietf.org; Fri, 07 Nov 2008 15:56:26 +0000
Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp1-g19.free.fr (Postfix) with ESMTP id 8F5A51AB2E6;
	Fri,  7 Nov 2008 16:56:23 +0100 (CET)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp1-g19.free.fr (Postfix) with ESMTP id 0D5A91AB351;
	Fri,  7 Nov 2008 16:56:22 +0100 (CET)
Message-ID: <491464CA.8080303@free.fr>
Date: Fri, 07 Nov 2008 16:54:50 +0100
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
CC: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, 
 IPv6 Operations <v6ops@ops.ietf.org>,
 Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on the NAT66 draft
References: <4911B9E7.8090108@free.fr>	<BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <4ECF9F45-314E-4877-BB75-6D9EAB87B970@lilacglade.org>
In-Reply-To: <4ECF9F45-314E-4877-BB75-6D9EAB87B970@lilacglade.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Margaret Wasserman   (1-12/1-31/200x) 11/6/08 9:38 PM:
> Hosting this discussion on the behave WG mailing list is certainly not 
> an attempt to avoid folks in v6ops having feedback on the work, it is 
> just that behave seems like the right place to work on the actual 
> specification.  With all of the v4v6 translation discussion happening 
> in behave, I think we've been hoping that the v6 folks will show up in 
> behave and have this discussion, and do this work, there.

> Personally, though, I'd rather that we discuss this in one forum 
> (behave) and that interested people bring their thoughts, opinions and 
> feedback to that forum.
Same opinion.
RD



From owner-v6ops@ops.ietf.org  Fri Nov  7 09:52:05 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F39233A69BF
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 09:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.53
X-Spam-Level: 
X-Spam-Status: No, score=-105.53 tagged_above=-999 required=5
	tests=[AWL=-1.035, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 HbVfyXaQgQal
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 09:52:04 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 187503A696D
	for <v6ops-archive@lists.ietf.org>; Fri,  7 Nov 2008 09:52:04 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyVPw-0004ul-KB
	for v6ops-data@psg.com; Fri, 07 Nov 2008 17:46:44 +0000
Received: from [171.71.176.71] (helo=sj-iport-2.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1KyVPq-0004tT-Qz
	for v6ops@ops.ietf.org; Fri, 07 Nov 2008 17:46:41 +0000
X-IronPort-AV: E=Sophos;i="4.33,565,1220227200"; 
   d="scan'208";a="102809665"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
  by sj-iport-2.cisco.com with ESMTP; 07 Nov 2008 17:46:38 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id mA7Hka2k019317
	for <v6ops@ops.ietf.org>; Fri, 7 Nov 2008 09:46:36 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mA7HkZaS002182
	for <v6ops@ops.ietf.org>; Fri, 7 Nov 2008 17:46:36 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 7 Nov 2008 09:46:35 -0800
Received: from stealth-10-32-244-221.cisco.com ([10.32.244.221]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 7 Nov 2008 09:46:34 -0800
Message-Id: <CA240954-81B7-4B49-9BFC-4F82930A33E5@cisco.com>
From: Fred Baker <fred@cisco.com>
To: IPv6 Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Fwd: Posting of IPR Disclosure
Date: Fri, 7 Nov 2008 09:46:34 -0800
References: <20081107164012.3459028C17C@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 07 Nov 2008 17:46:34.0927 (UTC) FILETIME=[C6E1EBF0:01C94100]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1001; t=1226079996; x=1226943996;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Fwd=3A=20Posting=20of=20IPR=20Disclosure
	|Sender:=20;
	bh=2HEH+byUsTcvVpTvf9Pnv3urYuR7D/EelycXDVF8e4w=;
	b=LTCSmoe3dVInwUbzQTreZk5jjHLH38DbCKjD96XLPrCWi/874F1bc3gWxB
	GT8Pe+0OKdsKZPljLCKT+7ehFQuGs5SKf32tuv1qOAF+AQUCYN9KNNTcuMt9
	Nm7Jrv0afM;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>



Begin forwarded message:

> From: IETF Secretariat <ietf-ipr@ietf.org>
> Date: November 7, 2008 8:40:12 AM PST
> To: fred.baker@cisco.com
> Cc: dromasca@avaya.com, rbonica@juniper.net, fred.baker@cisco.com, kurtis@kurtis.pp.se
> Subject: Posting of IPR Disclosure
>
> Dear Fred Baker:
>
> An IPR disclosure that pertains to your RFC entitled "Procedures for  
> Renumbering
> an IPv6 Network without a Flag Day" (RFC4192) was submitted to the  
> IETF
> Secretariat on 2008-11-05 and has been posted on the "IETF Page of  
> Intellectual
> Property Rights Disclosures" (https://datatracker.ietf.org/public/ipr_list.cgi 
> ).
> The title of the IPR disclosure is "Comcast IP Holdings I, LLC's  
> Statement about
> IPR related to RFC 3953, RFC 4415, RFC 4759, RFC 4769, RFC 4002, RFC  
> 4355, RFC
> 4414, RFC 4725, RFC 4969, RFC 4979, RFC 5028, RFC 5278, RFC 5346,  
> RFC 5067, RFC
> 5076, RFC 5105, RFC 2168, RFC 3401, RFC 3402, RF...."
>
> The IETF Secretariat
>
>




From owner-v6ops@ops.ietf.org  Fri Nov  7 10:21:18 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18E843A68B8
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 10:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.958
X-Spam-Level: 
X-Spam-Status: No, score=-0.958 tagged_above=-999 required=5
	tests=[AWL=-0.521, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 niraIl-U-63X
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 10:21:17 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 3F8543A6B66
	for <v6ops-archive@lists.ietf.org>; Fri,  7 Nov 2008 10:21:17 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyVvG-0008Yk-Rw
	for v6ops-data@psg.com; Fri, 07 Nov 2008 18:19:06 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KyVvB-0008Y4-RB
	for v6ops@ops.ietf.org; Fri, 07 Nov 2008 18:19:04 +0000
Received: (qmail 15540 invoked by uid 417); 7 Nov 2008 18:18:51 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 7 Nov 2008 18:18:51 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Fri, 07 Nov 2008 11:18:51 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
In-Reply-To: <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> 
From: EricLKlein@softhome.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee =?iso-8859-1?Q?\=22(wbeebee)?=" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Fri, 07 Nov 2008 11:18:51 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.107.149]
Message-ID: <courier.4914868B.00003F53@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Iljitsch, 

This is why we have RFC 4864, and the comment that the IETF does not support 
NAT in IPv6. We need to find a way to make it crystal clear that NAT is not 
part of v6 and using it will be non-standard. 

And this is why I think this draft will cause more harm than good.
Eric 

Iljitsch van Beijnum writes:
> 
> Well, if that's what we want to avoid, we shouldn't be coy and come  out 
> and say that IPv6 NAT won't be accommodated in IETF protocols. 
> 
> What seems to be happening today is that we all look the other way and  
> pretend the issue doesn't exist, because we either assume that of  course 
> there won't be any IPv6 NAT or of course there will. So we are  on our way 
> ending up with the same situation that we encountered with  IPv4: 
> suddenly, it's no longer realistically possible to deploy a  protocol that 
> isn't NAT-friendly, but there are so many different NATs  that it's 
> impossible to be friendly to them all, and many of them  operate is very 
> suboptimal ways that could have been avoided with some  forethought.



From owner-v6ops@ops.ietf.org  Fri Nov  7 10:25:33 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 465A23A69BF
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 10:25:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.966
X-Spam-Level: 
X-Spam-Status: No, score=-0.966 tagged_above=-999 required=5
	tests=[AWL=-0.529, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 CkapcgooVCwk
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 10:25:32 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6A8BF3A68B8
	for <v6ops-archive@lists.ietf.org>; Fri,  7 Nov 2008 10:25:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyW0W-0008wy-8G
	for v6ops-data@psg.com; Fri, 07 Nov 2008 18:24:32 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KyW0Q-0008wR-U4
	for v6ops@ops.ietf.org; Fri, 07 Nov 2008 18:24:29 +0000
Received: (qmail 22305 invoked by uid 417); 7 Nov 2008 18:23:39 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 7 Nov 2008 18:23:39 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Fri, 07 Nov 2008 11:23:39 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com>
            <4913528C.2000207@gmail.com>
In-Reply-To: <4913528C.2000207@gmail.com> 
From: EricLKlein@softhome.net
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>,
  Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>
Subject: Re: Comments on the NAT66 draft
Date: Fri, 07 Nov 2008 11:23:39 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.107.149]
Message-ID: <courier.491487AB.000043EE@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Brian E Carpenter writes: 

> Wes, 
> 
> On 2008-11-07 03:40, Wes Beebee (wbeebee) wrote:
>> I guess RFC 4864 doesn't go quite far enough - it says (paraphrasing): 
>> You shouldn't need NAT66 because there are other ways to accomplish your
>> goals which may be existing or under development at IETF.  
> 
> And the weakness in that is that although we have the gap analysis
> in 4864, we do *not* have an adequate work plan to fill those gaps.
> (ADs: I hope you are reading this.) Until we do, the emperor is
> missing a few vital items of clothing. 
> 
>> 
>> Are we prepared to make a stronger statement here?  Are we prepared to
>> say: 
>> If you use NAT66, then be prepared for interoperability problems with
>> IETF specifications because we WILL NOT design around your box, and,
>> furthermore, that all the reasons you would want such a box have been
>> fully accomodated through other means which are all in a good enough
>> state for you to deploy today.
> 
> I think it's unrealistic to say that. We can put strong health warnings
> in the draft, but we can't assert that other means exist for everything
> until that becomes true (see above). We know very well that we can't
> make that 'WILL NOT' assertion, because that isn't how our industry,
> or the IETF, works. I'm unhappy about this but we have to be realistic. 
> 
> MAT66 works for me because it makes it clear that this is not NAPT66. 
> 
>    Brian

I agree with Brian, MAT would work as it breaks from the NAT mentality and 
may be more manageable in the future.
Eric



From compulso_2007@BlackBerry.net  Fri Nov  7 10:42:11 2008
Return-Path: <compulso_2007@BlackBerry.net>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4E2B3A6B63
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 10:42:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -57.811
X-Spam-Level: 
X-Spam-Status: No, score=-57.811 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_RELAY_NODNS=1.451,
	FM_FAKE_HELO_VERIZON=1.229, HELO_DYNAMIC_IPADDR=2.426,
	HELO_EQ_VERIZON_POOL=1.495, HELO_MISMATCH_NET=0.611,
	HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	URIBL_BLACK=20, 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 7wJs0ya8n5IK
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 10:42:11 -0800 (PST)
Received: from pool-70-23-80-80.ny325.east.verizon.net (unknown [70.23.80.80])
	by core3.amsl.com (Postfix) with ESMTP id B07773A68A0
	for <v6ops-archive@ietf.org>; Fri,  7 Nov 2008 10:42:09 -0800 (PST)
Message-ID: <31636588.2634758053417.JavaMail.root@D04FFE399B9>
From: "Sensation news" <compulso_2007@BlackBerry.net>
To: v6ops-archive@ietf.org
Subject: Dream to be an upsized guy?
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_000E_01C940DE.97106040"
Date: Fri, 7 Nov 2008 13:41:51 -0500

------=_NextPart_000_000E_01C940DE.97106040
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit

<html>
<head>
<title>Guayaba Productions Corporation</title>

</head>
<body bgcolor="#FFFFFF" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
<p align="center"><FONT SIZE="1" COLOR="#000000" FACE="ARIAL">If you are unable to see the message below, <A href="http://pkob.onraobz.cn/">click here to view</A>.<br>
</FONT><font face="ARIAL" color="#808080" size="2"><br>
</font></CENTER>
</p>
<div align="center">
  <table border="0" width="600" cellspacing="0" cellpadding="0">
    <tr>
      <td>
      <p align="center"><a href="http://che.onraobz.cn/"><img border="0" src="http://dphvonr.onraobz.cn/widget2.jpg"></a></td>
    </tr>
  </table>
</div>
<table width="555" border="0" align="center" cellpadding="10" cellspacing="0">
  <tr>
    <td align="center" class="gray">
      <p> <font size="-1" color="#999999" face="Arial, Helvetica, sans-serif">You have received this message because you opted in to receives Guayaba Productions Corporation pecial <br>
        offers via email. Login to your member account to</font> <font size="-2" face="Arial, Helvetica, sans-serif">
  <a href="http://uxxid.onraobz.cn/" >
  <font color="#999999" size="-1">edit your email subscription</font></a>
  <font color="#999999" size="-1">.</font><font color="#999999"><br>
        <font size="-1">Click here to</font>
  </font></font> <font size="-2" face="Arial, Helvetica, sans-serif">
  <a href="http://zyoq.onraobz.cn/optout.aspx?user=v6ops-archive@ietf.org" >
  <font color="#999999" size="-1">unsubscribe</font></a><font color="#999999" size="-1">.</font><br>
        <br>
        <font color="#999999" size="-1">PLEASE DO NOT REPLY - This is being sent
        from an unattended mailbox. <br>
      <p><font color="#999999" size="-1" face="Arial, Helvetica, sans-serif">Copyright &copy; 2008 Guayaba Productions Corporation, Inc. All rights reserved.<br>
        515 Suite L-6 Providence Highway, Dedham, MA 02026</font></p>
    </td>
  </tr>
</table>
</body>
</html>
------=_NextPart_000_000E_01C940DE.97106040--


From tianxiang-melany@barlows.co.za  Fri Nov  7 19:22:12 2008
Return-Path: <tianxiang-melany@barlows.co.za>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B3683A68F4
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 19:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -58.519
X-Spam-Level: 
X-Spam-Status: No, score=-58.519 tagged_above=-999 required=5
	tests=[BAYES_60=1, GB_I_LETTER=-2, HTML_EXTRA_CLOSE=2.809,
	HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_UNI=0.591,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083,
	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 bHR8wukBoE3k
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 19:22:11 -0800 (PST)
Received: from mail.brfp.com (mail.brfp.com [70.90.82.114])
	by core3.amsl.com (Postfix) with ESMTP id 6449A3A684D
	for <v6ops-archive@megatron.ietf.org>; Fri,  7 Nov 2008 19:22:10 -0800 (PST)
To: <v6ops-archive@megatron.ietf.org>
Subject: confirm please
From: <v6ops-archive@megatron.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081108032211.6449A3A684D@core3.amsl.com>
Date: Fri,  7 Nov 2008 19:22:10 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 </head>
        <html>
<body>
<tr>
		<td class=EC_container bgcolor="#F2F2F2">
			<table cellpadding=0 cellspacing=0 width="100%">
				<tr>
					<td>

                                                <div align=center> <a href="http://wrd.mightresponsibility.com" target="_blank"><img src="http://chv.mightresponsibility.com/3.gif" border=0 alt="Click Here!"></a> </div>
					                    </td>
				</tr>
				<tr>
					<td class=EC_legal>
					<strong>About this mailing: </strong><br>
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe
you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service
 advertised. Prices and item availability subject to change without notice.<br><br>

		?2008 Microsoft | <a href="http://www.mightresponsibility.com/" target="_blank">Unsubscribe</a> | <a href="http://jwhs.mightresponsibility.com" target="_blank">More Newsletters</a> | <a href="http://nnwom.mightresponsibility.com" target="_blank">Privacy</a><br><br>
		Microsoft Corporation, One Microsoft Way, Redmond, WA 98052



					</td>
				</tr>
			</table>
		</td>
	</tr>
</table>



        </div>
    </div>

          </div>

    </body>
</html>


From meriksir1959@barlows.co.za  Fri Nov  7 19:24:11 2008
Return-Path: <meriksir1959@barlows.co.za>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 554163A6921
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 19:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -38.519
X-Spam-Level: 
X-Spam-Status: No, score=-38.519 tagged_above=-999 required=5
	tests=[BAYES_60=1, GB_I_LETTER=-2, HTML_EXTRA_CLOSE=2.809,
	HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_UNI=0.591,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10,
	URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, 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 SXHRKlZ6MtUE
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 19:24:10 -0800 (PST)
Received: from mail.brfp.com (mail.brfp.com [70.90.82.114])
	by core3.amsl.com (Postfix) with ESMTP id 701583A68F4
	for <v6ops-archive@ietf.org>; Fri,  7 Nov 2008 19:24:10 -0800 (PST)
To: <v6ops-archive@ietf.org>
Subject: invoice
From: <v6ops-archive@ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081108032410.701583A68F4@core3.amsl.com>
Date: Fri,  7 Nov 2008 19:24:10 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 </head>
        <html>
<body>
<tr>
		<td class=EC_container bgcolor="#F2F2F2">
			<table cellpadding=0 cellspacing=0 width="100%">
				<tr>
					<td>

                                                <div align=center> <a href="http://eitll.singstring.com" target="_blank"><img src="http://knalpix.singstring.com/3.gif" border=0 alt="Click Here!"></a> </div>
					                    </td>
				</tr>
				<tr>
					<td class=EC_legal>
					<strong>About this mailing: </strong><br>
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe
you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service
 advertised. Prices and item availability subject to change without notice.<br><br>

		?2008 Microsoft | <a href="http://www.singstring.com/" target="_blank">Unsubscribe</a> | <a href="http://egszmi.singstring.com" target="_blank">More Newsletters</a> | <a href="http://mmb.singstring.com" target="_blank">Privacy</a><br><br>
		Microsoft Corporation, One Microsoft Way, Redmond, WA 98052



					</td>
				</tr>
			</table>
		</td>
	</tr>
</table>



        </div>
    </div>

          </div>

    </body>
</html>


From miniscri_1984@barlows.co.za  Fri Nov  7 19:25:30 2008
Return-Path: <miniscri_1984@barlows.co.za>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D5CB3A68F4
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri,  7 Nov 2008 19:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -57.519
X-Spam-Level: 
X-Spam-Status: No, score=-57.519 tagged_above=-999 required=5
	tests=[BAYES_80=2, GB_I_LETTER=-2, HTML_EXTRA_CLOSE=2.809,
	HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_UNI=0.591,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083,
	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 5vmh9lz2IIqL
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri,  7 Nov 2008 19:25:26 -0800 (PST)
Received: from mail.brfp.com (mail.brfp.com [70.90.82.114])
	by core3.amsl.com (Postfix) with ESMTP id 0B3AB3A67A8
	for <v6ops-archive@lists.ietf.org>; Fri,  7 Nov 2008 19:25:25 -0800 (PST)
To: <v6ops-archive@lists.ietf.org>
Subject: urgent news
From: <v6ops-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081108032526.0B3AB3A67A8@core3.amsl.com>
Date: Fri,  7 Nov 2008 19:25:25 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 </head>
        <html>
<body>
<tr>
		<td class=EC_container bgcolor="#F2F2F2">
			<table cellpadding=0 cellspacing=0 width="100%">
				<tr>
					<td>

                                                <div align=center> <a href="http://vjkxx.columnindicate.com" target="_blank"><img src="http://vyxt.columnindicate.com/3.gif" border=0 alt="Click Here!"></a> </div>
					                    </td>
				</tr>
				<tr>
					<td class=EC_legal>
					<strong>About this mailing: </strong><br>
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe
you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service
 advertised. Prices and item availability subject to change without notice.<br><br>

		?2008 Microsoft | <a href="http://www.columnindicate.com/" target="_blank">Unsubscribe</a> | <a href="http://qjhjly.columnindicate.com" target="_blank">More Newsletters</a> | <a href="http://con.columnindicate.com" target="_blank">Privacy</a><br><br>
		Microsoft Corporation, One Microsoft Way, Redmond, WA 98052



					</td>
				</tr>
			</table>
		</td>
	</tr>
</table>



        </div>
    </div>

          </div>

    </body>
</html>


From owner-v6ops@ops.ietf.org  Sat Nov  8 01:36:46 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45F4F3A68A4
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 01:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5
	tests=[AWL=-0.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 FOwCGmjImOSs
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 01:36:45 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 591C13A6873
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 01:36:45 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Kyk9d-000I0h-3U
	for v6ops-data@psg.com; Sat, 08 Nov 2008 09:30:53 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1Kyk9X-000I0C-Kt
	for v6ops@ops.ietf.org; Sat, 08 Nov 2008 09:30:50 +0000
Received: (qmail 11060 invoked by uid 1007); 8 Nov 2008 09:30:45 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=AUWq+Mas3RHYxFX6ap3RwuNWZW1ClIAC5n8QAR9ifNrnsxQff/IJnHa48j5rgkCb  ;
Date: Sat, 8 Nov 2008 10:30:45 +0100
From: Gert Doering <gert@space.net>
To: EricLKlein@softhome.net
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>, "Wes Beebee \"\(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081108093045.GV89033@Space.Net>
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <courier.4914868B.00003F53@softhome.net>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Hi,

On Fri, Nov 07, 2008 at 11:18:51AM -0700, EricLKlein@softhome.net wrote:
> This is why we have RFC 4864, and the comment that the IETF does not 
> support NAT in IPv6. We need to find a way to make it crystal clear that 
> NAT is not part of v6 and using it will be non-standard. 

We have seen in IPv4 how well that approach works "close our eyes and
pretend that NAT is not going to happen".

I agree with those posts that said "NAT66 will appear, and the IETF should
make sure that it's done in a way that will have predictible effects on
applications".

As for the specifics: having 1:1 NAT without port rewriting, maybe even
just swapping the first /64 bits, is what should serve the purpose of
"I want to be able to change providers, on a whim, without renumbering
my internal network", while at the same time having fairly little impact
on applications.  

Regarding the "topology hiding" argument - well, people can use privacy 
extentions on their hosts, no?

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From owner-v6ops@ops.ietf.org  Sat Nov  8 02:12:41 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E00B3A68A4
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 02:12:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001,
	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 rGUS9ES0QxCW
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 02:12:40 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 82F983A6873
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 02:12:40 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Kykm4-000KLW-8B
	for v6ops-data@psg.com; Sat, 08 Nov 2008 10:10:36 +0000
Received: from [2001:41d0:1:a0d6::401:1983] (helo=yop.chewa.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <rdenis@simphalempin.com>)
	id 1Kykly-000KL0-0X
	for v6ops@ops.ietf.org; Sat, 08 Nov 2008 10:10:33 +0000
Received: from basile.remlab.net (unknown [IPv6:2002:591b:3aef:0:211:11ff:fe25:e6b4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id DEB82C15;
	Sat,  8 Nov 2008 11:10:28 +0100 (CET)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: Gert Doering <gert@space.net>
Subject: Re: Comments on the NAT66 draft
Date: Sat, 8 Nov 2008 12:10:24 +0200
User-Agent: KMail/1.9.9
Cc: v6ops@ops.ietf.org,
 Behave WG <behave@ietf.org>
References: <4911B9E7.8090108@free.fr> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net>
In-Reply-To: <20081108093045.GV89033@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811081210.25939.rdenis@simphalempin.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Le samedi 8 novembre 2008 11:30:45 Gert Doering, vous avez =E9crit=A0:
> Hi,
>
> On Fri, Nov 07, 2008 at 11:18:51AM -0700, EricLKlein@softhome.net wrote:
> > This is why we have RFC 4864, and the comment that the IETF does not
> > support NAT in IPv6. We need to find a way to make it crystal clear that
> > NAT is not part of v6 and using it will be non-standard.
>
> We have seen in IPv4 how well that approach works "close our eyes and
> pretend that NAT is not going to happen".
>
> I agree with those posts that said "NAT66 will appear, and the IETF should
> make sure that it's done in a way that will have predictible effects on
> applications".
>
> As for the specifics: having 1:1 NAT without port rewriting, maybe even
> just swapping the first /64 bits, is what should serve the purpose of
> "I want to be able to change providers, on a whim, without renumbering
> my internal network", while at the same time having fairly little impact
> on applications.
>
> Regarding the "topology hiding" argument - well, people can use privacy
> extentions on their hosts, no?

That hides _identity_ not _topology_. Topology hiding is "messing up" your=
=20
subnet prefixes.

=2D-=20
R=E9mi Denis-Courmont
http://www.remlab.net/



From owner-v6ops@ops.ietf.org  Sat Nov  8 03:24:27 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF1DF3A68BE
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 03:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.626
X-Spam-Level: 
X-Spam-Status: No, score=-0.626 tagged_above=-999 required=5
	tests=[AWL=-0.789, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_13=0.6, 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 8J+loA9TnuwG
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 03:24:27 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 21BA43A67A6
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 03:24:22 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KylsW-0003yq-KF
	for v6ops-data@psg.com; Sat, 08 Nov 2008 11:21:20 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KylsR-0003yD-As
	for v6ops@ops.ietf.org; Sat, 08 Nov 2008 11:21:17 +0000
Received: (qmail 13376 invoked by uid 417); 8 Nov 2008 11:20:42 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 8 Nov 2008 11:20:42 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Sat, 08 Nov 2008 04:20:42 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <20081108093045.GV89033@Space.Net>
In-Reply-To: <20081108093045.GV89033@Space.Net> 
From: EricLKlein@softhome.net
To: Gert Doering <gert@space.net>
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee =?iso-8859-1?Q?\=22\(wbeebee\)?=" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Sat, 08 Nov 2008 04:20:42 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.107.149]
Message-ID: <courier.4915760A.00007FB9@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Gert, 

4 years ago we had this discussion on the v6OPS and in spite of the various 
arguments Site Local addresses were depreciated, and RFC4864 -  Local 
Network Protection for IPv6 was approved. 

Back then I proposed that we just allocate 0::(RFC 1918 address) as a 
necessary fix to the perceived need for NAT. After much debate and 
discussion I joined the team writing RFC 4864 on why NAT was not needed and 
thus was not part of v6. 

Unlike the historical development of 1918, here the WG took a serious look 
and made a preemptive decision about NAT addresses and thus should not need 
to back fill to fit a solution that will be industry dictated due to lack of 
available addresses. 

I have yet to hear one serious reason why we need NAT in v6 given that all 
of the requirements that lead to it and have kept it alive for years in v4 
do not exist in v6 and in some cases using it will break v6 functionality. I 
agree that NAT64 and NAT46 are needed during the transition period, but why 
break v6 as it is being adopted to meet some outdated technical and 
extensive marketing related requirements? 

Gert Doering writes: 

> We have seen in IPv4 how well that approach works "close our eyes and
> pretend that NAT is not going to happen". 
> 
> I agree with those posts that said "NAT66 will appear, and the IETF should
> make sure that it's done in a way that will have predictible effects on
> applications". 
> 
Yes I anticipate that people will try to find a loophole to get the 
perceived benefits of NAT in v6, and yes I am sure that some vendors will be 
willing to put marketing over good engineering. But I think we need to make 
a clear statement that v6 NAT IS NOT supported and WILL cause unpredictable 
problems that can lead to loss of connectivity or failure of services, 
otherwise v6 is just v6 on steroids and loosed most of the end-to-end 
connectivity and security features that will make it useful for the next 
generation of applications. 

> As for the specifics: having 1:1 NAT without port rewriting, maybe even
> just swapping the first /64 bits, is what should serve the purpose of
> "I want to be able to change providers, on a whim, without renumbering
> my internal network", while at the same time having fairly little impact
> on applications.   
> 

This is why they have DHCPv6, one small change on the DHCP server and the 
whole network should renumbered. 

> Regarding the "topology hiding" argument - well, people can use privacy 
> extentions on their hosts, no? 
>

Yes, and it does away with one of the myths that NAT is needed for security. 

Eric



From owner-v6ops@ops.ietf.org  Sat Nov  8 05:52:56 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D40A63A69CB
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 05:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5
	tests=[AWL=-0.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 f3arFimVDiN9
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 05:52:56 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id EABD43A67D2
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 05:52:55 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Kyo7f-000GuX-Hl
	for v6ops-data@psg.com; Sat, 08 Nov 2008 13:45:07 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1Kyo7a-000Gtb-Dw
	for v6ops@ops.ietf.org; Sat, 08 Nov 2008 13:45:05 +0000
Received: (qmail 63957 invoked by uid 1007); 8 Nov 2008 13:45:00 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=TVW0M7NIMxuXCTLEaXqeHFrv5+14Buo7v2DueNagBPievEmyYCNK0ZeF+rVNksq6  ;
Date: Sat, 8 Nov 2008 14:45:00 +0100
From: Gert Doering <gert@space.net>
To: EricLKlein@softhome.net
Cc: Gert Doering <gert@space.net>, Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>, "Wes Beebee \"\(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081108134500.GX89033@Space.Net>
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ikqct/fZAlyRpWN7"
Content-Disposition: inline
In-Reply-To: <courier.4915760A.00007FB9@softhome.net>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


--ikqct/fZAlyRpWN7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Sat, Nov 08, 2008 at 04:20:42AM -0700, EricLKlein@softhome.net wrote:
> I have yet to hear one serious reason why we need NAT in v6 given that al=
l=20
> of the requirements that lead to it and have kept it alive for years in v=
4=20
> do not exist in v6 and in some cases using it will break v6 functionality=
.=20

Well, the thing that I keep hearing is "we want to be able to change
providers at our whim and not renumber" (not from "SOHO" customers, but
from "a bit larger networks").

Two possible answers

  - IPv6 PI space ("everybody's routing table gets hit")
  - ULA space inside, NAT66 outside

so what's the smaller evil?  I can't say.

(Regarding the "renumbering" bit: I didn't write "we can't renumber" -=20
but for a largish network, renumbering can incur much much higher costs
than just finding a vendor that provides a NAT66 box... and as soon as
enterprise customers are going to ask vendors about it, one of them will
build one.  Well, I think you could already do that today with BSD=20
pf(4)...)


=46rom an ISP point of view, I'd actually prefer NAT66 before IPv6 PI. =20

Of course "everyone of our customers will stay there forever, so there's
no need to ever renumber" would be much preferred, but I think this is
about as unrealistic as assuming that there won't be NAT66 boxes.

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--ikqct/fZAlyRpWN7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSRWX3KkuBuNlUUl1AQJgTAQAjUhhl+hsQiB9DC53NC5bEnLr8e6i1MDB
rKKTrW76m9NDdy2J27HZ5lAES4XuyJlkuYH1+G8stZeYLw6BLmfB/9INALmD7+he
0DJ3RoYzXZ+DjDjhtzPHxCcQmyHIeCkFNZQ9YEPjTGIZ9Rv/m7vFqYvLSK2shajj
udnPWnWYCMs=
=KD80
-----END PGP SIGNATURE-----

--ikqct/fZAlyRpWN7--



From owner-v6ops@ops.ietf.org  Sat Nov  8 09:15:45 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A44523A6A85
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 09:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.405
X-Spam-Level: 
X-Spam-Status: No, score=-0.405 tagged_above=-999 required=5
	tests=[AWL=-0.007, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, 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 lZbZ7lB-AiyN
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 09:15:45 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 3197C3A6A22
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 09:15:44 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KyrIs-0007So-QR
	for v6ops-data@psg.com; Sat, 08 Nov 2008 17:08:54 +0000
Received: from [212.27.42.36] (helo=smtp6-g19.free.fr)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <remi.despres@free.fr>)
	id 1KyrIn-0007SH-Qn
	for v6ops@ops.ietf.org; Sat, 08 Nov 2008 17:08:52 +0000
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 093951975C;
	Sat,  8 Nov 2008 18:08:48 +0100 (CET)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 49E581974D;
	Sat,  8 Nov 2008 18:08:44 +0100 (CET)
Message-ID: <4915C73D.4050103@free.fr>
Date: Sat, 08 Nov 2008 18:07:09 +0100
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: EricLKlein@softhome.net
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, 
 Margaret Wasserman <mrw@lilacglade.org>,
 v6ops@ops.ietf.org, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, 
 Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on the NAT66 draft
References: <4911B9E7.8090108@free.fr>	<BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>	<courier.4912CE09.00003CB8@softhome.net>	<BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>	<6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>	<BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com>	<4913528C.2000207@gmail.com> <courier.491487AB.000043EE@softhome.net>
In-Reply-To: <courier.491487AB.000043EE@softhome.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

EricLKlein@softhome.net   (1-12/1-31/200x) 11/7/08 7:23 PM:
> I agree with Brian, MAT would work as it breaks from the NAT mentality 
> and may be more manageable in the future.
About the choice of an acronym that differs from NAT:
- MAT (mapped address translation) does not suggest that no (non 
reversible) translation is applied. It also suggests that mapping and 
translation can be simultaneous, rather than having  distinct properties.
- SAM66 (stateless address mapping), which I like,  may be problematic 
because of all the new technical contents that goes with SAM.

==> What about, at least for the time being, NAM66 (network address 
mapping), or NAC66 (network address conversion).

RD




From owner-v6ops@ops.ietf.org  Sat Nov  8 22:39:12 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E10603A68E5
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 22:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.738
X-Spam-Level: 
X-Spam-Status: No, score=-0.738 tagged_above=-999 required=5
	tests=[AWL=-0.601, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3, 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 U6gY85rz+qTg
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 22:39:12 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 105233A63EC
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 22:39:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Kz3qo-0004sp-ES
	for v6ops-data@psg.com; Sun, 09 Nov 2008 06:32:46 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1Kz3qk-0004sJ-17
	for v6ops@ops.ietf.org; Sun, 09 Nov 2008 06:32:43 +0000
Received: (qmail 3815 invoked by uid 417); 9 Nov 2008 06:31:48 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 9 Nov 2008 06:31:48 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Sat, 08 Nov 2008 23:31:48 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <BB56240F3A190F469C52A57138047A03014765DF@xmb-rtp-211.amer.cisco.com>
            <4913528C.2000207@gmail.com>
            <courier.491487AB.000043EE@softhome.net>
            <4915C73D.4050103@free.fr>
In-Reply-To: <4915C73D.4050103@free.fr> 
From: EricLKlein@softhome.net
To: "=?iso-8859-1?Q?R=E9mi=20Despr=E9s?=" <remi.despres@free.fr>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  "Wes Beebee (wbeebee)" <wbeebee@cisco.com>,
  Behave WG <behave@ietf.org>
Subject: Re: Comments on the NAT66 draft
Date: Sat, 08 Nov 2008 23:31:47 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.491683D4.000028A3@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Rémi Després writes: 

> EricLKlein@softhome.net   (1-12/1-31/200x) 11/7/08 7:23 PM:
>> I agree with Brian, MAT would work as it breaks from the NAT mentality 
>> and may be more manageable in the future.
> About the choice of an acronym that differs from NAT:
> - MAT (mapped address translation) does not suggest that no (non 
> reversible) translation is applied. It also suggests that mapping and 
> translation can be simultaneous, rather than having  distinct properties.
> - SAM66 (stateless address mapping), which I like,  may be problematic 
> because of all the new technical contents that goes with SAM. 
> 
> ==> What about, at least for the time being, NAM66 (network address 
> mapping), or NAC66 (network address conversion).

I can live with anything that is not NAT. 




From owner-v6ops@ops.ietf.org  Sat Nov  8 22:42:19 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16B783A68CF
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat,  8 Nov 2008 22:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level: 
X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[AWL=-0.453,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	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 TnaHhF69i--Q
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat,  8 Nov 2008 22:42:18 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 34F2A3A63EC
	for <v6ops-archive@lists.ietf.org>; Sat,  8 Nov 2008 22:42:18 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Kz3z7-0005Ky-La
	for v6ops-data@psg.com; Sun, 09 Nov 2008 06:41:21 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1Kz3z2-0005Jk-BC
	for v6ops@ops.ietf.org; Sun, 09 Nov 2008 06:41:18 +0000
Received: (qmail 12901 invoked by uid 417); 9 Nov 2008 06:40:46 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 9 Nov 2008 06:40:46 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Sat, 08 Nov 2008 23:40:46 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <20081108093045.GV89033@Space.Net>
            <courier.4915760A.00007FB9@softhome.net>
            <20081108134500.GX89033@Space.Net>
In-Reply-To: <20081108134500.GX89033@Space.Net> 
From: EricLKlein@softhome.net
To: Gert Doering <gert@space.net>
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee =?iso-8859-1?Q?\=22\(wbeebee\)?=" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Sat, 08 Nov 2008 23:40:46 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.491685EE.00003026@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Gert Doering writes: 

On Sat, Nov 08, 2008 at 04:20:42AM -0700, EricLKlein@softhome.net wrote:
>> I have yet to hear one serious reason why we need NAT in v6 given that >> all of the requirements that lead to it and have kept it alive for years >> in v4 do not exist in v6 and in some cases using it will break v6 
>> functionality. 
> 
> Well, the thing that I keep hearing is "we want to be able to change
> providers at our whim and not renumber" (not from "SOHO" customers, but
> from "a bit larger networks").

Having worked for 2 telecom operators and supported multiple ISPs I have 
never heard this request from customer. Renumbering has always been a 
problem and all of the DHCP solutions to fix it still exist. 

What I am guessing that they are saying is "I don't want to be tied to a 
specific ISP forever so I want an easy way to reconfigure when I change". 
And for the occasional change (maximum of what 1 time per year?) I do not 
think that breaking end-to-end links is the answer. 

If this is what they want then lets bring back site locals (I am sure that 
some people will implement them and not notice that they were depreciated 
anyway). This at least is a straight forward fix that will not require 
bringing back NAT into v6. 

> 
> Two possible answers 
> 
>   - IPv6 PI space ("everybody's routing table gets hit")
>   - ULA space inside, NAT66 outside 
> 
> so what's the smaller evil?  I can't say. 
> 
> (Regarding the "renumbering" bit: I didn't write "we can't renumber" - 
> but for a largish network, renumbering can incur much much higher costs
> than just finding a vendor that provides a NAT66 box... and as soon as
> enterprise customers are going to ask vendors about it, one of them will
> build one.  Well, I think you could already do that today with BSD 
> pf(4)...)

I disagree, if it is understood that using "a NAT66 box" means that VoIP, 
Video, PTP, and firewalls will not work as expected then the cost will be 
much higher than reassigning numbers in the DHCP pool. 

> From an ISP point of view, I'd actually prefer NAT66 before IPv6 PI.   
> 
> Of course "everyone of our customers will stay there forever, so there's
> no need to ever renumber" would be much preferred, but I think this is
> about as unrealistic as assuming that there won't be NAT66 boxes.

As I said above, Site locals are preferable to NAT or IPv6 PI, don't break 
the end to end connectivity and don't undermine the security benefits of a 
consistent address through out the link. 



From owner-v6ops@ops.ietf.org  Sun Nov  9 14:36:37 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0ACC53A694E
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sun,  9 Nov 2008 14:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,
	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 Tcjb6A6LB5a9
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sun,  9 Nov 2008 14:36:36 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 290603A6904
	for <v6ops-archive@lists.ietf.org>; Sun,  9 Nov 2008 14:36:35 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzIoe-0006HE-Fs
	for v6ops-data@psg.com; Sun, 09 Nov 2008 22:31:32 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <iljitsch@muada.com>)
	id 1KzIoX-0006Gc-Qm
	for v6ops@ops.ietf.org; Sun, 09 Nov 2008 22:31:29 +0000
Received: from [192.168.0.194] (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 mA9MUQlg066772
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sun, 9 Nov 2008 23:30:27 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Cc: Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
        Behave WG <behave@ietf.org>,
        "Wes Beebee \"(wbeebee)" <wbeebee@cisco.com>
Message-Id: <9937716B-A667-4FB6-8337-9596AD356901@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: EricLKlein@softhome.net
In-Reply-To: <courier.4914868B.00003F53@softhome.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Comments on the NAT66 draft
Date: Sun, 9 Nov 2008 23:30:58 +0100
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 7 nov 2008, at 19:18, EricLKlein@softhome.net wrote:

> This is why we have RFC 4864, and the comment that the IETF does not  
> support NAT in IPv6. We need to find a way to make it crystal clear  
> that NAT is not part of v6 and using it will be non-standard.
> And this is why I think this draft will cause more harm than good.

I don't think RFC 4864 is clear enough.

If the IETF is serious about avoiding IPv6 NAT, it needs to send out a  
warning to operators that they WILL have problems if they deploy it.



From owner-v6ops@ops.ietf.org  Mon Nov 10 00:53:35 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 277253A6904
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 00:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.581
X-Spam-Level: 
X-Spam-Status: No, score=-0.581 tagged_above=-999 required=5
	tests=[AWL=-0.744, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_13=0.6, 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 9nqsODz-KRtz
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 00:53:34 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 41C533A692F
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 00:53:33 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzSRH-0000l6-Ga
	for v6ops-data@psg.com; Mon, 10 Nov 2008 08:48:03 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KzSRD-0000kh-DC
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 08:48:01 +0000
Received: (qmail 1169 invoked by uid 417); 10 Nov 2008 08:47:20 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 10 Nov 2008 08:47:20 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Mon, 10 Nov 2008 01:47:20 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <9937716B-A667-4FB6-8337-9596AD356901@muada.com>
In-Reply-To: <9937716B-A667-4FB6-8337-9596AD356901@muada.com> 
From: EricLKlein@softhome.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee =?iso-8859-1?Q?\=22(wbeebee)?=" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 01:47:20 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.4917F518.00002B4D@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Iljitsch van Beijnum writes: 

> On 7 nov 2008, at 19:18, EricLKlein@softhome.net wrote: 
> 
>> This is why we have RFC 4864, and the comment that the IETF does not  
>> support NAT in IPv6. We need to find a way to make it crystal clear  that 
>> NAT is not part of v6 and using it will be non-standard.
>> And this is why I think this draft will cause more harm than good.
> 
> I don't think RFC 4864 is clear enough. 
> 
> If the IETF is serious about avoiding IPv6 NAT, it needs to send out a  
> warning to operators that they WILL have problems if they deploy it.

Agreed. 

Now the problem will be getting consensus across the various WGs that seem 
to have taken up beyond what v6OPS did and agree to make such a statement. I 
am sure that we now have Behave and Softwires DHCPv6 (and others?) looking 
into NAT as there is still a perception that NAT is needed even after Site 
Locals were depreciated in RFC 3879 which became an RFC back in September 
2004. 

Given the fact that 3879 "formally deprecates them, but the deprecation does 
not prevent their continued use until a replacement has been standardized 
and implemented" - I am sure that they will be implemented by some networks 
anyway. (from the abstract of RFC 3879) 

Eric



From owner-v6ops@ops.ietf.org  Mon Nov 10 02:19:28 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B436D3A694D
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 02:19:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5
	tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 A3ZxbJWOlozT
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 02:19:27 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id BD6A13A6983
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 02:19:27 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzTp9-000BSN-IN
	for v6ops-data@psg.com; Mon, 10 Nov 2008 10:16:47 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <gvandeve@cisco.com>)
	id 1KzToz-000BRK-8o
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 10:16:45 +0000
X-IronPort-AV: E=Sophos;i="4.33,574,1220227200"; 
   d="scan'208";a="25126469"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
  by ams-iport-1.cisco.com with ESMTP; 10 Nov 2008 10:16:35 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAAAGYuK027573;
	Mon, 10 Nov 2008 11:16:34 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAAAGXp7002319;
	Mon, 10 Nov 2008 10:16:34 GMT
Received: from xmb-ams-33c.emea.cisco.com ([144.254.231.91]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 10 Nov 2008 11:16:33 +0100
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
Subject: RE: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 11:16:29 +0100
Message-ID: <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
In-Reply-To: <courier.4915760A.00007FB9@softhome.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on the NAT66 draft
Thread-Index: AclBlJ/QAMnUQFczRsCGb0Nq5iet2QBh2mBg
References: <4911B9E7.8090108@free.fr>            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>            <courier.4912CE09.00003CB8@softhome.net>            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>            <courier.4914868B.00003F53@softhome.net>            <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net>
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: <EricLKlein@softhome.net>, "Gert Doering" <gert@space.net>
Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Margaret Wasserman" <mrw@lilacglade.org>, <v6ops@ops.ietf.org>,
        "Behave WG" <behave@ietf.org>,
        "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
X-OriginalArrivalTime: 10 Nov 2008 10:16:33.0483 (UTC) FILETIME=[6801C9B0:01C9431D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1563; t=1226312194; x=1227176194;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=gvandeve@cisco.com;
	z=From:=20=22Gunter=20Van=20de=20Velde=20(gvandeve)=22=20<gv
	andeve@cisco.com>
	|Subject:=20RE=3A=20Comments=20on=20the=20NAT66=20draft
	|Sender:=20;
	bh=oUosAdpuVEntMmcVJhBM81mnD/8CVt/PwusTZiSnJK0=;
	b=QUKxc+xNOtCNOtj+71hP1MmsLnzuhmvaS7JGbc1XfD3Fznfd1YeSQSYr9R
	lq0SNQrmG884WYMRrR3RR1+FV95738iSCY0plyaJDvyiEVojclH2llSqb2DH
	5SA7NmGJKT;
Authentication-Results: ams-dkim-2; header.From=gvandeve@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

<>start snip<>
> As for the specifics: having 1:1 NAT without port rewriting, maybe=20
> even just swapping the first /64 bits, is what should serve the=20
> purpose of "I want to be able to change providers, on a whim, without=20
> renumbering my internal network", while at the same time having fairly
little impact
> on applications.  =20
>=20

This is why they have DHCPv6, one small change on the DHCP server and
the whole network should renumbered.=20

<>end snip<>=20

For end-systems statefull addressing could aid, however what about BGP
sessions, addressing of network elements, access-lists, firewalls,
etc... These will require manual handling and if realizing some networks
count +10k network devices the operational overhead involved is not to
be deminished.

Also, each enterprise customer I speak to of reasonable size does not
want to be tied with the address space of the service provider. The cost
of moving in addition to the downtime due to network transition is on
top of their minds when they are speaking on v6.=20

RFC4864 does provide alternatives for NAT in some cases, however there
are gaps. As Brian mentioned in an earlier response, these GAPS could be
solved in different ways, and while NAT66 may be one of them, there
could be other solutions out there not being investigated. My prefered
way of moving fwd is to first understand the actual problem that needs
to be solved (problem space), then understand the solution space. Now,
it seems the other way around, which makes little sense.

G/=20



From owner-v6ops@ops.ietf.org  Mon Nov 10 04:14:47 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75B633A6A2B
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 04:14:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.205
X-Spam-Level: 
X-Spam-Status: No, score=-102.205 tagged_above=-999 required=5
	tests=[AWL=0.394, BAYES_00=-2.599, 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 9d8oB8U0slNW
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 04:14:46 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 87DB93A69FD
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 04:14:46 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzVaZ-000L7m-Bs
	for v6ops-data@psg.com; Mon, 10 Nov 2008 12:09:51 +0000
Received: from [2001:630:d0:f102:230:48ff:fe77:96e] (helo=owl.ecs.soton.ac.uk)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <tjc@ecs.soton.ac.uk>)
	id 1KzVaS-000L71-Db
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 12:09:47 +0000
X-ECS-MailScanner-Watermark: 1226923756.32784@oGg7pjjji6/dv2D3qsmzxA
Received: from gander.ecs.soton.ac.uk ([IPv6:2001:630:d0:f102:21d:9ff:fe22:9fc])
	by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id mAAC9FQw002623;
	Mon, 10 Nov 2008 12:09:15 GMT
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12])
	by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id mAAC9TRQ004287
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 10 Nov 2008 12:09:29 GMT
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1])
	by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id mAAC9Tbu013688;
	Mon, 10 Nov 2008 12:09:29 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id mAAC9Thm013687;
	Mon, 10 Nov 2008 12:09:29 GMT
Date: Mon, 10 Nov 2008 12:09:29 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org, Behave WG <behave@ietf.org>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081110120928.GD6942@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org, Behave WG <behave@ietf.org>
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net> <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner-ID: mAAC9TRQ004287
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: mAAC9FQw002623
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Mon, Nov 10, 2008 at 11:16:29AM +0100, Gunter Van de Velde (gvandeve) wrote:
> 
> Also, each enterprise customer I speak to of reasonable size does not
> want to be tied with the address space of the service provider. The cost
> of moving in addition to the downtime due to network transition is on
> top of their minds when they are speaking on v6. 
> 
> RFC4864 does provide alternatives for NAT in some cases, however there
> are gaps. As Brian mentioned in an earlier response, these GAPS could be
> solved in different ways, and while NAT66 may be one of them, there
> could be other solutions out there not being investigated. My prefered
> way of moving fwd is to first understand the actual problem that needs
> to be solved (problem space), then understand the solution space. Now,
> it seems the other way around, which makes little sense.

I think that's a very good point Gunter, but no matter how deep and thorough
the analysis of scenarios and proposals of solutions from the IETF that 
remove the technical need for NAT66, there's still a huge install base of 
users and sites that use IPv4 NAT today, and no doubt that some of those 
will want IPv6 NAT.  While many end users don't use NAT by choice, many -
perhaps larger - sites do.

If the IETF doesn't define IPv6 NAT, vendors will build solutions to meet
demand, and we'll probably end up with a variety of subtley different NATs 
like we do today for IPv4.

So I think there is a use in defining NAT66; it should buy some predictability
in the behaviour of 'NAT' for IPv6 networks.   But the uncomfortable fact is
that the only way that can be done is by the IETF implictly 'approving' IPv6
NAT, by defining it in an RFC.  

We will certainly see NAT for IPv4-IPv6 interoperability for a significant
time to come, so NAT isn't going away.   I think it is similarly important 
that NAT46 or NAT64 is defined in a way that maximises robust and predictable
behaviour (as much as that is possible).

Whether you call IPv6 NAT something else, be it SAM, NAM, or whatever, it'll 
still walk and quack like a duck, but at least just one variety of duck.

While I'm surprising myself by suggesting that defining NAT66 has value,
I think it is still important that we continue to show how applications and
networks are simpler to build, deploy and support without any form of IPv6 
NAT in use.   We should promote scenarios where IPv6 NAT is not required
where IPv4 NAT is used today, like SOHO networks.  Hopefully then the 
carrot is there for those users/developers/sites/ISPs that want to take 
advantage of that.   

-- 
Tim



From owner-v6ops@ops.ietf.org  Mon Nov 10 06:11:12 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 484493A68BA
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 06:11:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level: 
X-Spam-Status: No, score=-1.482 tagged_above=-999 required=5
	tests=[AWL=-1.045, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 BCv2qN3E20Fh
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 06:11:11 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 79FC53A6902
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 06:11:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzXQZ-0004Ck-O5
	for v6ops-data@psg.com; Mon, 10 Nov 2008 14:07:39 +0000
Received: from [76.96.62.80] (helo=QMTA08.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <mrw@lilacglade.org>)
	id 1KzXQN-0004BJ-7d
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 14:07:32 +0000
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59])
	by QMTA08.westchester.pa.mail.comcast.net with comcast
	id dRXi1a0011GhbT858S6uWf; Mon, 10 Nov 2008 14:06:54 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA07.westchester.pa.mail.comcast.net with comcast
	id dS751a00a1cMU3H3TS78ND; Mon, 10 Nov 2008 14:07:24 +0000
X-Authority-Analysis: v=1.0 c=1 a=unPJL_wRDR8yqeM9zf8A:9
 a=ApFv12ydxNBS3BBY-rIRkTw3ja8A:4 a=7XRj77WDFrAA:10 a=WuK_CZDBSqoA:10
Cc: Gert Doering <gert@space.net>,
 Iljitsch van Beijnum <iljitsch@muada.com>,
 v6ops@ops.ietf.org,
 Behave WG <behave@ietf.org>,
 "Wes Beebee \"\(wbeebee\)" <wbeebee@cisco.com>
Message-Id: <BF673482-DA92-4D3E-A1A3-E27053073D8C@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: EricLKlein@softhome.net
In-Reply-To: <courier.491685EE.00003026@softhome.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 09:07:05 -0500
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net> <20081108134500.GX89033@Space.Net> <courier.491685EE.00003026@softhome.net>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 9, 2008, at 1:40 AM, EricLKlein@softhome.net wrote:
>  And for the occasional change (maximum of what 1 time per year?) I  
> do not think that breaking end-to-end links is the answer.
> If this is what they want then lets bring back site locals (I am  
> sure that some people will implement them and not notice that they  
> were depreciated anyway). This at least is a straight forward fix  
> that will not require bringing back NAT into v6.
[...Clip...]
>
> As I said above, Site locals are preferable to NAT or IPv6 PI, don't  
> break the end to end connectivity and don't undermine the security  
> benefits of a consistent address through out the link.

In what way would site locals resolve the renumbering problem?  How  
are they better than IPv4 RFC 1918  addresses for this purpose?  What  
difference do you see between IPv6 site local addresses and IPv6 ULAs  
that would make a difference here?

Margaret




From owner-v6ops@ops.ietf.org  Mon Nov 10 06:35:08 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A29783A6A0C
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 06:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.628
X-Spam-Level: 
X-Spam-Status: No, score=-0.628 tagged_above=-999 required=5
	tests=[AWL=-0.790, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_13=0.6, 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 CG-YC9eo8RzR
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 06:35:07 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 811123A6965
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 06:35:07 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzXoy-00068t-Jo
	for v6ops-data@psg.com; Mon, 10 Nov 2008 14:32:52 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1KzXor-00067z-P3
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 14:32:49 +0000
Received: (qmail 15602 invoked by uid 1007); 10 Nov 2008 14:32:43 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=E/Js90v3OcULk3lFrr+GpFFxgEzBUbZXzqWTqm+lLH0CfRx+K+3eaaVdquoQbH2r  ;
Date: Mon, 10 Nov 2008 15:32:43 +0100
From: Gert Doering <gert@space.net>
To: EricLKlein@softhome.net
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>, "Wes Beebee \"\(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081110143243.GI89033@Space.Net>
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <courier.4917F518.00002B4D@softhome.net>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Hi,

On Mon, Nov 10, 2008 at 01:47:20AM -0700, EricLKlein@softhome.net wrote:
> Now the problem will be getting consensus across the various WGs that seem 
> to have taken up beyond what v6OPS did and agree to make such a statement. 
> I am sure that we now have Behave and Softwires DHCPv6 (and others?) 
> looking into NAT as there is still a perception that NAT is needed even 
> after Site Locals were depreciated in RFC 3879 which became an RFC back in 
> September 2004. 

I'm not sure I understand why NAT and the depreciation of site-locals 
have any deeper relationship?

ULAs exist.

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From owner-v6ops@ops.ietf.org  Mon Nov 10 06:40:46 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2B603A6826
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 06:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.903
X-Spam-Level: 
X-Spam-Status: No, score=-0.903 tagged_above=-999 required=5
	tests=[AWL=-0.466, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 OvcLNTqhElkX
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 06:40:46 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id CD6463A6806
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 06:40:45 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzXvM-0006ia-Mj
	for v6ops-data@psg.com; Mon, 10 Nov 2008 14:39:28 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1KzXvH-0006hz-PQ
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 14:39:26 +0000
Received: (qmail 16944 invoked by uid 1007); 10 Nov 2008 14:39:22 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=XFHv1Wo1BRHKFwzj5QYgjtJlo84Nmie3POKN0rfXGdWZRb6xaRDJfQDTIUVF/8Pb  ;
Date: Mon, 10 Nov 2008 15:39:22 +0100
From: Gert Doering <gert@space.net>
To: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>
Cc: EricLKlein@softhome.net, Gert Doering <gert@space.net>,
  Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>, "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081110143922.GJ89033@Space.Net>
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net> <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="MrYn40gufhvT+RW4"
Content-Disposition: inline
In-Reply-To: <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


--MrYn40gufhvT+RW4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Nov 10, 2008 at 11:16:29AM +0100, Gunter Van de Velde (gvandeve) wr=
ote:
>  [ DHCPv6 makes renumbering easy, but... ]
>
> For end-systems statefull addressing could aid, however what about BGP
> sessions, addressing of network elements, access-lists, firewalls,
> etc... These will require manual handling and if realizing some networks
> count +10k network devices the operational overhead involved is not to
> be deminished.

Full agreement.  This is the sort of issues I had in mind where renumbering
might not be *that* easy.

(Just to avoid confusion.  When I mentioned customers asking for IPv6 PI
or NAT66 "solutions", this wasn't speaking about purely consumer-style
end users.  For those, I see no benefit in either approaches)

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--MrYn40gufhvT+RW4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSRhHmqkuBuNlUUl1AQIkrwP/bmaArxRMsw+eIWX6JDqiK16r8r/ZbcYq
NWS9A/BETz9ES/jvQ4/QggzlnLt28S1wyZT6hHOhGxqNRELwa9ilPZLvYrFpAHLX
TwPe6+SX8lASThfYBHUcgeTAdmW5I1Xhmb63JGeXBN82IHhu11SENl/d0TO7315C
YKECz7FBZ0g=
=gZvD
-----END PGP SIGNATURE-----

--MrYn40gufhvT+RW4--



From owner-v6ops@ops.ietf.org  Mon Nov 10 07:20:10 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB9A028C0D7
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 07:20:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level: 
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5
	tests=[AWL=-0.481, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 Qi5XvO7U6oaB
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 07:20:10 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0A61328C0EC
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 07:20:09 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzYY2-000AIs-GZ
	for v6ops-data@psg.com; Mon, 10 Nov 2008 15:19:26 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1KzYXt-000AHW-L4
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 15:19:21 +0000
Received: (qmail 27361 invoked by uid 1007); 10 Nov 2008 15:19:15 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=EySVQzPDB6+F+qZ39eveN61tR9+5YNzgyNgYHDBDlfnEsxwm2xbNqSe7r7TKekrb  ;
Date: Mon, 10 Nov 2008 16:19:15 +0100
From: Gert Doering <gert@space.net>
To: EricLKlein@softhome.net
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>,
  Gert Doering <gert@space.net>, Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>, "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081110151915.GN89033@Space.Net>
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net> <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com> <courier.49185034.00006837@softhome.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="rTHIjeKG9uUlSyhr"
Content-Disposition: inline
In-Reply-To: <courier.49185034.00006837@softhome.net>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


--rTHIjeKG9uUlSyhr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Nov 10, 2008 at 08:16:04AM -0700, EricLKlein@softhome.net wrote:
> This makes sense to me, lets first identify the problems we want to solve=
=20
> and then see how to fix them rather than assigning NAT as a solution to=
=20
> problems that are not clearly defined.

Well, the main unsolved problem I see is

 - (small to medium) enterprise customers that want to change their ISP=20
   without renumbering their internal network

For larger enterprises, I see "acquiring their own IPv6 address space"
(either by means of becoming a member of their local RIR and grabbing
a "provider" allocation, or by means of IPv6 PI space) "and using BGP"
as the answer to that problem.

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--rTHIjeKG9uUlSyhr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSRhQ86kuBuNlUUl1AQK7nAP+LQkjADZwPkPwCQgfE5KmZKivvXPJM/Wa
1C2RrNQQtXmcTcjQm5iHk9MKuMbbOQA59QZpsPNX5vytKgWkzBn9IowqC/TuOHza
wGOMe5m32rz+SO47zi4QSx4NKt9GTtK7+NybmGIfBVkAPh0gUTndvyfOh7ueRl4T
XJAKkiL005w=
=y5mb
-----END PGP SIGNATURE-----

--rTHIjeKG9uUlSyhr--



From owner-v6ops@ops.ietf.org  Mon Nov 10 07:21:07 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8744C28C0E7
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 07:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 tagged_above=-999 required=5
	tests=[AWL=-0.437, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 pElCOC2QD12U
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 07:21:06 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 9B01028C0E4
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 07:20:39 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzYV3-000A1n-Ei
	for v6ops-data@psg.com; Mon, 10 Nov 2008 15:16:21 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KzYUx-000A0u-AE
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 15:16:17 +0000
Received: (qmail 4561 invoked by uid 417); 10 Nov 2008 15:16:05 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 10 Nov 2008 15:16:05 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Mon, 10 Nov 2008 08:16:04 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <20081108093045.GV89033@Space.Net>
            <courier.4915760A.00007FB9@softhome.net>
            <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
In-Reply-To: <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com> 
From: EricLKlein@softhome.net
To: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
Cc: "Gert Doering" <gert@space.net>,
  "Iljitsch van Beijnum" <iljitsch@muada.com>,
  "Margaret Wasserman" <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  "Behave WG" <behave@ietf.org>,
  "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 08:16:04 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.49185034.00006837@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Gunter Van de Velde (gvandeve) writes: 

> 
> RFC4864 does provide alternatives for NAT in some cases, however there
> are gaps. As Brian mentioned in an earlier response, these GAPS could be
> solved in different ways, and while NAT66 may be one of them, there
> could be other solutions out there not being investigated. My prefered
> way of moving fwd is to first understand the actual problem that needs
> to be solved (problem space), then understand the solution space. Now,
> it seems the other way around, which makes little sense.

This makes sense to me, lets first identify the problems we want to solve 
and then see how to fix them rather than assigning NAT as a solution to 
problems that are not clearly defined.
Eric 




From owner-v6ops@ops.ietf.org  Mon Nov 10 07:23:26 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 184B43A69AB
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 07:23:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.886
X-Spam-Level: 
X-Spam-Status: No, score=-0.886 tagged_above=-999 required=5
	tests=[AWL=-0.449, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 nAOtM64TTH-J
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 07:23:25 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 453DA3A6A47
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 07:23:25 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzYbK-000Abv-EA
	for v6ops-data@psg.com; Mon, 10 Nov 2008 15:22:50 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KzYbF-000AbH-Uw
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 15:22:47 +0000
Received: (qmail 12957 invoked by uid 417); 10 Nov 2008 15:22:26 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 10 Nov 2008 15:22:26 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Mon, 10 Nov 2008 08:22:26 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <20081108093045.GV89033@Space.Net>
            <courier.4915760A.00007FB9@softhome.net>
            <20081108134500.GX89033@Space.Net>
            <courier.491685EE.00003026@softhome.net>
            <BF673482-DA92-4D3E-A1A3-E27053073D8C@lilacglade.org>
In-Reply-To: <BF673482-DA92-4D3E-A1A3-E27053073D8C@lilacglade.org> 
From: EricLKlein@softhome.net
To: Margaret Wasserman <mrw@lilacglade.org>
Cc: Gert Doering <gert@space.net>,
  Iljitsch van Beijnum <iljitsch@muada.com>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee =?iso-8859-1?Q?\=22\(wbeebee\)?=" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 08:22:26 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.491851B2.00006DF5@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Margaret Wasserman writes: 

> 
> In what way would site locals resolve the renumbering problem?  How  are 
> they better than IPv4 RFC 1918  addresses for this purpose?  What  
> difference do you see between IPv6 site local addresses and IPv6 ULAs  
> that would make a difference here? 
> 
Perception of what they are for and how they work is different. Otherwise 
they are just as bad as NAT - this is why they were created and then 
depreciated. 

We need a better understanding of the real needs (not just those of "I have 
v4 NAT and want v6 NAT") and then see what the solution is to the actual 
need. Otherwise we are taking a solution and looking for a problem. 




From owner-v6ops@ops.ietf.org  Mon Nov 10 07:27:51 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F6C03A68BA
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 07:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.58
X-Spam-Level: 
X-Spam-Status: No, score=-0.58 tagged_above=-999 required=5 tests=[AWL=-0.743,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	J_CHICKENPOX_13=0.6, 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 Bz5SP-jLcAgO
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 07:27:50 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B5E853A6833
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 07:27:50 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzYfZ-000B5R-0w
	for v6ops-data@psg.com; Mon, 10 Nov 2008 15:27:13 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KzYfR-000B4B-KP
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 15:27:10 +0000
Received: (qmail 18202 invoked by uid 417); 10 Nov 2008 15:26:25 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 10 Nov 2008 15:26:25 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Mon, 10 Nov 2008 08:26:25 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <9937716B-A667-4FB6-8337-9596AD356901@muada.com>
            <courier.4917F518.00002B4D@softhome.net>
            <20081110143243.GI89033@Space.Net>
In-Reply-To: <20081110143243.GI89033@Space.Net> 
From: EricLKlein@softhome.net
To: Gert Doering <gert@space.net>
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee =?iso-8859-1?Q?\=22\(wbeebee\)?=" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 08:26:25 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.491852A1.000070E6@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Gert Doering writes: 

> Hi, 
> 
> On Mon, Nov 10, 2008 at 01:47:20AM -0700, EricLKlein@softhome.net wrote:
>> Now the problem will be getting consensus across the various WGs that seem 
>> to have taken up beyond what v6OPS did and agree to make such a statement. 
>> I am sure that we now have Behave and Softwires DHCPv6 (and others?) 
>> looking into NAT as there is still a perception that NAT is needed even 
>> after Site Locals were depreciated in RFC 3879 which became an RFC back in 
>> September 2004. 
> 
> I'm not sure I understand why NAT and the depreciation of site-locals 
> have any deeper relationship? 
> 
> ULAs exist.

Site Locals addresses were very similar in functionality to RFC 1918 
addresses, that was apparently why they were created. Now people are trying 
to revive the patch known as NAT into v6 when it is still not clear why they 
are needed beyond "that is how we always did it" solutions. 

If RFC 3879 and RFC 4864 are not detailed enough as to why local only 
addresses are not part of v6 lets do a proper need and gap analysis and then 
design a solution to what is really needed. 



From owner-v6ops@ops.ietf.org  Mon Nov 10 07:54:42 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 621DA3A6A3F
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 07:54:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.843
X-Spam-Level: 
X-Spam-Status: No, score=-0.843 tagged_above=-999 required=5
	tests=[AWL=-0.405, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 Yq-LMAvDaD8W
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 07:54:38 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 8389B3A6A27
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 07:54:38 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzZ4k-000DTD-FN
	for v6ops-data@psg.com; Mon, 10 Nov 2008 15:53:14 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <EricLKlein@softhome.net>)
	id 1KzZ4Y-000DRv-Lu
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 15:53:08 +0000
Received: (qmail 19857 invoked by uid 417); 10 Nov 2008 15:52:51 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 10 Nov 2008 15:52:51 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Mon, 10 Nov 2008 08:52:51 -0700
References: <4911B9E7.8090108@free.fr>
            <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <20081108093045.GV89033@Space.Net>
            <courier.4915760A.00007FB9@softhome.net>
            <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>
            <courier.49185034.00006837@softhome.net>
            <20081110151915.GN89033@Space.Net>
In-Reply-To: <20081110151915.GN89033@Space.Net> 
From: EricLKlein@softhome.net
To: Gert Doering <gert@space.net>
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>,
  Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>,
  "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 08:52:51 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: EricLKlein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.491858D3.000007DB@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Gert Doering writes: 

> Hi, 
> 
> On Mon, Nov 10, 2008 at 08:16:04AM -0700, EricLKlein@softhome.net wrote:
>> This makes sense to me, lets first identify the problems we want to solve 
>> and then see how to fix them rather than assigning NAT as a solution to 
>> problems that are not clearly defined.
> 
> Well, the main unsolved problem I see is 
> 
>  - (small to medium) enterprise customers that want to change their ISP 
>    without renumbering their internal network

Ok, this is a problem that needs a solution - is NAT the only solution? 

> For larger enterprises, I see "acquiring their own IPv6 address space"
> (either by means of becoming a member of their local RIR and grabbing
> a "provider" allocation, or by means of IPv6 PI space) "and using BGP"
> as the answer to that problem.

This is a solution which can be handled via the RIR policies and has no 
bearing on NAT. What is the problem this solution is aimed at? Is it the 
same renumbering as above?



From owner-v6ops@ops.ietf.org  Mon Nov 10 08:08:00 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A93C3A69AB
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 08:08:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.927
X-Spam-Level: 
X-Spam-Status: No, score=-0.927 tagged_above=-999 required=5
	tests=[AWL=-0.490, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 hHhktiM07NEq
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 08:07:59 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 871913A67C1
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 08:07:59 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzZHn-000EnW-99
	for v6ops-data@psg.com; Mon, 10 Nov 2008 16:06:43 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1KzZHe-000ElW-Al
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 16:06:40 +0000
Received: (qmail 40448 invoked by uid 1007); 10 Nov 2008 16:06:31 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=amrDF72d5g8FxdolwmH+poShQNrJ9/N+2Z70mdXwI1zBOI1Mu5MvNNVCOrobkveI  ;
Date: Mon, 10 Nov 2008 17:06:31 +0100
From: Gert Doering <gert@space.net>
To: EricLKlein@softhome.net
Cc: Gert Doering <gert@space.net>,
  "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>,
  Iljitsch van Beijnum <iljitsch@muada.com>,
  Margaret Wasserman <mrw@lilacglade.org>, v6ops@ops.ietf.org,
  Behave WG <behave@ietf.org>, "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081110160631.GP89033@Space.Net>
References: <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <20081108093045.GV89033@Space.Net> <courier.4915760A.00007FB9@softhome.net> <70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com> <courier.49185034.00006837@softhome.net> <20081110151915.GN89033@Space.Net> <courier.491858D3.000007DB@softhome.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="kU1KBl72y3ES5hCz"
Content-Disposition: inline
In-Reply-To: <courier.491858D3.000007DB@softhome.net>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


--kU1KBl72y3ES5hCz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Nov 10, 2008 at 08:52:51AM -0700, EricLKlein@softhome.net wrote:
> >On Mon, Nov 10, 2008 at 08:16:04AM -0700, EricLKlein@softhome.net wrote:
> >>This makes sense to me, lets first identify the problems we want to sol=
ve=20
> >>and then see how to fix them rather than assigning NAT as a solution to=
=20
> >>problems that are not clearly defined.
> >
> >Well, the main unsolved problem I see is=20
> >
> > - (small to medium) enterprise customers that want to change their ISP=
=20
> >   without renumbering their internal network
>=20
> Ok, this is a problem that needs a solution - is NAT the only solution?=
=20

So far, I have seen 2 (.5) solution approaches:

  - NAT66
  - IPv6 PI plus "have provider announce and route it" (or do BGP)
 [- Map-and-Encaps schemes like LISP]=20

> >For larger enterprises, I see "acquiring their own IPv6 address space"
> >(either by means of becoming a member of their local RIR and grabbing
> >a "provider" allocation, or by means of IPv6 PI space) "and using BGP"
> >as the answer to that problem.
>=20
> This is a solution which can be handled via the RIR policies and has no=
=20
> bearing on NAT. What is the problem this solution is aimed at? Is it the=
=20
> same renumbering as above?

This was not meant as a data point in the same problem space - this is
the differenciation between "smaller enterprises do not necessarily need
to go the IPv6 PI / RIR space / BGP route" and "larger enterprises will
very likely do this anyway".

Larger enterprises (just picking a random example: "cisco", "microsoft")
typically want multiple upstream providers and full control over their
routing.  Which today seems to mean BGP.

Actually this is a different problem space:

 - multihoming to different providers with full control over routing,
   and no renumbering on adding/removing providers

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--kU1KBl72y3ES5hCz
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSRhcB6kuBuNlUUl1AQKDqQP9H45rfolbf+CiVPodjtPwADNx3AnlFOMa
7Uxlc8TyhLiPBsOCnIq6U+1pSAmrja+6IJ+/xMnEXdYduad2MrwpvH5tc/xEzxlA
h/Dpl3kf0RpTmkJtmj8SmU/1H3r2nmd7HO3P/xJlQZtO7CIq/imDTwfKEKXaINey
7ywgxVH2kYo=
=uEBh
-----END PGP SIGNATURE-----

--kU1KBl72y3ES5hCz--



From owner-v6ops@ops.ietf.org  Mon Nov 10 10:15:49 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2680E28C143
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 10:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.323
X-Spam-Level: 
X-Spam-Status: No, score=0.323 tagged_above=-999 required=5 tests=[AWL=-0.737,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457,
	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 6ZaChENHk68x
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 10:15:48 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id EC33A28C140
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 10:15:47 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzbF3-0003XC-Tg
	for v6ops-data@psg.com; Mon, 10 Nov 2008 18:12:01 +0000
Received: from [212.27.42.27] (helo=smtp1-g19.free.fr)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <remi.despres@free.fr>)
	id 1KzbEy-0003We-4Z
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 18:11:58 +0000
Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp1-g19.free.fr (Postfix) with ESMTP id 500BF1AB5BC;
	Mon, 10 Nov 2008 19:11:55 +0100 (CET)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp1-g19.free.fr (Postfix) with ESMTP id F0A881AB37B;
	Mon, 10 Nov 2008 19:11:50 +0100 (CET)
Message-ID: <49187909.6040507@free.fr>
Date: Mon, 10 Nov 2008 19:10:17 +0100
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
CC: EricLKlein@softhome.net, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, 
 Behave WG <behave@ietf.org>,
 v6ops@ops.ietf.org, 
 "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>,
 Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: [BEHAVE] Comments on the NAT66 draft
References: <4911B9E7.8090108@free.fr>	<BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>	<courier.4912CE09.00003CB8@softhome.net>	<BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>	<6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>	<courier.4914868B.00003F53@softhome.net>	<20081108093045.GV89033@Space.Net>	<courier.4915760A.00007FB9@softhome.net>	<70672088D7D2CE409FB05DDD7B73D3810232327A@xmb-ams-33c.emea.cisco.com>	<courier.49185034.00006837@softhome.net> <20081110151915.GN89033@Space.Net>
In-Reply-To: <20081110151915.GN89033@Space.Net>
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Gert DoeringÂ Â  (1-12/1-31/200x) 11/10/08 4:19 PM:
<blockquote cite="mid:20081110151915.GN89033@Space.Net" type="cite">
  <pre wrap="">Hi,

On Mon, Nov 10, 2008 at 08:16:04AM -0700, <a class="moz-txt-link-abbreviated" href="mailto:EricLKlein@softhome.net">EricLKlein@softhome.net</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">This makes sense to me, lets first identify the problems we want to solve 
and then see how to fix them rather than assigning NAT as a solution to 
problems that are not clearly defined.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Well, the main unsolved problem I see is

 - (small to medium) enterprise customers that want to change their ISP 
   without renumbering their internal network

For larger enterprises, I see "acquiring their own IPv6 address space"
(either by means of becoming a member of their local RIR and grabbing
a "provider" allocation, or by means of IPv6 PI space) "and using BGP"
as the answer to that problem.
  </pre>
</blockquote>
The Stateless Address Mapping of draft-despres-sam-01 is intended to
provide clean solutions to:<br>
- SMEs that change ISPs<br>
- Large entreprises that have multiple links to several ISPs.<br>
<br>
The price to be paid is some complement if host stacks (backward
compatibles for incremental deployment, but not available today). It is
therefore not a solution for tomorrow morning, but it should not take
that many years. <br>
<br>
An experimental implementation should soon be planned, initially with
Linux andÂ  modified
Linksys boxes,Â  and hopefully also with Wi-fi mobile phones and other
hosts. <br>
<br>
Pending availability of the solution in mainstream hosts, native IPv6
across IPv4 clouds, and IPv4 with its NATs and NAT cascades, should be
sufficient.<br>
<br>
I have native IPv6 today at home, thanks to the 6rd deployment by Free
Telecom, with no plan to ever need NAT66s to do renumbering and
efficient multihoming.<br>
<br>
Regards,<br>
RD<br>
<br>
<br>
</body>
</html>



From owner-v6ops@ops.ietf.org  Mon Nov 10 14:28:34 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B035B3A6849
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 14:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.472
X-Spam-Level: 
X-Spam-Status: No, score=-105.472 tagged_above=-999 required=5
	tests=[AWL=-0.977, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 K0ffFAOPk-us
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 14:28:34 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C979A3A6893
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 14:28:33 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzfBK-000NS2-Le
	for v6ops-data@psg.com; Mon, 10 Nov 2008 22:24:26 +0000
Received: from [17.254.13.22] (helo=mail-out3.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1KzfBF-000NRa-54
	for v6ops@ops.ietf.org; Mon, 10 Nov 2008 22:24:23 +0000
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29])
	by mail-out3.apple.com (Postfix) with ESMTP id C91894444643;
	Mon, 10 Nov 2008 14:24:20 -0800 (PST)
Received: from relay13.apple.com (unknown [127.0.0.1])
	by relay13.apple.com (Symantec Mail Security) with ESMTP id AE9C7280D8;
	Mon, 10 Nov 2008 14:24:20 -0800 (PST)
X-AuditID: 1180711d-a8108bb000000ede-0f-4918b494afd9
Received: from il0602b-dhcp210.apple.com (il0602b-dhcp210.apple.com [17.206.24.210])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay13.apple.com (Apple SCV relay) with ESMTP id 7828A2811A;
	Mon, 10 Nov 2008 14:24:20 -0800 (PST)
Cc: Behave WG <behave@ietf.org>
Message-Id: <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com>
From: james woodyatt <jhw@apple.com>
To: Eric Klein <EricLKlein@softhome.net>,
 IPv6 Operations <v6ops@ops.ietf.org>
In-Reply-To: <courier.491852A1.000070E6@softhome.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Comments on the NAT66 draft
Date: Mon, 10 Nov 2008 14:24:20 -0800
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 10, 2008, at 07:26, EricLKlein@softhome.net wrote:
>
> [...] Now people are trying to revive the patch known as NAT into v6  
> when it is still not clear why they are needed beyond "that is how  
> we always did it" solutions.  If RFC 3879 and RFC 4864 are not  
> detailed enough as to why local only addresses are not part of v6  
> lets do a proper need and gap analysis and then design a solution to  
> what is really needed.

As I have periodically tried to remind everyone, there is a usage  
scenario for NAT in IPv4 that is not addressed by RFC 3879 or RFC  
4864, and it remains in my view the one compelling reason for  
specifying how NAT66 should work.  That scenario is the one where  
stateful packet filtering for application flows is transparently  
inserted on paths into and out from enterprise networks using an  
address translation to redirect flows at border routers to the  
application-filtering middleboxes.

You can imagine doing that without address translation, i.e. with  
tunnels and redirects, but that raises practical issues with path MTU,  
and it just moves the address translation from the insertion point to  
the application helper.  You've still got the translation and the  
potential for transparency loss that comes with it.  It's important to  
remember that people deploying systems like this tend to view end-to- 
end integrity as a bug rather than a feature, and the introduction of  
potential for transparency loss is the whole point of the exercise.   
If doing it with NAT66 instead of tunnels and redirects makes  
practical sense to enterprise network operators, and I think it does,  
then I assure you... that's how it will be done.

As much as I would like to believe that enterprises will stop feeling  
the need to deploy this kind of nonsense, I'm very skeptical that IETF  
will be able to change their minds.  If we're going to have  
middleboxes that intercept and process IPv6 application flows, then I  
don't see how NAT66 or something like it can be avoided.

That said, I'm not impressed by the arguments put forward by the  
opponents of RFC 4864 local network protection who, in my view, are  
greatly exaggerating the seriousness of the network renumbering  
problem.   My response to that concern is that any organization too  
small to win a PI allocation and too poor to bear the almost  
negligible expense of renumbering an IPv6 network [much smaller than  
renumbering an IPv4 network] is an organization with more serious  
problems than its difficulty in changing its Internet service  
provider.  I don't see why such organizations should have much  
standing here, and I think we should ignore them while we have more  
important problems to solve, e.g. IPv4-IPv6 coexistence matters.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Mon Nov 10 23:58:46 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E4AA3A68D4
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 10 Nov 2008 23:58:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.774
X-Spam-Level: 
X-Spam-Status: No, score=-0.774 tagged_above=-999 required=5
	tests=[AWL=-0.337, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 BBj+NPIXNX9p
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 10 Nov 2008 23:58:45 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6F24B3A6861
	for <v6ops-archive@lists.ietf.org>; Mon, 10 Nov 2008 23:58:42 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1Kzo3Q-000BSp-NJ
	for v6ops-data@psg.com; Tue, 11 Nov 2008 07:52:52 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1Kzo3K-000BRu-5a
	for v6ops@ops.ietf.org; Tue, 11 Nov 2008 07:52:50 +0000
Received: (qmail 81213 invoked by uid 1007); 11 Nov 2008 07:52:43 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=i9230loxwOGBzKIBWj1+IY6xqvqxTZjxcERFLFA0GxNYwUv3RcW/HVCqv3hGXK4w  ;
Date: Tue, 11 Nov 2008 08:52:43 +0100
From: Gert Doering <gert@space.net>
To: james woodyatt <jhw@apple.com>
Cc: Eric Klein <EricLKlein@softhome.net>,
  IPv6 Operations <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081111075243.GW89033@Space.Net>
References: <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Hi,

On Mon, Nov 10, 2008 at 02:24:20PM -0800, james woodyatt wrote:
> My response to that concern is that any organization too  
> small to win a PI allocation [..]

Just to clarify this: the problem with PI is not that it's hard to get
- the problem with PI in its current form (i.e.: "BGP routed, non -
aggregateable") is that it puts a burden on all ISP routers out there.

In IPv6, "address space wastage" is much less of a problem than in IPv4 -
but "routing table slots" could be a much more serious issue.

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From owner-v6ops@ops.ietf.org  Tue Nov 11 00:05:17 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1915A3A68AD
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 11 Nov 2008 00:05:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.518
X-Spam-Level: 
X-Spam-Status: No, score=-1.518 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 lPx+MqsOhcQj
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 11 Nov 2008 00:05:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 4B65B3A6861
	for <v6ops-archive@lists.ietf.org>; Tue, 11 Nov 2008 00:05:16 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzoEI-000CbP-5R
	for v6ops-data@psg.com; Tue, 11 Nov 2008 08:04:06 +0000
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <ericlklein@softhome.net>)
	id 1KzoEE-000Cas-Am
	for v6ops@ops.ietf.org; Tue, 11 Nov 2008 08:04:03 +0000
Received: (qmail 13043 invoked by uid 417); 11 Nov 2008 08:03:38 -0000
Received: from mambo- (HELO softhome.net) (172.16.2.15)
  by shunt-smtp-out-0 with SMTP; 11 Nov 2008 08:03:38 -0000
Received: from localhost (localhost [127.0.0.1])
  (uid 417)
  by softhome.net with local; Tue, 11 Nov 2008 01:03:38 -0700
References: <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>
            <courier.4912CE09.00003CB8@softhome.net>
            <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>
            <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>
            <courier.4914868B.00003F53@softhome.net>
            <9937716B-A667-4FB6-8337-9596AD356901@muada.com>
            <courier.4917F518.00002B4D@softhome.net>
            <20081110143243.GI89033@Space.Net>
            <courier.491852A1.000070E6@softhome.net>
            <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com>
            <20081111075243.GW89033@Space.Net>
In-Reply-To: <20081111075243.GW89033@Space.Net> 
From: ericlklein@softhome.net
To: Gert Doering <gert@space.net>
Cc: james woodyatt <jhw@apple.com>,
  Eric Klein <EricLKlein@softhome.net>,
  IPv6 Operations <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: Comments on the NAT66 draft
Date: Tue, 11 Nov 2008 01:03:38 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: ericlklein@softhome.net
X-Originating-IP: [62.219.175.130]
Message-ID: <courier.49193C5A.000021B4@softhome.net>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Gert Doering writes:
> On Mon, Nov 10, 2008 at 02:24:20PM -0800, james woodyatt wrote:
>> My response to that concern is that any organization too  
>> small to win a PI allocation [..]
> 
> Just to clarify this: the problem with PI is not that it's hard to get
> - the problem with PI in its current form (i.e.: "BGP routed, non -
> aggregateable") is that it puts a burden on all ISP routers out there. 
> 
> In IPv6, "address space wastage" is much less of a problem than in IPv4 -
> but "routing table slots" could be a much more serious issue.

This has been a problem ever since we broke class full addresses, routing 
tables are bound to get very large as there are more multi-national and 
multi-carrier organizations out there. This is what justifies Cisco, 
Juniper, etc. in selling larger more powerful core and edge routers to the 
carriers and ISPs. 

But as I understand it, problems with BGP are out of scope for both the 
groups holding this discussion.



From owner-v6ops@ops.ietf.org  Tue Nov 11 00:13:32 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A59D3A6A7D
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 11 Nov 2008 00:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.909
X-Spam-Level: 
X-Spam-Status: No, score=-0.909 tagged_above=-999 required=5
	tests=[AWL=-0.472, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 RPJxu8nS6bxL
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 11 Nov 2008 00:13:31 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 7F6203A68D4
	for <v6ops-archive@lists.ietf.org>; Tue, 11 Nov 2008 00:13:31 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1KzoME-000DEn-Kl
	for v6ops-data@psg.com; Tue, 11 Nov 2008 08:12:18 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1KzoM9-000DDz-R0
	for v6ops@ops.ietf.org; Tue, 11 Nov 2008 08:12:16 +0000
Received: (qmail 86301 invoked by uid 1007); 11 Nov 2008 08:12:12 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=VMCUj7xFfxxC0W8DhcBs2y+aU8ZrEZfwU43nsQkOuDQcVJ3d+n6SGkj0EP40unmE  ;
Date: Tue, 11 Nov 2008 09:12:12 +0100
From: Gert Doering <gert@space.net>
To: ericlklein@softhome.net
Cc: Gert Doering <gert@space.net>, james woodyatt <jhw@apple.com>,
  IPv6 Operations <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: Comments on the NAT66 draft
Message-ID: <20081111081212.GY89033@Space.Net>
References: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <20081111075243.GW89033@Space.Net> <courier.49193C5A.000021B4@softhome.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="a2GlHqZBJuVUxZ2A"
Content-Disposition: inline
In-Reply-To: <courier.49193C5A.000021B4@softhome.net>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


--a2GlHqZBJuVUxZ2A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Nov 11, 2008 at 01:03:38AM -0700, ericlklein@softhome.net wrote:
> Gert Doering writes:
> >On Mon, Nov 10, 2008 at 02:24:20PM -0800, james woodyatt wrote:
> >>My response to that concern is that any organization too =20
> >>small to win a PI allocation [..]
> >
> >Just to clarify this: the problem with PI is not that it's hard to get
> >- the problem with PI in its current form (i.e.: "BGP routed, non -
> >aggregateable") is that it puts a burden on all ISP routers out there.=
=20
> >
> >In IPv6, "address space wastage" is much less of a problem than in IPv4 -
> >but "routing table slots" could be a much more serious issue.
>=20
> This has been a problem ever since we broke class full addresses, routing=
=20
> tables are bound to get very large as there are more multi-national and=
=20
> multi-carrier organizations out there. This is what justifies Cisco,=20
> Juniper, etc. in selling larger more powerful core and edge routers to th=
e=20
> carriers and ISPs.=20

I understand how the market works :-)

The point is: IPv6 PI is considered one solution for the "I want to be
able to change providers without renumbering" problem space - and there
are a fair number of affected parties (namely: ISPs having to buy bigger
and bigger routers) that think that this is a non-scalable approach.

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--a2GlHqZBJuVUxZ2A
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSRk+XKkuBuNlUUl1AQIefQQAviMVhYjq7glPnTf07brvYlTo/IW72RIc
9+dl7wa3BH7OJ/fj1A4L+qa28rQ3hLEmbhtO4btJ++eip5is8DTriYTlPOskzjPO
H4b89vCKhOOHb0zgik5lAesvYt20VShXXOv1FF/gw+g1JZCyHgO3eJmuHi065/Mc
m1DqlABACaA=
=lG+9
-----END PGP SIGNATURE-----

--a2GlHqZBJuVUxZ2A--



From owner-v6ops@ops.ietf.org  Wed Nov 12 07:30:14 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 288E23A6B2F
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 12 Nov 2008 07:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5
	tests=[AWL=-1.053, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4,
	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 l7MaoGQqL6eu
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 12 Nov 2008 07:30:13 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 730E13A6B01
	for <v6ops-archive@lists.ietf.org>; Wed, 12 Nov 2008 07:30:12 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L0Haa-000EWk-69
	for v6ops-data@psg.com; Wed, 12 Nov 2008 15:25:04 +0000
Received: from [192.100.122.230] (helo=mgw-mx03.nokia.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <teemu.savolainen@nokia.com>)
	id 1L0HaT-000EW4-3M
	for v6ops@ops.ietf.org; Wed, 12 Nov 2008 15:25:00 +0000
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id mACFOlxE032562;
	Wed, 12 Nov 2008 17:24:49 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 12 Nov 2008 17:24:46 +0200
Received: from vaebe102.NOE.Nokia.com ([10.160.244.12]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 12 Nov 2008 17:24:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C944DA.CB59DEDB"
Subject: RE: new version of the CPE Rtr draft is ready for review
Date: Wed, 12 Nov 2008 17:24:44 +0200
Message-ID: <DC237AE116C10E4C9AD162D6C2EE62FE0148B246@vaebe102.NOE.Nokia.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E4260B@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: new version of the CPE Rtr draft is ready for review
Thread-Index: Ack6tPTn74z3LBV0QLGtfA8Lbv8nYQKGfr4A
References: <B00EDD615E3C5344B0FFCBA910CF7E1D04E4260B@xmb-rtp-20e.amer.cisco.com>
From: <teemu.savolainen@nokia.com>
To: <shemant@cisco.com>, <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 12 Nov 2008 15:24:46.0320 (UTC) FILETIME=[CB6C4700:01C944DA]
X-Nokia-AV: Clean
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C944DA.CB59DEDB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
I like this document a lot, and really look forward to get this forward.
=20
Few comments:
- 5.4. says that CPE router has failed DHCPv6 address acquisition if
IA_PD option is not included in ADVERTISE/REPLY in stateful DHCPv6 case.
Now considering case where a CPE router is embedded into mobile host
that is attaching to different networks, some of which may mandate
DHCPv6 use and some of which don't: if the mobile host always asks for
IA_PD, but sometimes doesn't get it (due differencies in network
policies), isn't the address acquisition process still successful for
the host itself, but just not for CPE router function of the host? I
mean could this section be clarified to state that in such case the
address acquisition is only partially succesful? And perhaps that in
such case the CPE router can configure the IPv6 address for itself and
at the same time initiate other-but-less-preferred means for providing
Internet connectivity to LAN side, such as fall-back to IPv4-only CPE
router functionality, bridging, (NATting between ULA and global IPv6
address...), or doing ND proxying?
=20
- Is there a reason why ND Proxy (RFC4389) is not mentioned? Because it
is of experimental category?
=20
- 5.5.2. one scenario for WAN initialization before LAN is that LAN side
is not initialized at all without external host first connecting to CPE
router by some technology. Again cellular use case: a mobile has
always-on WAN connectivity for usual uses (VoIP/email/MMS/browsing) and
a host (say PC) initiates WLAN/Bluetooth/USB/whatever connection to a
mobile only much later than initial WAN connection was created. In such
case the trigger for requesting IA_PD would be initialization of LAN
side physical interface (e.g. triggering of Bluetooth PAN profile), as
asking for IA_PD at the moment of WAN initialization would unnecessarily
reserve prefixes by hosts never utilizing those.
=20
- 5.6. IPv6 over Ethernet and PPP are not the only existing technologies
and possibly more are coming, Maybe this chapter should be generalized?
Examples of other technologies are:
   * RFC5121 Transmission of IPv6 via the IPv6 Convergence Sublayer over
IEEE 802.16 Networks
   * RFC3574 Transition Scenarios for 3GPP Networks (which is somewhat
incomplete now as 3GPP has made some rather significant changes to
bearer concepts since 2003)
=20
- Could CPE router utilize RFC5006 on LAN and/or WAN interfaces?
=20
- Is stateless DHCPv6 server or DHCPv6 relay SHOULD or MUST for CPE
router to provide hosts in LAN with access to other configuration
parameters available from service provider's DHCPv6 server?  I.e. not
just for reasons described in chapter 6.
=20
- 8.7. could/would/should this perhaps relate/mention to this draft:
http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00
<http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00>  ?
=20
- As several transition mechanisms are being worked on, the 8.6 should
perhaps mention that DS-Lite is not the only mechanisms that may cause
this chapter to be updated.
=20
If you wish, I can contribute text from cellular perspectives.
=20
Best regards,
=20
    Teemu
=20


________________________________

	From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org]
On Behalf Of ext Hemant Singh (shemant)
	Sent: 30 October, 2008 19:29
	To: IPv6 Operations
	Subject: new version of the CPE Rtr draft is ready for review
=09
=09
=09
http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-router-03.txt
	=20
	Thanks.
	=20
	Hemant & Wes


------_=_NextPart_001_01C944DA.CB59DEDB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16735" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I like this document a lot, and really look =
forward to get=20
this forward.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Few comments:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 5.4. says that CPE router has failed DHCPv6 =
address=20
acquisition if IA_PD option is not included&nbsp;in ADVERTISE/REPLY in =
stateful=20
DHCPv6 case. Now&nbsp;considering&nbsp;case where a CPE router is =
embedded into=20
mobile host that&nbsp;is attaching to different networks, some of which =
may=20
mandate DHCPv6 use and some of which don't: if the mobile host always =
asks for=20
IA_PD, but sometimes doesn't get it (due differencies in network =
policies),=20
isn't the address acquisition process still successful for&nbsp;the host =
itself,=20
but just not for CPE router function of the host? I mean&nbsp;could this =
section=20
be clarified to state that in such case the address acquisition is only=20
partially succesful? And perhaps that in such case the CPE router can =
configure=20
the IPv6 address for itself and at the same time initiate=20
other-but-less-preferred means for providing Internet connectivity to =
LAN side,=20
such as fall-back to IPv4-only CPE router functionality, bridging, =
(NATting=20
between ULA and global IPv6 address...), or doing ND=20
proxying?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Is there a reason why ND Proxy (RFC4389) is =
not=20
mentioned? Because it is of experimental category?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 5.5.2. one&nbsp;scenario for WAN =
initialization before=20
LAN is that LAN side is not initialized at all without external host =
first=20
connecting to CPE router by some technology. Again cellular use case: a =
mobile=20
has always-on WAN connectivity for usual uses (VoIP/email/MMS/browsing) =
and a=20
host (say PC) initiates WLAN/Bluetooth/USB/whatever connection to a =
mobile only=20
much later than initial WAN connection was created. In such case the =
trigger for=20
requesting IA_PD would be initialization of LAN side physical interface =
(e.g.=20
triggering of Bluetooth PAN profile), as asking for IA_PD at the moment =
of WAN=20
initialization would unnecessarily reserve prefixes by hosts never =
utilizing=20
those.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 5.6. IPv6 over Ethernet and PPP&nbsp;are not =
the only=20
existing technologies and possibly more are coming, Maybe this chapter =
should be=20
generalized? Examples of other technologies are:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; * RFC5121 Transmission of IPv6 via =
the IPv6=20
Convergence Sublayer over IEEE 802.16 Networks</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; * RFC3574 Transition Scenarios for =
3GPP=20
Networks (which is somewhat incomplete now&nbsp;as 3GPP has made some =
rather=20
significant changes to bearer concepts since 2003)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Could CPE router utilize RFC5006 on LAN =
and/or WAN=20
interfaces?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Is stateless DHCPv6 server or DHCPv6 relay =
SHOULD or MUST=20
for CPE router to provide hosts in LAN with access to other =
configuration=20
parameters available from service provider's DHCPv6 =
server?&nbsp;&nbsp;I.e. not=20
just for reasons described in chapter 6.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 8.7. could/would/should this perhaps =
relate/mention to=20
this draft: <A=20
href=3D"http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00"><U><F=
ONT=20
color=3D#0000ff=20
size=3D2>http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00</U></=
FONT></A>&nbsp;?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D511535913-12112008></SPAN><SPAN=20
class=3D511535913-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- As several transition mechanisms are being =
worked on, the=20
8.6 should perhaps mention that DS-Lite is not the only mechanisms that =
may=20
cause this chapter to be updated.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If you wish, I can contribute text from =
cellular=20
perspectives.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Best regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D511535913-12112008>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>Teemu</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-v6ops@ops.ietf.org=20
  [mailto:owner-v6ops@ops.ietf.org] <B>On Behalf Of </B>ext Hemant Singh =

  (shemant)<BR><B>Sent:</B> 30 October, 2008 19:29<BR><B>To:</B> IPv6=20
  Operations<BR><B>Subject:</B> new version of the CPE Rtr draft is =
ready for=20
  review<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial size=3D2><A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-router=
-03.txt">http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-route=
r-03.txt</A></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D248472417-30102008><FONT face=3DArial=20
  size=3D2>Thanks.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D248472417-30102008><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D248472417-30102008><FONT face=3DArial =
size=3D2>Hemant &amp;=20
  Wes</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C944DA.CB59DEDB--



From owner-v6ops@ops.ietf.org  Wed Nov 12 08:19:12 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D1A93A67B6
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 12 Nov 2008 08:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.894
X-Spam-Level: 
X-Spam-Status: No, score=-3.894 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4,
	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 yP+R1Z1xIZ5J
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 12 Nov 2008 08:19:10 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E11993A67A7
	for <v6ops-archive@lists.ietf.org>; Wed, 12 Nov 2008 08:19:09 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L0IP9-000HS2-9c
	for v6ops-data@psg.com; Wed, 12 Nov 2008 16:17:19 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <shemant@cisco.com>)
	id 1L0IP1-000HRD-V7
	for v6ops@ops.ietf.org; Wed, 12 Nov 2008 16:17:16 +0000
X-IronPort-AV: E=Sophos;i="4.33,591,1220227200"; 
   d="scan'208,217";a="27617520"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
  by rtp-iport-1.cisco.com with ESMTP; 12 Nov 2008 16:17:10 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mACGHAmW031774;
	Wed, 12 Nov 2008 11:17:10 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mACGHAus009814;
	Wed, 12 Nov 2008 16:17:10 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 12 Nov 2008 11:17:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C944E2.1D501D3E"
Subject: RE: new version of the CPE Rtr draft is ready for review
Date: Wed, 12 Nov 2008 11:17:10 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42723@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <DC237AE116C10E4C9AD162D6C2EE62FE0148B246@vaebe102.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: new version of the CPE Rtr draft is ready for review
Thread-Index: Ack6tPTn74z3LBV0QLGtfA8Lbv8nYQKGfr4AAANbiAA=
References: <B00EDD615E3C5344B0FFCBA910CF7E1D04E4260B@xmb-rtp-20e.amer.cisco.com> <DC237AE116C10E4C9AD162D6C2EE62FE0148B246@vaebe102.NOE.Nokia.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <teemu.savolainen@nokia.com>, <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 12 Nov 2008 16:17:10.0639 (UTC) FILETIME=[1D9547F0:01C944E2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=30248; t=1226506630; x=1227370630;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20RE=3A=20new=20version=20of=20the=20CPE=20Rtr=20
	draft=20is=20ready=20for=20review
	|Sender:=20
	|To:=20<teemu.savolainen@nokia.com>,=20<v6ops@ops.ietf.org>;
	bh=gV/XQ0UP2ievm6WWpa1d7DU6YityrPb/fjK0xpVEMmM=;
	b=MY8QZlv9EMEYknDvCoeN3ELgUxHvpeAbKnp/gQ6D+moLOJr7kQVbURlFSG
	V/YLSNLcKouKkLRPtZm3jJPZewRskgBih+mLAUvc0lg6iuC3XuU7wbjW7F7k
	RVYVdEUS4T;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C944E2.1D501D3E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Teemu,
=20
Thanks very much for the review.  I and Wes discussed your comments and
here are our responses back in line between <hs> </hs>.

________________________________

From: teemu.savolainen@nokia.com [mailto:teemu.savolainen@nokia.com]=20
Sent: Wednesday, November 12, 2008 10:25 AM
To: Hemant Singh (shemant); v6ops@ops.ietf.org
Subject: RE: new version of the CPE Rtr draft is ready for review


Hi,
=20
I like this document a lot, and really look forward to get this forward.
=20
Few comments:
- 5.4. says that CPE router has failed DHCPv6 address acquisition if
IA_PD option is not included in ADVERTISE/REPLY in stateful DHCPv6 case.
Now considering case where a CPE router is embedded into mobile host
that is attaching to different networks, some of which may mandate
DHCPv6 use and some of which don't: if the mobile host always asks for
IA_PD, but sometimes doesn't get it (due differencies in network
policies), isn't the address acquisition process still successful for
the host itself, but just not for CPE router function of the host? I
mean could this section be clarified to state that in such case the
address acquisition is only partially succesful? And perhaps that in
such case the CPE router can configure the IPv6 address for itself and
at the same time initiate other-but-less-preferred means for providing
Internet connectivity to LAN side, such as fall-back to IPv4-only CPE
router functionality, bridging, (NATting between ULA and global IPv6
address...), or doing ND proxying?
=20
<hs>
Good catch.  This section missed the zero-LAN case.  We can modify text
in this section to say something like "the CPE Router software knows its
running in a zero-LAN hardware device and in such a case of zero-LAN
hardware, if an IA_PD is not asked for by the CPE Router, nor does a
DHCPv6 response received by the CPE Router includes the IA_PD Option,
then there is no error deemed.=20
</hs>
=20
- Is there a reason why ND Proxy (RFC4389) is not mentioned? Because it
is of experimental category?=20
=20
<hs>
Partial reason.  But we have not found a need for the CPE Router to
support ND Proxy just yet.  If any deployment still thinks that the CPE
Router MUST support an ND Proxy, please contact us and we will evaluate
the deployment and the need.
</hs>=20
=20
- 5.5.2. one scenario for WAN initialization before LAN is that LAN side
is not initialized at all without external host first connecting to CPE
router by some technology. Again cellular use case: a mobile has
always-on WAN connectivity for usual uses (VoIP/email/MMS/browsing) and
a host (say PC) initiates WLAN/Bluetooth/USB/whatever connection to a
mobile only much later than initial WAN connection was created. In such
case the trigger for requesting IA_PD would be initialization of LAN
side physical interface (e.g. triggering of Bluetooth PAN profile), as
asking for IA_PD at the moment of WAN initialization would unnecessarily
reserve prefixes by hosts never utilizing those.
=20
<hs>
We can modify this section's 1st para, 2nd line to change from=20
=20
[After the IPv6 address configuration for WAN interface is completed,
the CPE Router configures IPv6 address for LAN interface(s).]
=20
to=20
=20
[After the IPv6 address configuration for WAN interface is completed,
the CPE Router may configure IPv6 address(es) for any LAN interface(s).]

=20
Further, in the 2nd paragraph, a portion of the 1st sentence of the same
section changes from=20
=20
[Once IPv6 address configuration of the LAN interface(s) is complete, ]
=20
to
=20
[When and if  IPv6 address configuration of the LAN interface(s)
completes, ]
=20
</hs>
=20
- 5.6. IPv6 over Ethernet and PPP are not the only existing technologies
and possibly more are coming, Maybe this chapter should be generalized?
Examples of other technologies are:
   * RFC5121 Transmission of IPv6 via the IPv6 Convergence Sublayer over
IEEE 802.16 Networks
   * RFC3574 Transition Scenarios for 3GPP Networks (which is somewhat
incomplete now as 3GPP has made some rather significant changes to
bearer concepts since 2003)
=20
<hs>
We need to think about this one.
<.hs>
=20
- Could CPE router utilize RFC5006 on LAN and/or WAN interfaces?
=20
<hs>
We personally have not accepted this RFC and it's also an experimental
one.  See more below against your DHCPV6 server comments.  Again, unless
a deal-breaking need is found where this RFC MUST be supported by the
CPE Router, we will skip this RFC in our document.=20
</hs>
=20
- Is stateless DHCPv6 server or DHCPv6 relay SHOULD or MUST for CPE
router to provide hosts in LAN with access to other configuration
parameters available from service provider's DHCPv6 server?  I.e. not
just for reasons described in chapter 6.=20
=20
<hs>
Yes, at least a stateless DHCPv6 server is needed to pass Service
Provider options to the LAN device(s).  We think section 5.7 can be
renamed to "DHCPv6 Server" and then we can discuss both stateless and
stateful DHCPv6 servers in the section.
<hs>=20
=20
- 8.7. could/would/should this perhaps relate/mention to this draft:
http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00
<http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00>  ?
=20
<hs>
Wes is on top of this section.  He will read your draft pointer above
and we will reply a little later on this one.
</hs>
=20
- As several transition mechanisms are being worked on, the 8.6 should
perhaps mention that DS-Lite is not the only mechanisms that may cause
this chapter to be updated.
=20
<hs>
We do say in this section that several proposals are out there.
However, we should probably mention more than just DS-Lite.
</hs>
=20
If you wish, I can contribute text from cellular perspectives.=20
=20
<hs>
If you are coming to IETF 73, let's get together and discuss this.  We
are presenting this draft in v6ops.=20
</hs>=20
=20
Thanks.
=20
Kind Regards.
=20
Hemant & Wes.
=20
=20
Best regards,
=20
    Teemu
=20



________________________________

	From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org]
On Behalf Of ext Hemant Singh (shemant)
	Sent: 30 October, 2008 19:29
	To: IPv6 Operations
	Subject: new version of the CPE Rtr draft is ready for review
=09
=09
=09
http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-router-03.txt
	=20
	Thanks.
	=20
	Hemant & Wes


------_=_NextPart_001_01C944E2.1D501D3E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D851013615-12112008><FONT =
face=3DArial=20
color=3D#ff0000 size=3D2>Teemu,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D851013615-12112008><FONT =
face=3DArial=20
color=3D#ff0000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D851013615-12112008><FONT =
face=3DArial=20
color=3D#ff0000 size=3D2>Thanks very much for the review.&nbsp; I and =
Wes=20
discussed&nbsp;your comments&nbsp;and here are our responses back in=20
line&nbsp;between &lt;hs&gt; &lt;/hs&gt;.</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> teemu.savolainen@nokia.com=20
[mailto:teemu.savolainen@nokia.com] <BR><B>Sent:</B> Wednesday, November =
12,=20
2008 10:25 AM<BR><B>To:</B> Hemant Singh (shemant);=20
v6ops@ops.ietf.org<BR><B>Subject:</B> RE: new version of the CPE Rtr =
draft is=20
ready for review<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I like this document a lot, and really look =
forward to get=20
this forward.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Few comments:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 5.4. says that CPE router has failed DHCPv6 =
address=20
acquisition if IA_PD option is not included&nbsp;in ADVERTISE/REPLY in =
stateful=20
DHCPv6 case. Now&nbsp;considering&nbsp;case where a CPE router is =
embedded into=20
mobile host that&nbsp;is attaching to different networks, some of which =
may=20
mandate DHCPv6 use and some of which don't: if the mobile host always =
asks for=20
IA_PD, but sometimes doesn't get it (due differencies in network =
policies),=20
isn't the address acquisition process still successful for&nbsp;the host =
itself,=20
but just not for CPE router function of the host? I mean&nbsp;could this =
section=20
be clarified to state that in such case the address acquisition is only=20
partially succesful? And perhaps that in such case the CPE router can =
configure=20
the IPv6 address for itself and at the same time initiate=20
other-but-less-preferred means for providing Internet connectivity to =
LAN side,=20
such as fall-back to IPv4-only CPE router functionality, bridging, =
(NATting=20
between ULA and global IPv6 address...), or doing ND=20
proxying?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>Good catch.&nbsp;=20
This section missed the zero-LAN case.&nbsp; We can modify text in this =
section=20
to say something like "the CPE Router software knows its running in a =
zero-LAN=20
hardware device and in such a case of zero-LAN hardware, if an IA_PD is =
not=20
asked for by the CPE Router, nor does a DHCPv6 response received by the =
CPE=20
Router includes the IA_PD Option, then there is no error=20
deemed.&nbsp;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;/hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>- Is there a reason why ND Proxy =
(RFC4389) is not=20
mentioned? Because it is of experimental category?<SPAN=20
class=3D851013615-12112008>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D851013615-12112008></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN=20
class=3D851013615-12112008>&lt;hs&gt;</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN class=3D851013615-12112008>Partial =
reason.&nbsp; But we=20
have not found a need for the CPE Router to support ND Proxy just =
yet.&nbsp; If=20
any deployment still thinks that the CPE Router MUST support an ND =
Proxy, please=20
contact us and we will evaluate the deployment and the=20
need.</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN=20
class=3D851013615-12112008>&lt;/hs&gt;&nbsp;</SPAN></FONT></FONT></SPAN><=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 5.5.2. one&nbsp;scenario for WAN =
initialization before=20
LAN is that LAN side is not initialized at all without external host =
first=20
connecting to CPE router by some technology. Again cellular use case: a =
mobile=20
has always-on WAN connectivity for usual uses (VoIP/email/MMS/browsing) =
and a=20
host (say PC) initiates WLAN/Bluetooth/USB/whatever connection to a =
mobile only=20
much later than initial WAN connection was created. In such case the =
trigger for=20
requesting IA_PD would be initialization of LAN side physical interface =
(e.g.=20
triggering of Bluetooth PAN profile), as asking for IA_PD at the moment =
of WAN=20
initialization would unnecessarily reserve prefixes by hosts never =
utilizing=20
those.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>We=20
can&nbsp;modify this section's 1st para, 2nd line to change from=20
</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>[After the IPv6=20
address configuration for WAN interface is completed, the CPE Router =
configures=20
IPv6 address for LAN interface(s).]</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>to=20
</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>[After the IPv6=20
address configuration for WAN interface is completed, the CPE Router may =

configure IPv6 address(es) for any LAN interface(s).]=20
</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial size=3D2><FONT =
color=3D#ff0000>Further,=20
in&nbsp;the 2nd paragraph, a portion of the 1st sentence of the same =
section=20
changes from</FONT> </FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>[Once IPv6=20
address configuration of the LAN interface(s) is complete,=20
]</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>to</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>[When and if=20
&nbsp;IPv6 address configuration of the LAN interface(s)&nbsp; =
completes,=20
]</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;/hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 5.6. IPv6 over Ethernet and PPP&nbsp;are not =
the only=20
existing technologies and possibly more are coming, Maybe this chapter =
should be=20
generalized? Examples of other technologies are:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; * RFC5121 Transmission of IPv6 via =
the IPv6=20
Convergence Sublayer over IEEE 802.16 Networks</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; * RFC3574 Transition Scenarios for =
3GPP=20
Networks (which is somewhat incomplete now&nbsp;as 3GPP has made some =
rather=20
significant changes to bearer concepts since 2003)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>We need to think=20
about this one.</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;.hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Could CPE router utilize RFC5006 on LAN =
and/or WAN=20
interfaces?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff =
size=3D2><FONT=20
color=3D#ff0000>We personally have not accepted this RFC and it's also =
an=20
experimental one.&nbsp; See more below against your DHCPV6=20
server&nbsp;comments.&nbsp; Again, unless a deal-breaking need is found =
where=20
this RFC MUST be supported by the CPE Router, we will skip this RFC in =
our=20
document</FONT>. </FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2>&lt;/hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>- Is stateless DHCPv6 server or DHCPv6 =
relay SHOULD=20
or MUST for CPE router to provide hosts in LAN with access to other=20
configuration parameters available from service provider's DHCPv6=20
server?&nbsp;&nbsp;I.e. not just for reasons described in chapter =
6.<SPAN=20
class=3D851013615-12112008>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D851013615-12112008></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN=20
class=3D851013615-12112008>&lt;hs&gt;</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN class=3D851013615-12112008>Yes, at least=20
a&nbsp;stateless DHCPv6 server is needed&nbsp;to pass Service Provider =
options=20
to the LAN device(s).&nbsp; We think section 5.7 can be renamed to =
"DHCPv6=20
Server" and then we can discuss both stateless and stateful DHCPv6 =
servers in=20
the section.</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN=20
class=3D851013615-12112008>&lt;hs&gt;&nbsp;</SPAN></FONT></FONT></SPAN></=
DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- 8.7. could/would/should this perhaps =
relate/mention to=20
this draft: <A=20
href=3D"http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00"><U><F=
ONT=20
color=3D#0000ff=20
size=3D2>http://tools.ietf.org/html/draft-bellis-dnsext-dnsproxy-00</U></=
FONT></A>&nbsp;?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D511535913-12112008></SPAN><SPAN=20
class=3D511535913-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>Wes is on top of=20
this section.&nbsp; He will read your draft pointer above and&nbsp;we =
will reply=20
a little later on this one.</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;/hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- As several transition mechanisms are being =
worked on, the=20
8.6 should perhaps mention that DS-Lite is not the only mechanisms that =
may=20
cause this chapter to be updated.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>We do say in this=20
section that several proposals are out there.&nbsp; However, we should =
probably=20
mention more than just DS-Lite.</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>&lt;/hs&gt;</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>If you wish, I can contribute text from =
cellular=20
perspectives.<SPAN=20
class=3D851013615-12112008>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D851013615-12112008></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN=20
class=3D851013615-12112008>&lt;hs&gt;</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN class=3D851013615-12112008>If you are =
coming to IETF=20
73, let's get together and discuss this.&nbsp; We are presenting this =
draft in=20
v6ops. </SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial><FONT=20
color=3D#ff0000 size=3D2><SPAN=20
class=3D851013615-12112008>&lt;/hs&gt;&nbsp;</SPAN></FONT></FONT></SPAN><=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#ff0000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2>Thanks.</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>Kind=20
Regards.</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000 =
size=3D2>Hemant &amp;=20
Wes.</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#ff0000=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><SPAN=20
class=3D851013615-12112008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Best regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D511535913-12112008>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>Teemu</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D511535913-12112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-v6ops@ops.ietf.org=20
  [mailto:owner-v6ops@ops.ietf.org] <B>On Behalf Of </B>ext Hemant Singh =

  (shemant)<BR><B>Sent:</B> 30 October, 2008 19:29<BR><B>To:</B> IPv6=20
  Operations<BR><B>Subject:</B> new version of the CPE Rtr draft is =
ready for=20
  review<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial size=3D2><A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-router=
-03.txt">http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-route=
r-03.txt</A></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D248472417-30102008><FONT face=3DArial=20
  size=3D2>Thanks.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D248472417-30102008><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D248472417-30102008><FONT face=3DArial =
size=3D2>Hemant &amp;=20
  Wes</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C944E2.1D501D3E--



From owner-v6ops@ops.ietf.org  Wed Nov 12 15:06:09 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56B613A6988
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 12 Nov 2008 15:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.946
X-Spam-Level: 
X-Spam-Status: No, score=-4.946 tagged_above=-999 required=5
	tests=[AWL=-0.450, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 sV8XTRxZzfXP
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 12 Nov 2008 15:06:08 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1D9233A63D2
	for <v6ops-archive@lists.ietf.org>; Wed, 12 Nov 2008 15:06:07 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L0Oia-000DO5-Kb
	for v6ops-data@psg.com; Wed, 12 Nov 2008 23:01:48 +0000
Received: from [128.18.84.113] (helo=mailgate-internal3.sri.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <edward.jankiewicz@sri.com>)
	id 1L0OiV-000DNY-CQ
	for v6ops@ops.ietf.org; Wed, 12 Nov 2008 23:01:46 +0000
Received: from smssmtp-internal1.sri.com (128.18.84.115)
  by mailgate-internal3.sri.com with SMTP; 12 Nov 2008 23:01:42 -0000
X-AuditID: 80125473-a9cdfbb000000a55-56-491b60550f91
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id E87F121AF2F
	for <v6ops@ops.ietf.org>; Wed, 12 Nov 2008 15:01:41 -0800 (PST)
Received: from [192.168.1.2]
 (nj-76-1-245-180.dhcp.embarqhsd.net [76.1.245.180]) by mail.sri.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0KA8003MKTARSHQC@mail.sri.com> for v6ops@ops.ietf.org; Wed,
 12 Nov 2008 15:01:41 -0800 (PST)
Date: Wed, 12 Nov 2008 18:01:38 -0500
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
Subject: v4v6 coexistence reading list for IETF73
To: IPv6 Operations <v6ops@ops.ietf.org>, ipv6@ietf.org,
 Behave WG <behave@ietf.org>, softwires@ietf.org, int-area-request@ietf.org
Message-id: <491B6052.30200@sri.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_PbgcO43drPIyrlhVihqQDA)"
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is a multi-part message in MIME format.

--Boundary_(ID_PbgcO43drPIyrlhVihqQDA)
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 8BIT

more for my own purposes reading through the alternative drafts, however 
this may be of use to those interested in current work in IPv4-IPv6 
coexistence tools. The work is going on in 3 working groups and some 
drafts will be on on each agenda (some I am guessing will be) are in 
bold. There will also be some general discussion in the intarea meeting. 
The drafts in italic may be obsolete, either merged into other work or 
dropped. And don't forget the paper presented by Randy Bush on Address 
Plus Port 
<https://mice.cs.columbia.edu/getTechreport.php?techreportID=560> that 
may become a draft.

I did not include some related work on tunneling, that maybe should be.
Please comment if I have missed any drafts, or mis-characterized any of 
these as to WG, status or category. Or any other suggestions to make it 
more useful.

	

v6ops WG

	

Behave WG

	

Softwires WG

	

Other or unspecified WG

Framework, scenarios, comparison

	

	

*Draft-baker-behave-v4v6-framework*

	

	

Draft-arkko-townsley-coexistence

	

Draft-wing-nat-pt-replacement-comparison

	

Draft-despres-sam-scenarios

Problem Statements, requirements

	

*Draft-ietf-v6ops-nat64-pb-statement-req*

	

Draft-miyata-behave-prefix64

	

	

	

Draft-jennings-behave-nat6

	

	

	

	

	

Solutions

	

/Draft-despres-v6ops-apbp/

	

*draft-baker-behave-v4v6-translation*

	

*Draft-durand-softwire-dual-stack-lite*

	

Draft-despres-sam

	

*draft-bagnulo-behave-dns64*

	

	

	

*draft-bagnulo-behave-nat64*

	

	

	

Draft-baker-behave-ivi
/Draft-xli-behave-ivi/

	

	

	

*draft-vogt-durand-virtual-ip6-connectivity*

	

	

helpers

	

	

*Draft-denis-behave-v4v6exthdr*

	

	

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


--Boundary_(ID_PbgcO43drPIyrlhVihqQDA)
Content-type: application/msword; name=roadmap.doc
Content-transfer-encoding: base64
Content-disposition: inline; filename=roadmap.doc

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAPQAAAAAA
AAAAEAAAPwAAAAEAAAD+////AAAAADwAAAD/////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
///////////////////////////////////spcEAJWAJBAAA8BK/AAAAAAAAEAAAAAAABgAA
xwoAAA4AYmpiaiJ4IngAAAAAAAAAAAAAAAAAAAAAAAAJBBYANygAAEASAQBAEgEAxwIAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAD//w8A
AAAAAAAAAAAAAAAAAAAAAKQAAAAAAB4FAAAAAAAAHgUAAB4FAAAAAAAAHgUAAAAAAAAeBQAA
AAAAAB4FAAAAAAAAHgUAABQAAAAAAAAAAAAAADIFAAAAAAAAWhMAAAAAAABaEwAAAAAAAFoT
AAAAAAAAWhMAAAwAAABmEwAAZAAAADIFAAAAAAAArBgAAOwAAADWEwAAAAAAANYTAAAAAAAA
1hMAAAAAAADWEwAAAAAAANYTAAAAAAAAsRQAAAAAAACxFAAAAAAAALEUAAAAAAAAKxgAAAIA
AAAtGAAAAAAAAC0YAAAAAAAALRgAAAAAAAAtGAAAAAAAAC0YAAAAAAAALRgAACQAAACYGQAA
aAIAAAAcAABwAAAAURgAABUAAAAAAAAAAAAAAAAAAAAAAAAAHgUAAAAAAACxFAAAAAAAAAAA
AAAAAAAAAAAAAAAAAACxFAAAAAAAALEUAAAAAAAAsRQAAAAAAACxFAAAAAAAAFEYAAAAAAAA
AAAAAAAAAAAeBQAAAAAAAB4FAAAAAAAA1hMAAAAAAAAAAAAAAAAAANYTAADbAAAAZhgAABYA
AABfFQAAAAAAAF8VAAAAAAAAXxUAAAAAAACxFAAAmgAAAB4FAAAAAAAA1hMAAAAAAAAeBQAA
AAAAANYTAAAAAAAAKxgAAAAAAAAAAAAAAAAAAF8VAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsRQAAAAAAAArGAAAAAAAAAAAAAAAAAAA
XxUAAAAAAAAAAAAAAAAAAF8VAAAAAAAAHgUAAAAAAAAeBQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAXxUAAAAAAADWEwAA
AAAAAMoTAAAMAAAAkIyTdhlFyQEAAAAAAAAAAFoTAAAAAAAASxUAAAoAAABfFQAAAAAAAAAA
AAAAAAAA5xUAAEQCAAB8GAAAMAAAAKwYAAAAAAAAXxUAAAAAAABwHAAAAAAAAFUVAAAAAAAA
cBwAAAAAAABfFQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABfFQAAFAAAAHAcAAAAAAAAAAAAAAAAAAAeBQAA
AAAAAHMVAAB0AAAAsRQAAAAAAACxFAAAAAAAAF8VAAAAAAAAsRQAAAAAAACxFAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsRQAAAAAAACxFAAAAAAAALEUAAAAAAAA
URgAAAAAAABRGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAVRUAAAoA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAALEUAAAAAAAAsRQAAAAAAACxFAAA
AAAAAKwYAAAAAAAAsRQAAAAAAACxFAAAAAAAALEUAAAAAAAAsRQAAAAAAAAAAAAAAAAAADIF
AAAAAAAAMgUAAAAAAAAyBQAAJAkAAFYOAAAEBQAAMgUAAAAAAAAyBQAAAAAAADIFAAAAAAAA
Vg4AAAAAAAAyBQAAAAAAADIFAAAAAAAAMgUAAAAAAAAeBQAAAAAAAB4FAAAAAAAAHgUAAAAA
AAAeBQAAAAAAAB4FAAAAAAAAHgUAAAAAAAD/////AAAAAAIADAEAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAd2Nm9wcyBXRwdCZWhhdmUgV0cHU29mdHdpcmVzIFdH
B090aGVyIG9yIHVuc3BlY2lmaWVkIFdHBwdGcmFtZXdvcmssIHNjZW5hcmlvcywgY29tcGFy
aXNvbgcHRHJhZnQtYmFrZXItYmVoYXZlLXY0djYtZnJhbWV3b3JrBwdEcmFmdC1hcmtrby10
b3duc2xleS1jb2V4aXN0ZW5jZQcHBwdEcmFmdC13aW5nLW5hdC1wdC1yZXBsYWNlbWVudC1j
b21wYXJpc29uB0RyYWZ0LWRlc3ByZXMtc2FtLXNjZW5hcmlvcwcHUHJvYmxlbSBTdGF0ZW1l
bnRzLCAgcmVxdWlyZW1lbnRzB0RyYWZ0LWlldGYtdjZvcHMtbmF0NjQtcGItc3RhdGVtZW50
LXJlcQdEcmFmdC1taXlhdGEtYmVoYXZlLXByZWZpeDY0BwcHBwcHRHJhZnQtamVubmluZ3Mt
YmVoYXZlLW5hdDYHBwcHBwcHBwcHU29sdXRpb25zB0RyYWZ0LWRlc3ByZXMtdjZvcHMtYXBi
cAdkcmFmdC1iYWtlci1iZWhhdmUtdjR2Ni10cmFuc2xhdGlvbgdEcmFmdC1kdXJhbmQtc29m
dHdpcmUtZHVhbC1zdGFjay1saXRlB0RyYWZ0LWRlc3ByZXMtc2FtBwcHB2RyYWZ0LWJhZ251
bG8tYmVoYXZlLWRuczY0BwcHBwcHZHJhZnQtYmFnbnVsby1iZWhhdmUtbmF0NjQHBwcHBwdE
cmFmdC1iYWtlci1iZWhhdmUtaXZpDURyYWZ0LXhsaS1iZWhhdmUtaXZpBwcHBwcHZHJhZnQt
dm9ndC1kdXJhbmQtdmlydHVhbC1pcDYtY29ubmVjdGl2aXR5BwcHB5NoZWxwZXJzlAcHRHJh
ZnQtZGVuaXMtYmVoYXZlLXY0djZleHRoZHIHBwcHDQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAABgAATggAAFoIAABcCAAAfggAAKEIAACjCAAAywgAAOkI
AAALCQAAMwkAAIMJAACcCQAAwAkAAOYJAAD3CQAA+AkAAPsJAAAWCgAAGwoAADYKAABSCgAA
ZwoAAGwKAACXCgAApQoAAMMKAADGCgAAxwoAAPz4/PD8+On4/OH82fDh/NL88Pzw/Nn88Pzw
/M4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
BhZo7gwYAAAMFWj0MfIAFmj0MfIAAA8VaPQx8gAWaPQx8gA2CIEPFWjvTm8AFmj0MfIANQiB
DBVoDX5OABZoDX5OAAAPFWgeNOgAFmj0MfIANQiBBhZoDX5OAAAGFmj0MfIAHAAGAAABCAAA
CggAABQIAAAhCAAAOQgAADoIAABbCAAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAA
AAAAAAAAAAAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAABCAAAAAAAAAAAAAAAA+QAAAAAA
AAAAAAAAAAAAAAAAAAAAAAC2AABrZAAAAAAWJAEXJAFJZgEAAAAClmwABdYYBAEAAAQBAAAE
AQAABAEAAAQBAAAEAQAACNZyAAWU/1EFlBGIHRQooDIABr0FAAAAAAAAAAAAAAAAAAAAAAAG
QwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAA
AAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOABE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8E
AQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYDDDMVNgEX9gMAABj2AwAAGtYUAAAA/wAA
AP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAA
AP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQUDAAA01gYAAQoDbABh9gMAAHl0
9DHyAAYAABYkAUlmAQAAAAAHAAYAAMcKAAD9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAABAQFbCAAAXAgAAH4I
AAB/CAAAoAgAAKEIAACiCAAAowgAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAA
AAAAAAAAAPkAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAPkAAAAAAAAA
AAAAAAAAAAAAAAAAuAAAa2SZAAAAFiQBFyQBSWYBAAAAApZsAAM0AQXWGAQBAAAEAQAABAEA
AAQBAAAEAQAABAEAAAjWcgAFlP9RBZQRiB0UKKAyYAa9BQAAAAAAAAAAAAAAAAAAAAAABkMM
AAAAAAAAAAAAAAAAAAAAAAAG9AsAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAA
AAAABowKAAAAAAAAAAAAAAAAAAAAAAp0AADgARPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEA
AAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAABT2AwwzFTYBF/YDAAAY9gMAABrWFAAAAP8AAAD/
AAAA/wAAAP8AAAD/G9YUAAAA/wAAAP8AAAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAAAP8AAAD/
AAAA/x3WFAAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEFAwAANNYGAAEKA2wAYfYDAAB5dPQx
8gAGAAAWJAFJZgEAAAAAB6MIAADMCAAA6AgAAOkIAAALCQAAMwkAAFAJAABRCQAAUgkAAPkA
AAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAAVAAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAA
AAAAAAAAAAAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAKUAAGtkOgEAABYkARckAUlmAQAAAAKWbAADNAEF1hgE
AQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1lwABJT/UQWUERQooDIgBr0FAAAAAAAAAAAAAAAA
AAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAaAFgAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAA
AAAAAAAAAAAAAAp0AADgARPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA
/wQBAAAAAAD/BAEAABT2AwwzFTYBF/YDAAAY9gMAABrWEAAAAP8AAAD/AAAA/wAAAP8b1hAA
AAD/AAAA/wAAAP8AAAD/HNYQAAAA/wAAAP8AAAD/AAAA/x3WEAAAAP8AAAD/AAAA/wAAAP80
1gYAAQUDAAA01gYAAQoDbABh9gMAAHl0DX5OAAYAABYkAUlmAQAAAAAIUgkAAFMJAABUCQAA
VQkAAHAJAABxCQAAcgkAAEcAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAA
AEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAYAABYkAUlmAQAAALgAAGtk0wEAABYkARckAUlmAQAAAAKWbAADNAEF1hgE
AQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1nIABZT/UQWUEYgdFCigMmAGvQUAAAAAAAAAAAAA
AAAAAAAAAAZDDAAAAAAAAAAAAAAAAAAAAAAABvQLAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAA
AAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAKdAAA4AET1jAAAAD/BAEAAAAAAP8E
AQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU9gMMMxU2ARf2AwAAGPYDAAAa
1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HNYUAAAA/wAA
AP8AAAD/AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABBQMAADTWBgABCgNs
AGH2AwAAeXT0MfIAAAZyCQAAcwkAAHQJAAB1CQAAdgkAAHcJAAB4CQAARwAAAAAAAAAAAAAA
AEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAFiQBSWYBAAAAuAAAa2R0
AgAAFiQBFyQBSWYBAAAAApZsAAM0AQXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWcgAF
lP9RBZQRiB0UKKAyIAa9BQAAAAAAAAAAAAAAAAAAAAAABkMMAAAAAAAAAAAAAAAAAAAAAAAG
9AsAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAA
AAAAAAp0AADgARPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAABT2AwwzFTYBF/YDAAAY9gMAABrWFAAAAP8AAAD/AAAA/wAAAP8AAAD/G9YUAAAA
/wAAAP8AAAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAAAP8AAAD/AAAA/x3WFAAAAP8AAAD/AAAA
/wAAAP8AAAD/NNYGAAEFAwAANNYGAAEKA2wAYfYDAAB5dPQx8gAABngJAAB5CQAAgwkAAJwJ
AADACQAA5gkAAPgJAABHAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAGAAAWJAFJZgEAAAC4AABrZBUDAAAWJAEXJAFJZgEAAAAClmwAAzQBBdYYBAEA
AAQBAAAEAQAABAEAAAQBAAAEAQAACNZyAAWU/1EFlBGIHRQooDIgBr0FAAAAAAAAAAAAAAAA
AAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAA
AAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOABE9YwAAAA/wQBAAAAAAD/BAEA
AAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYDDDMVNgEX9gMAABj2AwAAGtYU
AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/
AAAA/wAAAP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQUDAAA01gYAAQoDbABh
9gMAAHl09DHyAAAG+AkAAPkJAAD6CQAA+wkAABYKAAAXCgAAGAoAAEcAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAABYkAUlmAQAAALgAAGtktgMA
ABYkARckAUlmAQAAAAKWbAADNAEF1hgEAQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1nIABZT/
UQWUEYgdFCigMmAGvQUAAAAAAAAAAAAAAAAAAAAAAAZDDAAAAAAAAAAAAAAAAAAAAAAABvQL
AAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAA
AAAKdAAA4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA
/wQBAAAU9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8A
AAD/AAAA/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8A
AAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXT0MfIAAAYYCgAAGQoAABoKAAAbCgAA
NgoAADcKAAA4CgAARwAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAA
AAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAABgAAFiQBSWYBAAAAuAAAa2RXBAAAFiQBFyQBSWYBAAAAApZsAAM0AQXWGAQBAAAE
AQAABAEAAAQBAAAEAQAABAEAAAjWcgAFlP9RBZQRiB0UKKAyIAa9BQAAAAAAAAAAAAAAAAAA
AAAABkMMAAAAAAAAAAAAAAAAAAAAAAAG9AsAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAA
AAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAp0AADgARPWMAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAABT2AwwzFTYBF/YDAAAY9gMAABrWFAAA
AP8AAAD/AAAA/wAAAP8AAAD/G9YUAAAA/wAAAP8AAAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAA
AP8AAAD/AAAA/x3WFAAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEFAwAANNYGAAEKA2wAYfYD
AAB5dPQx8gAABjgKAAA5CgAAOgoAADsKAABSCgAAZwoAAGgKAABpCgAARwAAAAAAAAAAAAAA
AEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAAAAAAAAAAAGAAAWJAFJZgEAAAC4AABrZPgEAAAW
JAEXJAFJZgEAAAAClmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQBAAAEAQAACNZyAAWU/1EF
lBGIHRQooDIgBr0FAAAAAAAAAAAAAAAAAAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAA
AAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAA
CnQAAOABE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8E
AQAAFPYDDDMVNgEX9gMAABj2AwAAGtYUAAAA/wAAAP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA
/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA
/wAAAP801gYAAQUDAAA01gYAAQoDbABh9gMAAHl09DHyAAAHaQoAAGoKAABrCgAAbAoAAJcK
AACYCgAAmQoAAEcAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAADgAAAAA
AAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAAAAAAAAAAkAABYkAUlmAQAAAGdk
HjToAAYAABYkAUlmAQAAALgAAGtkmQUAABYkARckAUlmAQAAAAKWbAADNAEF1hgEAQAABAEA
AAQBAAAEAQAABAEAAAQBAAAI1nIABZT/UQWUEYgdFCigMiAGvQUAAAAAAAAAAAAAAAAAAAAA
AAZDDAAAAAAAAAAAAAAAAAAAAAAABvQLAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAA
AAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAKdAAA4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA
/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/
AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/
AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAA
eXT0MfIAAAaZCgAAmgoAAKQKAAClCgAAwwoAAMQKAADFCgAARwAAAAAAAAAAAAAAAEEAAAAA
AAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAFiQBSWYBAAAAuAAAa2Q6BgAAFiQB
FyQBSWYBAAAAApZsAAM0AQXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWcgAFlP9RBZQR
iB0UKKAyIAa9BQAAAAAAAAAAAAAAAAAAAAAABkMMAAAAAAAAAAAAAAAAAAAAAAAG9AsAAAAA
AAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAp0
AADgARPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEA
ABT2AwwzFTYBF/YDAAAY9gMAABrWFAAAAP8AAAD/AAAA/wAAAP8AAAD/G9YUAAAA/wAAAP8A
AAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAAAP8AAAD/AAAA/x3WFAAAAP8AAAD/AAAA/wAAAP8A
AAD/NNYGAAEFAwAANNYGAAEKA2wAYfYDAAB5dPQx8gAABsUKAADGCgAAxwoAAEgAAAAAAAAA
AAAAAABGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAEAAAC2AABrZNsGAAAWJAEXJAFJZgEAAAAClmwABdYYBAEAAAQBAAAE
AQAABAEAAAQBAAAEAQAACNZyAAWU/1EFlBGIHRQooDIABr0FAAAAAAAAAAAAAAAAAAAAAAAG
QwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAA
AAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOABE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8E
AQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYDDDMVNgEX9gMAABj2AwAAGtYUAAAA/wAA
AP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAA
AP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQUDAAA01gYAAQoDbABh9gMAAHl0
9DHyAAACNQAxkGgBHTACOnDtKOMAH7DgPSCw0C8hsKAFIrCgBSOQCAckkAgHJbAAABew0AIY
sNACDJDQAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACXABYkARckAUlmAQAAAAGWAAAhdgAF
aAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMM
I3YCA/QLI3YDBYwKOlYPAAKWbAAKdAAA4AEU9gMMMxU2ARj2AwAANdYFAAEDvQU11gUBAgND
DDXWBQIDA/QLNdYFAwUDjAp5dPQx8gCfABYkARckAUlmAQAAAAGWAAAhdgAFaAE11gUAAQO9
BTXWBQECA0MMNdYFAgMD9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMMI3YCA/QLI3YD
BYwKOlYPAAKWbAADNAEKdAAA4AEU9gMMMxU2ARj2AwAAK9YCAAM11gUAAQO9BTXWBQECA0MM
NdYFAgMD9As11gUDBQOMCnl09DHyAJcAFiQBFyQBSWYBAAAAAZYAACF2AARoATXWBQABA70F
NdYFAQIDQww11gUCAwOAFjXWBQMEA4wKI3YAAb0FI3YBAkMMI3YCA4AWI3YDBIwKOlYPAAKW
bAADNAEKdAAA4AEU9gMMMxU2ARj2AwAAK9YCAAE11gUAAQO9BTXWBQECA0MMNdYFAgMDgBY1
1gUDBAOMCnl0DX5OAJ8AFiQBFyQBSWYBAAAAAZYAACF2AAVoATXWBQABA70FNdYFAQIDQww1
1gUCAwP0CzXWBQMEA4wKNdYFBAUDjAojdgABvQUjdgECQwwjdgID9AsjdgMFjAo6Vg8AApZs
AAM0AQp0AADgART2AwwzFTYBGPYDAAAr1gIAAzXWBQABA70FNdYFAQIDQww11gUCAwP0CzXW
BQMFA4wKeXT0MfIAnwAWJAEXJAFJZgEAAAABlgAAIXYABWgBNdYFAAEDvQU11gUBAgNDDDXW
BQIDA/QLNdYFAwQDjAo11gUEBQOMCiN2AAG9BSN2AQJDDCN2AgP0CyN2AwWMCjpWDwAClmwA
AzQBCnQAAOABFPYDDDMVNgEY9gMAACvWAgABNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYF
AwUDjAp5dPQx8gCfABYkARckAUlmAQAAAAGWAAAhdgAFaAE11gUAAQO9BTXWBQECA0MMNdYF
AgMD9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMMI3YCA/QLI3YDBYwKOlYPAAKWbAAD
NAEKdAAA4AEU9gMMMxU2ARj2AwAAK9YCAAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUD
BQOMCnl09DHyAJ8AFiQBFyQBSWYBAAAAAZYAACF2AAVoATXWBQABA70FNdYFAQIDQww11gUC
AwP0CzXWBQMEA4wKNdYFBAUDjAojdgABvQUjdgECQwwjdgID9AsjdgMFjAo6Vg8AApZsAAM0
AQp0AADgART2AwwzFTYBGPYDAAAr1gIAAzXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMF
A4wKeXT0MfIAnwAWJAEXJAFJZgEAAAABlgAAIXYABWgBNdYFAAEDvQU11gUBAgNDDDXWBQID
A/QLNdYFAwQDjAo11gUEBQOMCiN2AAG9BSN2AQJDDCN2AgP0CyN2AwWMCjpWDwAClmwAAzQB
CnQAAOABFPYDDDMVNgEY9gMAACvWAgABNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwUD
jAp5dPQx8gCfABYkARckAUlmAQAAAAGWAAAhdgAFaAE11gUAAQO9BTXWBQECA0MMNdYFAgMD
9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMMI3YCA/QLI3YDBYwKOlYPAAKWbAADNAEK
dAAA4AEU9gMMMxU2ARj2AwAAK9YCAAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBQOM
Cnl09DHyAJ8AFiQBFyQBSWYBAAAAAZYAACF2AAVoATXWBQABA70FNdYFAQIDQww11gUCAwP0
CzXWBQMEA4wKNdYFBAUDjAojdgABvQUjdgECQwwjdgID9AsjdgMFjAo6Vg8AApZsAAM0AQp0
AADgART2AwwzFTYBGPYDAAAr1gIAATXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMFA4wK
eXT0MfIAnwAWJAEXJAFJZgEAAAABlgAAIXYABWgBNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QL
NdYFAwQDjAo11gUEBQOMCiN2AAG9BSN2AQJDDCN2AgP0CyN2AwWMCjpWDwAClmwAAzQBCnQA
AOABFPYDDDMVNgEY9gMAACvWAgABNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwUDjAp5
dPQx8gCXABYkARckAUlmAQAAAAGWAAAhdgAFaAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As1
1gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMMI3YCA/QLI3YDBYwKOlYPAAKWbAAKdAAA4AEU
9gMMMxU2ARj2AwAANdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwUDjAp5dPQx8gAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAhgIUABIAAQCcAA8ABAAAAAAAAAAAAAQAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAQPH/AgBAAAwEAAAAAAAAAAAGAE4AbwByAG0A
YQBsAAAAAgAAABgAQ0oYAF9IAQRhShgAbUgJBHNICQR0SAkEAAAAAAAAAAAAAAAAAAAAAAAA
RABBQPL/oQBEAAwFAAAAAAAAAAAWAEQAZQBmAGEAdQBsAHQAIABQAGEAcgBhAGcAcgBhAHAA
aAAgAEYAbwBuAHQAAAAAAFIAaUDz/7MAUgAMBQAAAAAAAAAADABUAGEAYgBsAGUAIABOAG8A
cgBtAGEAbAAAABwAF/YDAAA01gYAAQoDbAA01gYAAQUDAABh9gMAAAIACwAAACgAa0D0/8EA
KAAABQAAAAAAAAAABwBOAG8AIABMAGkAcwB0AAAAAgAAAAAAAABqAJpAswDzAGoADAQAAO0o
4wAAAAoAVABhAGIAbABlACAARwByAGkAZAAAADcAOlYPABPWMAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAACAA8AAABCACdAogABAUIADAUAAPQx
8gAAABEAQwBvAG0AbQBlAG4AdAAgAFIAZQBmAGUAcgBlAG4AYwBlAAAACABDShAAYUoQADwA
HkABABIBPAAMBQAA9DHyAAAADABDAG8AbQBtAGUAbgB0ACAAVABlAHgAdAAAAAIAEQAIAENK
FABhShQAQABqQBEBEgFAAAwFAAD0MfIAAAAPAEMAbwBtAG0AZQBuAHQAIABTAHUAYgBqAGUA
YwB0AAAAAgASAAYANQiBXAiBSACZQAEAMgFIAAwFAAD0MfIAAAAMAEIAYQBsAGwAbwBvAG4A
IABUAGUAeAB0AAAAAgATABQAQ0oQAE9KAwBRSgMAXkoDAGFKEAAAAAAAxwIAAAsAACgAAAkA
/////wAAAAABAAAACgAAABQAAAAhAAAAOQAAADoAAABbAAAAXAAAAH4AAAB/AAAAoAAAAKEA
AACiAAAAowAAAMwAAADoAAAA6QAAAAsBAAAzAQAAUAEAAFEBAABSAQAAUwEAAFQBAABVAQAA
cAEAAHEBAAByAQAAcwEAAHQBAAB1AQAAdgEAAHcBAAB4AQAAeQEAAIMBAACcAQAAwAEAAOYB
AAD4AQAA+QEAAPoBAAD7AQAAFgIAABcCAAAYAgAAGQIAABoCAAAbAgAANgIAADcCAAA4AgAA
OQIAADoCAAA7AgAAUgIAAGcCAABoAgAAaQIAAGoCAABrAgAAbAIAAJcCAACYAgAAmQIAAJoC
AACkAgAApQIAAMMCAADEAgAAxQIAAMYCAADJAgAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAA
AAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQ
AAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEA
ANAAAAAAIAGZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqQAAAAAwAAAAAAAAAIAAAACA
AQAAqAAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAACoAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAAqAAAAAAgAKkAAAAAMAAAAAAAAACA
AAAAgAEAAKgAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAACsAAAAACAAqSAAAAAwAAAAAAAA
AIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAA
AAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAA
AAAAAACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAw
AAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAA
ADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkA
AAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpIAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAA
qQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAA
IACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAA
AAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpIAAAADAAAAAAAAAAgAAAAIABAADQ
AAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEA
ANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACA
AQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAakAAAAAMAAAAAAAAACA
AAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAA
AIAAAACAAQAA0AAAAAAgAZkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpIAAAADAAAAAA
AAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAA
AAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAw
AAAAAAAAAIAAAACAAQAA0AAAAAAgAZkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpIAAA
ADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkA
AAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAA
qQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAA
IACpIAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAA
AAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAAACpAAAAADAAAAAAAAAAgAAAAIABAADQ
AAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEA
ANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqSAAAAAwAAAAAAAAAIAAAACA
AQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACA
AAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqQAAAAAwAAAAAAAA
AIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAA
AAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAA
AAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAmAAAAAAw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAAAAAAB/AAAAoAAAAKEAAADoAAAA6QAAAAsBAAAzAQAA
UAEAAFEBAABSAQAAVAEAAFUBAABwAQAAcQEAAHIBAAB2AQAAdwEAAHgBAACDAQAAnAEAAMAB
AADmAQAA+AEAAPoBAAD7AQAAFgIAABcCAAAYAgAANwIAADgCAABoAgAAaQIAAGsCAABsAgAA
lwIAAJgCAACZAgAAxAIAAMUCAADJAgAAWtEAMAAQAAAAAAAAAQAAAAoAAAABAAAAOGCaB1rR
ADABAAAAAAAAAAEAAAAbAAAAAgAAAOSLCgdY0QAwAgAAAAAAAAACAAAAAQAAAAMAAAC4RSAF
WtEAMAIQAAAAAAAAAgAAAAEAAAADAAAAuEUzBwhAAAAAAAAAAAAAAAAAAAAAAB0wtgAAAAMA
IAVa0QAwAQAAAAAAAAABAAAACgABAAAAAAAAAKAHWtEAMAEQAAAAAAAAAQAAAAoAAQAAAAAA
AACgB1rRADAFAAAAAAAAAAEAAAATAAEAAAAAAAAAIAdY0QAwAQAAAAAAAAABAAAACgABAAAA
AAAAAKABWNEAMAYAAAAAAAAAAQAAABcAAAAHAAAAcIwKB1rRADACAAAAAAAAAAEAAAAKAAEA
AAAAAAAAoAda0QAwAgAAAAAAAAABAAAACgABAAAAAAAAAKAHWNEAMAIAAAAAAAAAAQAAAAoA
AQAAAAAAAACgAVjRADACAAAAAAAAAAEAAAAKAAAAAwAAAAQXmgdY0QAwCwAAAAAAAAABAAAA
EwAAAAwAAAD8jAoHWtEAMAMAAAAAAAAAAQAAAA4AAAAEAAAA6LSoB1rRADAAAAAAAAAAAAEA
AAAGAAEAAAAAAAAAoAdY0QAwDgAAAAAAAAABAAAAEQAAAA8AAABQjQoHWtEAMAAAAAAAAAAA
AgAAAAEAAQAAAAAAAACgB1rRADAAAAAAAAAAAAIAAAABAAEAAAAAAAAAoAda0QAwABAAAAAA
AAACAAAAAQABAAAAAAAAAKAHWtEAMAcQAAAAAAAAAQAAAAIAAQAAAAAAAACgB1rRADATEAAA
AAAAAAEAAAANAAAAFAAAANyNCgda0QAwCAAAAAAAAAABAAAAAgABAAAAAAAAAKAHWtEAMAgA
AAAAAAAAAQAAAAIAAQAAAAAAAACgB1rRADAIEAAAAAAAAAEAAAACAAEAAAAAAAAAoAda0QAw
CAAAAAAAAAABAAAAAgAAAAkAAACsF5oHWtEAMBgAAAAAAAAAAQAAAAkAAAAZAAAAaI4KB1rR
ADAJEAAAAAAAAAEAAAACAAAACgAAAMgXmgdY0QAwGgAAAAAAAAABAAAACAAAABsAAACgjgoH
WtEAMBQAAAAAAAAAAQAAAAgAAAAVAAAAoNMzB1jRADAcAAAAAAAAAAEAAAAHAAAAHQAAAPQr
Cgda0QAwHgAAAAAAAAABAAAABgABAAAAAAAAACAHWNEAMB4AAAAAAAAAAQAAAAUAAQAAAAAA
AAAgAVjRADAPEAAAAAAAAAIAAAAKAAEAAAAAAAAAIAFY0QAwHQAAAAAAAAACAAAAAgABAAAA
AAAAACABWNEAMCEAAAAAAAAAAQAAAAMAAAAiAAAAgCwKB1rRADAZAAAAAAAAAAEAAAACAAAA
GgAAACzUMwdY0QAwIwAAAAAAAAABAAAAAgAAACQAAAC4LAoHWpEAMAAQAAAAAAAAAQAAAAAA
AAAAAAAAQArCBwAGAADHCgAABgAAAAAGAABbCAAAowgAAFIJAAByCQAAeAkAAPgJAAAYCgAA
OAoAAGkKAACZCgAAxQoAAMcKAAAHAAAACQAAAAoAAAALAAAADAAAAA0AAAAOAAAADwAAABAA
AAARAAAAEgAAABMAAAAABgAAxwoAAAgAAAAPAADwOAAAAAAABvAYAAAAAggAAAIAAAABAAAA
AQAAAAEAAAACAAAAQAAe8RAAAAD//wAAAAD/AICAgAD3AAAQAA8AAvCSAAAAEAAI8AgAAAAB
AAAAAQQAAA8AA/AwAAAADwAE8CgAAAABAAnwEAAAAAAAAAAAAAAAAAAAAAAAAAACAArwCAAA
AAAEAAAFAAAADwAE8EIAAAASAArwCAAAAAEEAAAADgAAUwAL8B4AAAC/AQAAEADLAQAAAAD/
AQAACAAEAwkAAAA/AwEAAQAAABHwBAAAAAEAAAAAAAAABwAAAAkAAAARAAAAEwAAABQAAAAd
AAAAHgAAACAAAAA2AAAAOAAAAIUAAACfAAAArgAAALEAAADSAAAA5wAAAMYBAADlAQAA7AEA
APcBAABOAgAAUQIAAGMCAABmAgAAyQIAAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAH
ABwABwAcAAcAHAAHABwABwAcAAcAAAAAAMkCAAAHAAAAAADJAgAABwABAMsULDUAAAAAAAAA
AAABAgACABcAAAAEAAAACAAAAOUAAAAAAAAAFgAAAMhhFQDuDBgA0BQfAP02JAA4TT8A6W1B
AA1+TgBMAV0A705vAOVZcQDjVKoAUXytAENTsQBbV7EAGUOzAO0o4wDFZ+cAHjToANwR6gD0
MfIArS31AMxZ/AAzZP4AAAAAAAEAAAAKAAAAFAAAACEAAAA5AAAAOgAAAFsAAABcAAAAfgAA
AH8AAACgAAAAoQAAAKIAAACjAAAAzAAAAOgAAADpAAAACwEAADMBAABQAQAAUQEAAFIBAABT
AQAAVAEAAFUBAABwAQAAcQEAAHIBAABzAQAAdAEAAHUBAAB2AQAAdwEAAHgBAAB5AQAAgwEA
AJwBAADAAQAA5gEAAPgBAAD5AQAA+gEAAPsBAAAWAgAAFwIAABgCAAAZAgAAGgIAABsCAAA2
AgAANwIAADgCAAA5AgAAOgIAADsCAABnAgAAaAIAAGkCAABqAgAAawIAAGwCAACXAgAAmAIA
AJkCAACaAgAApAIAAKUCAADDAgAAxAIAAMUCAADGAgAAyQIAAAAAAAACAQAAAgEAAAIBAAAC
AQAAAgEAAJ4BAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAACAQAAAgEAAAIBAAACAQAAngEA
AAIBAAACAQAAAgEAAAIBAAACAQAAngEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAAIBAAAC
AQAAAgEAAAIBAAACAQAAngEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAAIBAAACAQAAAgEA
AAIBAAACAQAAngEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAAIBAAACAQAAAgEAAAIBAAAC
AQAAngEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAAIBAAACAQAAAgEAAAIBAAACAQAAlgEA
AP9ADYABADgCAAA4AgAAXHgSAwEAAAA4AgAAAAACADgCAACUERQoAhAAAAAAAAAAxwIAALAA
ABAAQAAA//8BAAAABwBVAG4AawBuAG8AdwBuAP//AQAIAAAAAAAAAAAAAAD//wEAAAAAAP//
AAACAP//AAAAAP//AAACAP//AAAAAAQAAABHFpABAAACAgYDBQQFAgMEh3oAIAAAAIAIAAAA
AAAAAP8BAAAAAAAAVABpAG0AZQBzACAATgBlAHcAIABSAG8AbQBhAG4AAAA1FpABAgAFBQEC
AQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5AG0AYgBvAGwAAAAzJpABAAACCwYE
AgICAgIEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAAQQByAGkAYQBsAAAANSaQAQAAAgsGBAMF
BAQCBId6AGEAAACACAAAAAAAAAD/AQEAAAAAAFQAYQBoAG8AbQBhAAAAIgAEAHEIiBgA8NAC
AABoAQAAAADwWstGdWTLZgAAAAAFADUCAABqAAAAXQIAAAEAAQAAAAQAAxAFAAAAagAAAF0C
AAABAAEAAAAFAAAAAAAAACEDAPAQAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAKAFCAe0ALQAgYFyNAAAEAAZAGQAAAAZAAAAxgIAAMYCAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAA
AAAAAAAAADKDEQDwEAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABLUAAAAAAp8P8P
AQABPwAA5AQAAP///3////9/////f////3////9/////f////3/tKOMAAAAAADIAAAAAAAAA
AAAAAAAAAQAAAP//EgAAAAAAAAAJAEIAZQBoAGEAdgBlACAAVwBHAAAAAAAAAA0AZQBkACAA
agBhAG4AawBpAGUAdwBpAGMAegANAGUAZAAgAGoAYQBuAGsAaQBlAHcAaQBjAHoAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/v8AAAUBAgAAAAAAAAAAAAAA
AAAAAAAAAQAAAOCFn/L5T2gQq5EIACsns9kwAAAAgAEAABEAAAABAAAAkAAAAAIAAACYAAAA
AwAAAKwAAAAEAAAAuAAAAAUAAADQAAAABgAAANwAAAAHAAAA6AAAAAgAAAD4AAAACQAAABAB
AAASAAAAHAEAAAoAAAA8AQAADAAAAEgBAAANAAAAVAEAAA4AAABgAQAADwAAAGgBAAAQAAAA
cAEAABMAAAB4AQAAAgAAAOQEAAAeAAAADAAAAEJlaGF2ZSBXRwAAAB4AAAAEAAAAAAAAAB4A
AAAQAAAAZWQgamFua2lld2ljegAAAB4AAAAEAAAAAAAAAB4AAAAEAAAAAAAAAB4AAAAIAAAA
Tm9ybWFsAAAeAAAAEAAAAGVkIGphbmtpZXdpY3oAAAAeAAAABAAAADUAAAAeAAAAGAAAAE1p
Y3Jvc29mdCBPZmZpY2UgV29yZAAAAEAAAAAAfvntTgAAAEAAAAAAoHlBHUTJAUAAAAAALk5p
GUXJAQMAAAABAAAAAwAAAGoAAAADAAAAXQIAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAFAQIAAAAAAAAAAAAAAAAAAAAAAAEA
AAAC1c3VnC4bEJOXCAArLPmuMAAAAAABAAAMAAAAAQAAAGgAAAAPAAAAcAAAAAUAAACMAAAA
BgAAAJQAAAARAAAAnAAAABcAAACkAAAACwAAAKwAAAAQAAAAtAAAABMAAAC8AAAAFgAAAMQA
AAANAAAAzAAAAAwAAADiAAAAAgAAAOQEAAAeAAAAFAAAAFNSSSBJbnRlcm5hdGlvbmFsAAAA
AwAAAAUAAAADAAAAAQAAAAMAAADGAgAAAwAAAA8nCwALAAAAAAAAAAsAAAAAAAAACwAAAAAA
AAALAAAAAAAAAB4QAAABAAAACgAAAEJlaGF2ZSBXRwAMEAAAAgAAAB4AAAAGAAAAVGl0bGUA
AwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAgAAAAMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkA
AAAKAAAACwAAAAwAAAANAAAADgAAAA8AAAAQAAAAEQAAABIAAAATAAAAFAAAAP7///8WAAAA
FwAAABgAAAAZAAAAGgAAABsAAAAcAAAA/v///x4AAAAfAAAAIAAAACEAAAAiAAAAIwAAACQA
AAAlAAAAJgAAACcAAAAoAAAAKQAAACoAAAArAAAA/v///y0AAAAuAAAALwAAADAAAAAxAAAA
MgAAADMAAAD+////NQAAADYAAAA3AAAAOAAAADkAAAA6AAAAOwAAAP7////9////PgAAAP7/
///+/////v//////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////1IAbwBvAHQA
IABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAWAAUB//////////8DAAAABgkCAAAAAADAAAAAAAAARgAAAAAAAAAAAAAAAGAQqXYZRckB
QAAAAIAAAAAAAAAARABhAHQAYQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAgH///////////////8AAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAVAAAAABAAAAAAAAAxAFQAYQBiAGwAZQAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgACAQEAAAAGAAAA
/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB0AAABwHAAAAAAAAFcA
bwByAGQARABvAGMAdQBtAGUAbgB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAaAAIBAgAAAAUAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAADcoAAAAAAAABQBTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8A
bgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAAgH///////////////8AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsAAAAABAAAAAAAAAFAEQAbwBjAHUAbQBlAG4A
dABTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAOAACAQQA
AAD//////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADQAAAAAEAAA
AAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAASAAIA////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAHEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///////////////8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAA/v//////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
/////////////////////wEA/v8DCgAA/////wYJAgAAAAAAwAAAAAAAAEYfAAAATWljcm9z
b2Z0IE9mZmljZSBXb3JkIERvY3VtZW50AAoAAABNU1dvcmREb2MAEAAAAFdvcmQuRG9jdW1l
bnQuOAD0ObJxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

--Boundary_(ID_PbgcO43drPIyrlhVihqQDA)--



From owner-v6ops@ops.ietf.org  Thu Nov 13 00:46:41 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45C8E3A6819
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 13 Nov 2008 00:46:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.57
X-Spam-Level: 
X-Spam-Status: No, score=0.57 tagged_above=-999 required=5 tests=[AWL=-0.490,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457,
	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 fyQgvcmk34Mf
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 13 Nov 2008 00:46:40 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 105313A6807
	for <v6ops-archive@lists.ietf.org>; Thu, 13 Nov 2008 00:46:40 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L0XlE-000G0E-Gi
	for v6ops-data@psg.com; Thu, 13 Nov 2008 08:41:08 +0000
Received: from [212.27.42.36] (helo=smtp6-g19.free.fr)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <remi.despres@free.fr>)
	id 1L0Xl8-000Fzu-1H
	for v6ops@ops.ietf.org; Thu, 13 Nov 2008 08:41:05 +0000
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 3235B19776;
	Thu, 13 Nov 2008 09:41:00 +0100 (CET)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 71038197A2;
	Thu, 13 Nov 2008 09:40:55 +0100 (CET)
Message-ID: <491BE7A7.8080609@free.fr>
Date: Thu, 13 Nov 2008 09:39:03 +0100
From: =?windows-1252?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
CC: IPv6 Operations <v6ops@ops.ietf.org>, ipv6@ietf.org, 
 Behave WG <behave@ietf.org>,
 softwires@ietf.org, int-area-request@ietf.org
Subject: Re: [BEHAVE] v4v6 coexistence reading list for IETF73
References: <491B6052.30200@sri.com>
In-Reply-To: <491B6052.30200@sri.com>
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=windows-1252"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ed Jankiewicz   (1-12/1-31/200x) 11/13/08 12:01 AM:
<blockquote cite="mid:491B6052.30200@sri.com" type="cite">more for my
own purposes reading through the alternative drafts, however this may
be of use to those interested in current work in IPv4-IPv6 coexistence
tools. The work is going on in 3 working groups and some drafts will be
on on each agenda (some I am guessing will be) are in bold. There will
also be some general discussion in the intarea meeting. The drafts in
italic may be obsolete, either merged into other work or dropped. And
don't forget the paper presented by Randy Bush on Address Plus Port
<a class="moz-txt-link-rfc2396E" href="https://mice.cs.columbia.edu/getTechreport.php?techreportID=560">&lt;https://mice.cs.columbia.edu/getTechreport.php?techreportID=560&gt;</a>
that may become a draft.
  <br>
  <br>
I did not include some related work on tunneling, that maybe should be.
  <br>
Please comment if I have missed any drafts, or mis-characterized any of
these as to WG, status or category. Or any other suggestions to make it
more useful.
  <br>
</blockquote>
Thanks for the list, and the opportunity to update it.<br>
<br>
1) Draft-despres-sam-scenarios is now obsolete<br>
<br>
2) The right document on SAM is draft-despres-sam-01<br>
- Its sections on Problem Statement and SAM Specification are IMO very
relevant.<br>
- Its section on Application Examples is unfortunately still seriously
bugged (rather than going through the details, waiting for the slides
under preparation is advisable).<br>
<br>
o Port-range and privacy-protection aspects or the draft are planned
for presentation in Behave<br>
o Address-mapping and encapsulation aspects are expected to be planned
for presentation in Softwire.<br>
<br>
<br>
Regards,<br>
RD<br>
<blockquote cite="mid:491B6052.30200@sri.com" type="cite">    
  <br>
  <br>
v6ops WG
  <br>
  <br>
    
  <br>
  <br>
Behave WG
  <br>
  <br>
    
  <br>
  <br>
Softwires WG
  <br>
  <br>
    
  <br>
  <br>
Other or unspecified WG
  <br>
  <br>
Framework, scenarios, comparison
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
*Draft-baker-behave-v4v6-framework*
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
Draft-arkko-townsley-coexistence
  <br>
  <br>
    
  <br>
  <br>
Draft-wing-nat-pt-replacement-comparison
  <br>
  <br>
    
  <br>
  <br>
Draft-despres-sam-scenarios
  <br>
  <br>
Problem Statements, requirements
  <br>
  <br>
    
  <br>
  <br>
*Draft-ietf-v6ops-nat64-pb-statement-req*
  <br>
  <br>
    
  <br>
  <br>
Draft-miyata-behave-prefix64
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
Draft-jennings-behave-nat6
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
Solutions
  <br>
  <br>
    
  <br>
  <br>
/Draft-despres-v6ops-apbp/
  <br>
  <br>
    
  <br>
  <br>
*draft-baker-behave-v4v6-translation*
  <br>
  <br>
    
  <br>
  <br>
*Draft-durand-softwire-dual-stack-lite*
  <br>
  <br>
    
  <br>
  <br>
Draft-despres-sam
  <br>
  <br>
    
  <br>
  <br>
*draft-bagnulo-behave-dns64*
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
*draft-bagnulo-behave-nat64*
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
Draft-baker-behave-ivi
  <br>
/Draft-xli-behave-ivi/
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
*draft-vogt-durand-virtual-ip6-connectivity*
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
helpers
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
*Draft-denis-behave-v4v6exthdr*
  <br>
  <br>
    
  <br>
  <br>
    
  <br>
  <br>
Ed Jankiewicz - SRI International
  <br>
Fort Monmouth Branch Office - IPv6 Research Supporting DISA Standards
Engineering Branch
  <br>
732-389-1003 or  <a class="moz-txt-link-abbreviated" href="mailto:ed.jankiewicz@sri.com">ed.jankiewicz@sri.com</a> <br>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Behave mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Behave@ietf.org">Behave@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/behave">https://www.ietf.org/mailman/listinfo/behave</a>
  </pre>
</blockquote>
<br>
</body>
</html>



From owner-v6ops@ops.ietf.org  Thu Nov 13 11:18:30 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 059A03A69B9
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 13 Nov 2008 11:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.655
X-Spam-Level: 
X-Spam-Status: No, score=-98.655 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1,
	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 kzEMPZwObqne
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 13 Nov 2008 11:18:29 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2DFDF3A694F
	for <v6ops-archive@lists.ietf.org>; Thu, 13 Nov 2008 11:18:29 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L0hbk-0000Ok-G2
	for v6ops-data@psg.com; Thu, 13 Nov 2008 19:12:00 +0000
Received: from [2001:670:87:2::25] (helo=lemland.kurtis.pp.se)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <kurtis@kurtis.pp.se>)
	id 1L0ham-0000LT-GF
	for v6ops@ops.ietf.org; Thu, 13 Nov 2008 19:11:03 +0000
Received: from laptop2.kangaroo.comcast.net (unknown [65.97.0.71])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client did not present a certificate)
	by lemland.kurtis.pp.se (Postfix) with ESMTP id BAA0D78C2D
	for <v6ops@ops.ietf.org>; Thu, 13 Nov 2008 21:10:55 +0200 (EET)
Message-Id: <72DB355E-E90C-4E0F-9ADB-FE185A88CAD3@kurtis.pp.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: IPv6 Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: v6ops agenda
Date: Thu, 13 Nov 2008 20:10:50 +0100
X-Pgp-Agent: GPGMail d53 (v53, Leopard)
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

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


1. draft-wbeebee-ipv6-cpe-router-03.txt,  Wes Beebe
2. draft-thaler-v6ops-teredo-extensions-02.txt, Dave Thaler
3. draft-boot-autoconf-brdp-01.txt & draft-boot-brdp-based- 
routing-00.txt, Teco Boot
4. Observations on IPv6 traffic in real life - Kurtis Lindqvist 15 mins

Best regards,

- - kurtis -



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkce7sACgkQAFdZ6xrc/t7olwCfXjwLrddhx/51ZPRjaE/4b/gi
Gc4Anjj26c4GuRZ0FIeKYrowEh80001E
=sPSV
-----END PGP SIGNATURE-----



From owner-v6ops@ops.ietf.org  Thu Nov 13 12:29:57 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB2163A69C6
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 13 Nov 2008 12:29:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.271
X-Spam-Level: 
X-Spam-Status: No, score=-5.271 tagged_above=-999 required=5
	tests=[AWL=-0.776, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 RWQGHbdfaIgK
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 13 Nov 2008 12:29:56 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 4307C3A69A6
	for <v6ops-archive@lists.ietf.org>; Thu, 13 Nov 2008 12:29:55 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L0imD-0004hJ-MJ
	for v6ops-data@psg.com; Thu, 13 Nov 2008 20:26:53 +0000
Received: from [128.18.84.114] (helo=mailgate-internal4.sri.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <edward.jankiewicz@sri.com>)
	id 1L0im6-0004gh-LB
	for v6ops@ops.ietf.org; Thu, 13 Nov 2008 20:26:50 +0000
Received: from smssmtp-internal2.sri.com (128.18.84.116)
  by mailgate-internal4.sri.com with SMTP; 13 Nov 2008 20:26:44 -0000
X-AuditID: 80125474-a9993bb000000a40-aa-491c8d843a09
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id CA76521AF2F
	for <v6ops@ops.ietf.org>; Thu, 13 Nov 2008 12:26:44 -0800 (PST)
Received: from [192.168.2.101]
 (static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
 by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTPSA id <0KAA003S3GSISJ8D@mail.sri.com> for v6ops@ops.ietf.org;
 Thu, 13 Nov 2008 12:26:44 -0800 (PST)
Date: Thu, 13 Nov 2008 15:26:41 -0500
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
Subject: v4v6 coexistence reading list for IETF73 - revised
To: IPv6 Operations <v6ops@ops.ietf.org>, ipv6@ietf.org,
 Behave WG <behave@ietf.org>, softwires@ietf.org,
 Internet Area <int-area@ietf.org>
Message-id: <491C8D81.2040305@sri.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_8rOH84tSdFXxWPvpmHGuVQ)"
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is a multi-part message in MIME format.

--Boundary_(ID_8rOH84tSdFXxWPvpmHGuVQ)
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7BIT

This may be of use to those interested in current work in IPv4-IPv6
coexistence tools. The work is going on in 3 working groups and some
drafts will be on on each agenda. There will also be some general 
discussion in the intarea meeting.

This has been revised reflecting comments from Dan Wing and Rene 
Despres.  Please comment if I have missed any drafts, or 
mis-characterized any of these as to WG, status or category. Or any 
other suggestions to make it more useful.

the table is attached in MS Word, I have not attempted to ascii-fy it 
after my last badly formatted e-mail...

See you on the edge of the prairie, where all the network engineers are 
above average.
	

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



--Boundary_(ID_8rOH84tSdFXxWPvpmHGuVQ)
Content-type: application/msword; name=roadmap.doc
Content-transfer-encoding: base64
Content-disposition: inline; filename=roadmap.doc

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAARQAAAAAA
AAAAEAAARwAAAAEAAAD+////AAAAAEQAAAD/////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
///////////////////////////////////spcEAJWAJBAAA8BK/AAAAAAAAEAAAAAAABgAA
LgwAAA4AYmpiaiJ4IngAAAAAAAAAAAAAAAAAAAAAAAAJBBYANzIAAEASAQBAEgEAuAMAAGgA
AAANAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAD//w8A
AAAAAAAAAAAAAAAAAAAAAKQAAAAAAKAFAAAAAAAAoAUAAKAFAAAWAAAAtgUAABQAAADKBQAA
AAAAAMoFAAAAAAAAygUAABQAAAAAAAAAAAAAAN4FAAAAAAAAhhgAAAAAAACGGAAAAAAAAIYY
AAA4AAAAvhgAABQAAADSGAAAfAAAAN4FAAAAAAAA0h8AAOwAAABaGQAAAAAAAFoZAAAAAAAA
WhkAAAAAAABaGQAAAAAAAFoZAAAAAAAANRoAAAAAAAA1GgAAAAAAADUaAAAAAAAAUR8AAAIA
AABTHwAAAAAAAFMfAAAAAAAAUx8AAAAAAABTHwAAAAAAAFMfAAAAAAAAUx8AACQAAAC+IAAA
aAIAACYjAABwAAAAdx8AABUAAAAAAAAAAAAAAAAAAAAAAAAAygUAAAAAAAA1GgAAAAAAAAAA
AAAAAAAAAAAAAAAAAAA1GgAAAAAAADUaAAAAAAAANRoAAAAAAAA1GgAAAAAAAHcfAAAAAAAA
AAAAAAAAAADKBQAAAAAAAMoFAAAAAAAAWhkAAAAAAAAAAAAAAAAAAFoZAADbAAAAjB8AABYA
AAAJHAAAAAAAAAkcAAAAAAAACRwAAAAAAAA1GgAAJAEAAMoFAAAAAAAAWhkAAAAAAADKBQAA
AAAAAFoZAAAAAAAAUR8AAAAAAAAAAAAAAAAAAAkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANRoAAAAAAABRHwAAAAAAAAAAAAAAAAAA
CRwAAAAAAAAAAAAAAAAAAAkcAAAAAAAAygUAAAAAAADKBQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACRwAAAAAAABaGQAA
AAAAAE4ZAAAMAAAA0KCBEc1FyQEAAAAAAAAAAIYYAAAAAAAAWRsAAFgAAAAJHAAAAAAAAAAA
AAAAAAAArRwAAKQCAACiHwAAMAAAANIfAAAAAAAACRwAAAAAAACWIwAAAAAAALEbAAAAAAAA
liMAAAAAAAAJHAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJHAAAFAAAAJYjAAAAAAAAAAAAAAAAAADKBQAA
AAAAAB0cAACQAAAANRoAAAAAAAA1GgAAAAAAAAkcAAAAAAAANRoAAAAAAAA1GgAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANRoAAAAAAAA1GgAAAAAAADUaAAAAAAAA
dx8AAAAAAAB3HwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsRsAAFgA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADUaAAAAAAAANRoAAAAAAAA1GgAA
AAAAANIfAAAAAAAANRoAAAAAAAA1GgAAAAAAADUaAAAAAAAANRoAAAAAAAAAAAAAAAAAAN4F
AAAAAAAA3gUAAAAAAADeBQAAhAwAAGISAAAkBgAA3gUAAAAAAADeBQAAAAAAAN4FAAAAAAAA
YhIAAAAAAADeBQAAAAAAAN4FAAAAAAAA3gUAAAAAAADKBQAAAAAAAMoFAAAAAAAAygUAAAAA
AADKBQAAAAAAAMoFAAAAAAAAygUAAAAAAAD/////AAAAAAIADAEAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAd2Nm9wcyBXRwdCZWhhdmUgV0cHU29mdHdpcmVzIFdH
B090aGVyIG9yIHVuc3BlY2lmaWVkIFdHBwdGcmFtZXdvcmssIHNjZW5hcmlvcywgY29tcGFy
aXNvbgcHRHJhZnQtYmFrZXItYmVoYXZlLXY0djYtZnJhbWV3b3JrBwdEcmFmdC1hcmtrby10
b3duc2xleS1jb2V4aXN0ZW5jZQcHBwdEcmFmdC13aW5nLW5hdC1wdC1yZXBsYWNlbWVudC1j
b21wYXJpc29uB0RyYWZ0LWRlc3ByZXMtc2FtLXNjZW5hcmlvcwIHB1Byb2JsZW0gU3RhdGVt
ZW50cywgIHJlcXVpcmVtZW50cwdEcmFmdC1pZXRmLXY2b3BzLW5hdDY0LXBiLXN0YXRlbWVu
dC1yZXEHRHJhZnQtbWl5YXRhLWJlaGF2ZS1wcmVmaXg2NAcHBwcHB0RyYWZ0LWplbm5pbmdz
LWJlaGF2ZS1uYXQ2BwcHB1NvbHV0aW9ucwdEcmFmdC1kZXNwcmVzLXY2b3BzLWFwYnAHZHJh
ZnQtYmFrZXItYmVoYXZlLXY0djYtdHJhbnNsYXRpb24HRHJhZnQtZHVyYW5kLXNvZnR3aXJl
LWR1YWwtc3RhY2stbGl0ZQcHBwcHZHJhZnQtYmFnbnVsby1iZWhhdmUtZG5zNjQHBwcHBwdk
cmFmdC1iYWdudWxvLWJlaGF2ZS1uYXQ2NAcHBwcHB0RyYWZ0LWJha2VyLWJlaGF2ZS1pdmkN
RHJhZnQteGxpLWJlaGF2ZS1pdmkHBwcHBwdkcmFmdC12b2d0LWR1cmFuZC12aXJ0dWFsLWlw
Ni1jb25uZWN0aXZpdHkHBwcHB0RyYWZ0LWJhamtvLXY2b3BzLXBvcnQtcmVzdHJpY3RlZC1p
cGFkZHItYXNzaWduAgdEcmFmdC15bWJrLWFwbHVzcA1EcmFmdC1ib3VjYWRhaXItcG9ydC1y
YW5nZQcHRHJhZnQtZGVzcHJlcy1zYW0CBweTaGVscGVyc5QHB0RyYWZ0LWRlbmlzLWJlaGF2
ZS12NHY2ZXh0aGRyBwcHBwcHRHJhZnQtYm91Y2FkYWlyLWRoYy1wb3J0LXJhbmdlBwcHBwcH
RHJhZnQtd2luZy1iZWhhdmUtbGVhcm4tcHJlZml4BwcHB0l0YWxpYyA9IGFzc3VtZWQgb3Ig
a25vd24gdG8gYmUgb2Jzb2xldGUgDUJvbGQgPSBzY2hlZHVsZWQgb24gSUVURjczIGFnZW5k
YQ0CIE9ic29sZXRlIJYgbWVyZ2VkIGludG8gZHJhZnQtZGVzcHJlcy1zYW0NAiBPbiBiZWhh
dmUgYWdlbmRhDQIgT24gYWdlbmRhIGluIGJvdGggYmVoYXZlIGFuZCBzb2Z0d2lyZXMNDQMN
DQQNDQMNDQQNDQ0NAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAABOCAAA
WggAAFwIAAB+CAAAoQgAAKMIAADLCAAAzAgAAOcIAADoCAAA6QgAAOoIAAAMCQAANAkAAHQJ
AAB+CQAAlwkAALsJAADhCQAA4gkAAOUJAAAACgAABQoAACAKAAA8CgAAUQoAAFYKAACBCgAA
hAoAAIUKAAC0CgAAtQoAAOMKAADkCgAA9QoAAPYKAAD3CgAAAwsAACELAAAkCwAAJgsAAPz4
/PD8+On44dXh+PzN/MnCurKrybrJusmjybrJn5eLl5+Dd4Ofb5/JAAAAAAAAAAAAAAAAAA8V
aB406AAWaJ4S3AA1CIEWA2oAAAAAFmjNfucAMEoVADUIgVUIAQAPFWjNfucAFmieEtwANQiB
FgNqAAAAABZo3Fi9ADBKFQA1CIFVCAEADxVo3Fi9ABZonhLcADUIgQYWaJ4S3AAADxVo9DHy
ABZo+jvPADYIgQwVaPQx8gAWaPo7zwAADxVo705vABZo+jvPADUIgQ8VaB406AAWaPo7zwA1
CIEMFWjNfucAFmj6O88AAAYWaPo7zwAADxVo705vABZo9DHyADUIgRYDagAAAAAWaM1+5wAw
ShUANgiBVQgBAA8VaM1+5wAWaA1+TgA2CIEMFWgNfk4AFmgNfk4AAA8VaB406AAWaPQx8gA1
CIEGFmgNfk4AAAYWaPQx8gApAAYAAAEIAAAKCAAAFAgAACEIAAA5CAAAOggAAFsIAAD5AAAA
AAAAAAAAAAAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAA
AAAAAAAAAEIAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAAAAAAAAAAAAAAALYAAGtkAAAAABYk
ARckAUlmAQAAAAKWbAAF1hgEAQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1nIABZT/UQWUEYgd
FCigMgAGvQUAAAAAAAAAAAAAAAAAAAAAAAZDDAAAAAAAAAAAAAAAAAAAAAAABvQLAAAAAAAA
AAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAKdAAA
4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU
9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8AAAD/AAAA
/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8AAAD/AAAA
/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXT0MfIABgAAFiQBSWYBAAAAAAcABgAAuAsAACAM
AAAtDAAA/f39AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAQEAAEBA1sIAABcCAAAfggAAH8IAACgCAAAoQgAAKIIAACjCAAA+QAAAAAA
AAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAEEAAAAAAAAA
AAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAAAAAAAAAAC4AABrZJkAAAAWJAEXJAFJ
ZgEAAAAClmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQBAAAEAQAACNZyAAWU/1EFlBGIHRQo
oDJgBr0FAAAAAAAAAAAAAAAAAAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAAAAAAAAAA
AAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOAB
E9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYD
DDMVNgEX9gMAABj2AwAAGtYUAAAA/wAAAP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA/wAAAP8A
AAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA/wAAAP80
1gYAAQUDAAA01gYAAQoDbABh9gMAAHl09DHyAAYAABYkAUlmAQAAAAAHowgAAMwIAADpCAAA
6ggAAAwJAAA0CQAAUQkAAFIJAABTCQAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAABUAAAA
AAAAAAAAAAAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAA
AAAAAAAAAPkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAa2Q6
AQAAFiQBFyQBSWYBAAAAApZsAAM0AQXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWXAAE
lP9RBZQRFCigMiAGvQUAAAAAAAAAAAAAAAAAAAAAAAZDDAAAAAAAAAAAAAAAAAAAAAAABoAW
AAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOABE9YwAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYDDDMVNgEX9gMAABj2
AwAAGtYQAAAA/wAAAP8AAAD/AAAA/xvWEAAAAP8AAAD/AAAA/wAAAP8c1hAAAAD/AAAA/wAA
AP8AAAD/HdYQAAAA/wAAAP8AAAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXQNfk4A
BgAAFiQBSWYBAAAAAAhTCQAAVAkAAFUJAABWCQAAcQkAAHIJAABzCQAARwAAAAAAAAAAAAAA
AEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAFiQBSWYBAAAAuAAAa2TT
AQAAFiQBFyQBSWYBAAAAApZsAAM0AQXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWcgAF
lP9RBZQRiB0UKKAyYAa9BQAAAAAAAAAAAAAAAAAAAAAABkMMAAAAAAAAAAAAAAAAAAAAAAAG
9AsAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAA
AAAAAAp0AADgARPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAABT2AwwzFTYBF/YDAAAY9gMAABrWFAAAAP8AAAD/AAAA/wAAAP8AAAD/G9YUAAAA
/wAAAP8AAAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAAAP8AAAD/AAAA/x3WFAAAAP8AAAD/AAAA
/wAAAP8AAAD/NNYGAAEFAwAANNYGAAEKA2wAYfYDAAB5dPQx8gAABnMJAAB0CQAAfgkAAJcJ
AAC7CQAA4QkAAOIJAABHAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAGAAAWJAFJZgEAAAC4AABrZHQCAAAWJAEXJAFJZgEAAAAClmwAAzQBBdYYBAEA
AAQBAAAEAQAABAEAAAQBAAAEAQAACNZyAAWU/1EFlBGIHRQooDIgBr0FAAAAAAAAAAAAAAAA
AAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAA
AAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOABE9YwAAAA/wQBAAAAAAD/BAEA
AAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYDDDMVNgEX9gMAABj2AwAAGtYU
AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/
AAAA/wAAAP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQUDAAA01gYAAQoDbABh
9gMAAHl09DHyAAAG4gkAAOMJAADkCQAA5QkAAAAKAAABCgAAAgoAAEcAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAABYkAUlmAQAAALgAAGtkFQMA
ABYkARckAUlmAQAAAAKWbAADNAEF1hgEAQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1nIABZT/
UQWUEYgdFCigMmAGvQUAAAAAAAAAAAAAAAAAAAAAAAZDDAAAAAAAAAAAAAAAAAAAAAAABvQL
AAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAA
AAAKdAAA4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA
/wQBAAAU9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8A
AAD/AAAA/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8A
AAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXT0MfIAAAYCCgAAAwoAAAQKAAAFCgAA
IAoAACEKAAAiCgAARwAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAA
AAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAABgAAFiQBSWYBAAAAuAAAa2S2AwAAFiQBFyQBSWYBAAAAApZsAAM0AQXWGAQBAAAE
AQAABAEAAAQBAAAEAQAABAEAAAjWcgAFlP9RBZQRiB0UKKAyIAa9BQAAAAAAAAAAAAAAAAAA
AAAABkMMAAAAAAAAAAAAAAAAAAAAAAAG9AsAAAAAAAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAA
AAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAp0AADgARPWMAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAABT2AwwzFTYBF/YDAAAY9gMAABrWFAAA
AP8AAAD/AAAA/wAAAP8AAAD/G9YUAAAA/wAAAP8AAAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAA
AP8AAAD/AAAA/x3WFAAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEFAwAANNYGAAEKA2wAYfYD
AAB5dPQx8gAABiIKAAAjCgAAJAoAACUKAAA8CgAAUQoAAFIKAABTCgAARwAAAAAAAAAAAAAA
AEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABB
AAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAAAAAAAAAAAGAAAWJAFJZgEAAAC4AABrZFcEAAAW
JAEXJAFJZgEAAAAClmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQBAAAEAQAACNZyAAWU/1EF
lBGIHRQooDIgBr0FAAAAAAAAAAAAAAAAAAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAA
AAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAA
CnQAAOABE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8E
AQAAFPYDDDMVNgEX9gMAABj2AwAAGtYUAAAA/wAAAP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA
/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA
/wAAAP801gYAAQUDAAA01gYAAQoDbABh9gMAAHl09DHyAAAHUwoAAFQKAABVCgAAVgoAAIEK
AACCCgAAgwoAAEcAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAADgAAAAA
AAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAAAAAAAAAAkAABYkAUlmAQAAAGdk
HjToAAYAABYkAUlmAQAAALgAAGtk+AQAABYkARckAUlmAQAAAAKWbAADNAEF1hgEAQAABAEA
AAQBAAAEAQAABAEAAAQBAAAI1nIABZT/UQWUEYgdFCigMiAGvQUAAAAAAAAAAAAAAAAAAAAA
AAZDDAAAAAAAAAAAAAAAAAAAAAAABvQLAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAA
AAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAKdAAA4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA
/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/
AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/
AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAA
eXT0MfIAAAaDCgAAhAoAAIUKAAC2CgAAyAoAAOMKAADkCgAARwAAAAAAAAAAAAAAAEEAAAAA
AAAAAAAAAABBAAAAAAAAAAAAAAAAOAAAAAAAAAAAAAAAADgAAAAAAAAAAAAAAABBAAAAAAAA
AAAAAAAAAAAAAAAACQAAFiQBSWYBAAAAZ2QeNOgABgAAFiQBSWYBAAAAuAAAa2SZBQAAFiQB
FyQBSWYBAAAAApZsAAM0AQXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWcgAFlP9RBZQR
iB0UKKAyIAa9BQAAAAAAAAAAAAAAAAAAAAAABkMMAAAAAAAAAAAAAAAAAAAAAAAG9AsAAAAA
AAAAAAAAAAAAAAAAAAaMCgAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAp0
AADgARPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEA
ABT2AwwzFTYBF/YDAAAY9gMAABrWFAAAAP8AAAD/AAAA/wAAAP8AAAD/G9YUAAAA/wAAAP8A
AAD/AAAA/wAAAP8c1hQAAAD/AAAA/wAAAP8AAAD/AAAA/x3WFAAAAP8AAAD/AAAA/wAAAP8A
AAD/NNYGAAEFAwAANNYGAAEKA2wAYfYDAAB5dPQx8gAABuQKAAD3CgAA+AoAAAILAAADCwAA
IQsAACILAAAjCwAA+QAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAA
AAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAAAAAAAA
AAC4AABrZDoGAAAWJAEXJAFJZgEAAAAClmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQBAAAE
AQAACNZyAAWU/1EFlBGIHRQooDIgBr0FAAAAAAAAAAAAAAAAAAAAAGAGQwwAAAAAAAAAAAAA
AAAAAAAAAAb0CwAAAAAAAAAAAAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAGAGjAoAAAAA
AAAAAAAAAAAAAAAACnQAAOABE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAFPYDDDMVNgEX9gMAABj2AwAAGtYUAAAA/wAAAP8AAAD/AAAA/wAA
AP8b1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HdYUAAAA
/wAAAP8AAAD/AAAA/wAAAP801gYAAQUDAAA01gYAAQoDbABh9gMAAHl09DHyAAYAABYkAUlm
AQAAAAAHIwsAACQLAAAlCwAAJgsAAEULAABGCwAARwsAAEcAAAAAAAAAAAAAAABBAAAAAAAA
AAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAABYkAUlmAQAAALgAAGtk5QYAABYkARck
AUlmAQAAAAKWbAADNAEF1hgEAQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1nIABZT/UQWUEYgd
FCigMmAGvQUAAAAAAAAAAAAAAAAAAAAAIAZDDAAAAAAAAAAAAAAAAAAAAAAABvQLAAAAAAAA
AAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAAIAaMCgAAAAAAAAAAAAAAAAAAAAAKdAAA
4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU
9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/AAAA/wAAAP8AAAD/AAAA/xvWFAAAAP8AAAD/AAAA
/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/AAAA/wAAAP8d1hQAAAD/AAAA/wAAAP8AAAD/AAAA
/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXT0MfIAAAYmCwAARQsAAGgLAABpCwAAbAsAAHUL
AACMCwAAlAsAAJYLAACaCwAAmwsAAJwLAACdCwAAtwsAALgLAAC5CwAA4wsAAOQLAAD2CwAA
9wsAAB8MAAAgDAAAIQwAACMMAAAkDAAAJgwAACcMAAApDAAAKgwAAC0MAAAuDAAA9/Ps8+Tf
5NvTztPO08a8uLy4vLi0rLSstKy0rLTGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8D
agAAAAAWaAZfZQBVCAEGFmgGX2UAAAYWaNxYvQAAEwNqAAAAABZo3Fi9ADBKFQBVCAEPFWin
TB0AFmjuDBgANQiBCRZop0wdADUIgQ8VaKdMHQAWaKdMHQA1CIEGFminTB0AAAkWaKdMHQA2
CIEPFWinTB0AFminTB0ANgiBDBVo+jvPABZo+jvPAAAGFmj6O88AAA8VaNxYvQAWaPo7zwA1
CIEAHkcLAABICwAASQsAAEoLAABpCwAAagsAAGsLAABHAAAAAAAAAAAAAAAAQQAAAAAAAAAA
AAAAAEEAAAAAAAAAAAAAAABBAAAAAAAAAAAAAAAAQQAAAAAAAAAAAAAAAEEAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAAWJAFJZgEAAAC4AABrZJAHAAAWJAEXJAFJ
ZgEAAAAClmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQBAAAEAQAACNZyAAWU/1EFlBGIHRQo
oDIgBr0FAAAAAAAAAAAAAAAAAAAAAAAGQwwAAAAAAAAAAAAAAAAAAAAAAAb0CwAAAAAAAAAA
AAAAAAAAAAAABowKAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAACnQAAOAB
E9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYD
DDMVNgEX9gMAABj2AwAAGtYUAAAA/wAAAP8AAAD/AAAA/wAAAP8b1hQAAAD/AAAA/wAAAP8A
AAD/AAAA/xzWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HdYUAAAA/wAAAP8AAAD/AAAA/wAAAP80
1gYAAQUDAAA01gYAAQoDbABh9gMAAHl09DHyAAAGawsAAGwLAACWCwAAuAsAAOMLAAD2CwAA
HwwAACAMAABHAAAAAAAAAAAAAAAARQAAAAAAAAAAAAAAAEUAAAAAAAAAAAAAAABDAAAAAAAA
AAAAAAAAQwAAAAAAAAAAAAAAAEMAAAAAAAAAAAAAAABFAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAARQAAAEAALgAAGtkMQgAABYkARckAUlmAQAAAAKWbAADNAEF1hgEAQAABAEAAAQBAAAE
AQAABAEAAAQBAAAI1nIABZT/UQWUEYgdFCigMiAGvQUAAAAAAAAAAAAAAAAAAAAAAAZDDAAA
AAAAAAAAAAAAAAAAAAAABvQLAAAAAAAAAAAAAAAAAAAAAAAGjAoAAAAAAAAAAAAAAAAAAAAA
AAaMCgAAAAAAAAAAAAAAAAAAAAAKdAAA4AET1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU9gMMMxU2ARf2AwAAGPYDAAAa1hQAAAD/AAAA/wAA
AP8AAAD/AAAA/xvWFAAAAP8AAAD/AAAA/wAAAP8AAAD/HNYUAAAA/wAAAP8AAAD/AAAA/wAA
AP8d1hQAAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABBQMAADTWBgABCgNsAGH2AwAAeXT0MfIA
AAcgDAAAIgwAACMMAAAlDAAAJgwAACgMAAApDAAAKwwAACwMAAAtDAAALgwAAP0AAAAAAAAA
AAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAA
AAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAA
AP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAACjUAMZBoAR0wAjpw3Fi9AB+w4D0gsNAvIbCg
BSKwoAUjkKAFJJCgBSWwAAAXsNACGLDQAgyQ0AIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
lwAWJAEXJAFJZgEAAAABlgAAIXYABWgBNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwQD
jAo11gUEBQOMCiN2AAG9BSN2AQJDDCN2AgP0CyN2AwWMCjpWDwAClmwACnQAAOABFPYDDDMV
NgEY9gMAADXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMFA4wKeXT0MfIAnwAWJAEXJAFJ
ZgEAAAABlgAAIXYABWgBNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwQDjAo11gUEBQOM
CiN2AAG9BSN2AQJDDCN2AgP0CyN2AwWMCjpWDwAClmwAAzQBCnQAAOABFPYDDDMVNgEY9gMA
ACvWAgADNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwUDjAp5dPQx8gCXABYkARckAUlm
AQAAAAGWAAAhdgAEaAE11gUAAQO9BTXWBQECA0MMNdYFAgMDgBY11gUDBAOMCiN2AAG9BSN2
AQJDDCN2AgOAFiN2AwSMCjpWDwAClmwAAzQBCnQAAOABFPYDDDMVNgEY9gMAACvWAgABNdYF
AAEDvQU11gUBAgNDDDXWBQIDA4AWNdYFAwQDjAp5dA1+TgCfABYkARckAUlmAQAAAAGWAAAh
dgAFaAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YB
AkMMI3YCA/QLI3YDBYwKOlYPAAKWbAADNAEKdAAA4AEU9gMMMxU2ARj2AwAAK9YCAAM11gUA
AQO9BTXWBQECA0MMNdYFAgMD9As11gUDBQOMCnl09DHyAJ8AFiQBFyQBSWYBAAAAAZYAACF2
AAVoATXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMEA4wKNdYFBAUDjAojdgABvQUjdgEC
QwwjdgID9AsjdgMFjAo6Vg8AApZsAAM0AQp0AADgART2AwwzFTYBGPYDAAAr1gIAATXWBQAB
A70FNdYFAQIDQww11gUCAwP0CzXWBQMFA4wKeXT0MfIAnwAWJAEXJAFJZgEAAAABlgAAIXYA
BWgBNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwQDjAo11gUEBQOMCiN2AAG9BSN2AQJD
DCN2AgP0CyN2AwWMCjpWDwAClmwAAzQBCnQAAOABFPYDDDMVNgEY9gMAACvWAgADNdYFAAED
vQU11gUBAgNDDDXWBQIDA/QLNdYFAwUDjAp5dPQx8gCfABYkARckAUlmAQAAAAGWAAAhdgAF
aAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMM
I3YCA/QLI3YDBYwKOlYPAAKWbAADNAEKdAAA4AEU9gMMMxU2ARj2AwAAK9YCAAE11gUAAQO9
BTXWBQECA0MMNdYFAgMD9As11gUDBQOMCnl09DHyAJ8AFiQBFyQBSWYBAAAAAZYAACF2AAVo
ATXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMEA4wKNdYFBAUDjAojdgABvQUjdgECQwwj
dgID9AsjdgMFjAo6Vg8AApZsAAM0AQp0AADgART2AwwzFTYBGPYDAAAr1gIAATXWBQABA70F
NdYFAQIDQww11gUCAwP0CzXWBQMFA4wKeXT0MfIAnwAWJAEXJAFJZgEAAAABlgAAIXYABWgB
NdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwQDjAo11gUEBQOMCiN2AAG9BSN2AQJDDCN2
AgP0CyN2AwWMCjpWDwAClmwAAzQBCnQAAOABFPYDDDMVNgEY9gMAACvWAgABNdYFAAEDvQU1
1gUBAgNDDDXWBQIDA/QLNdYFAwUDjAp5dPQx8gCfABYkARckAUlmAQAAAAGWAAAhdgAFaAE1
1gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBAOMCjXWBQQFA4wKI3YAAb0FI3YBAkMMI3YC
A/QLI3YDBYwKOlYPAAKWbAADNAEKdAAA4AEU9gMMMxU2ARj2AwAAK9YCAAE11gUAAQO9BTXW
BQECA0MMNdYFAgMD9As11gUDBQOMCnl09DHyAKkAFiQBFyQBSWYBAAAAAZYAACF2AAVoATXW
BQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMEA4wKNdYFBAUDjAojdgABvQUjdgECQwwjdgID
9AsjdgMFjAo6Vg8AApZsAAM0AQp0AADgART2AwwzFTYBGPYDAAAr1gIAASvWAgEDK9YCBAM1
1gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBQOMCnl09DHyAKkAFiQBFyQBSWYBAAAAAZYA
ACF2AAVoATXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMEA4wKNdYFBAUDjAojdgABvQUj
dgECQwwjdgID9AsjdgMFjAo6Vg8AApZsAAM0AQp0AADgART2AwwzFTYBGPYDAAAr1gIAAyvW
AgEBK9YCBAE11gUAAQO9BTXWBQECA0MMNdYFAgMD9As11gUDBQOMCnl09DHyAJ8AFiQBFyQB
SWYBAAAAAZYAACF2AAVoATXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMEA4wKNdYFBAUD
jAojdgABvQUjdgECQwwjdgID9AsjdgMFjAo6Vg8AApZsAAM0AQp0AADgART2AwwzFTYBGPYD
AAAr1gIAATXWBQABA70FNdYFAQIDQww11gUCAwP0CzXWBQMFA4wKeXT0MfIAnwAWJAEXJAFJ
ZgEAAAABlgAAIXYABWgBNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwQDjAo11gUEBQOM
CiN2AAG9BSN2AQJDDCN2AgP0CyN2AwWMCjpWDwAClmwAAzQBCnQAAOABFPYDDDMVNgEY9gMA
ACvWAgABNdYFAAEDvQU11gUBAgNDDDXWBQIDA/QLNdYFAwUDjAp5dPQx8gAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIYCFgASAAEA
nAAPAAQAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAEDx/wIA
QAAMBAAAAAAAAAAABgBOAG8AcgBtAGEAbAAAAAIAAAAYAENKGABfSAEEYUoYAG1ICQRzSAkE
dEgJBAAAAAAAAAAAAAAAAAAAAAAAAEQAQUDy/6EARAAMBQAAAAAAAAAAFgBEAGUAZgBhAHUA
bAB0ACAAUABhAHIAYQBnAHIAYQBwAGgAIABGAG8AbgB0AAAAAABSAGlA8/+zAFIADAUAAAAA
AAAAAAwAVABhAGIAbABlACAATgBvAHIAbQBhAGwAAAAcABf2AwAANNYGAAEKA2wANNYGAAEF
AwAAYfYDAAACAAsAAAAoAGsA9P/BACgAAAUAAAAAAAAAAAcATgBvACAATABpAHMAdAAAAAIA
AAAAAAAAagCaQLMA8wBqAAwEAADtKOMAAAAKAFQAYQBiAGwAZQAgAEcAcgBpAGQAAAA3ADpW
DwAT1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAA
AgAPAAAAQgAnAKIAAQFCAAwFAAD0MfIAAAARAEMAbwBtAG0AZQBuAHQAIABSAGUAZgBlAHIA
ZQBuAGMAZQAAAAgAQ0oQAGFKEAA8AB4AAQASATwADAUAAPQx8gAAAAwAQwBvAG0AbQBlAG4A
dAAgAFQAZQB4AHQAAAACABEACABDShQAYUoUAEAAagARARIBQAAMBQAA9DHyAAAADwBDAG8A
bQBtAGUAbgB0ACAAUwB1AGIAagBlAGMAdAAAAAIAEgAGADUIgVwIgUgAmQABADIBSAAMBQAA
9DHyAAAADABCAGEAbABsAG8AbwBuACAAVABlAHgAdAAAAAIAEwAUAENKEABPSgMAUUoDAF5K
AwBhShAAPgAdQAEAQgE+AAwFAADNfucAAAANAEYAbwBvAHQAbgBvAHQAZQAgAFQAZQB4AHQA
AAACABQACABDShQAYUoUAEAAJkCiAFEBQAAMBQAAzX7nAAAAEgBGAG8AbwB0AG4AbwB0AGUA
IABSAGUAZgBlAHIAZQBuAGMAZQAAAAMASCoBAOcAAAC0AgAA9QIAAC4EAAABAAIAAwAAAAAA
KwAAAD4AAABnAAAAagAAAAAAAAAuBAAABgAAMgAABQD/////AAAAAAEAAAAKAAAAFAAAACEA
AAA5AAAAOgAAAFsAAABcAAAAfgAAAH8AAACgAAAAoQAAAKIAAACjAAAAzAAAAOkAAADqAAAA
DAEAADQBAABRAQAAUgEAAFMBAABUAQAAVQEAAFYBAABxAQAAcgEAAHMBAAB0AQAAfgEAAJcB
AAC7AQAA4QEAAOIBAADjAQAA5AEAAOUBAAAAAgAAAQIAAAICAAADAgAABAIAAAUCAAAgAgAA
IQIAACICAAAjAgAAJAIAACUCAAA8AgAAUQIAAFICAABTAgAAVAIAAFUCAABWAgAAgQIAAIIC
AACDAgAAhAIAAIUCAAC2AgAAyAIAAOMCAADkAgAA9wIAAPgCAAACAwAAAwMAACEDAAAiAwAA
IwMAACQDAAAlAwAAJgMAAEUDAABGAwAARwMAAEgDAABJAwAASgMAAGkDAABqAwAAawMAAGwD
AACWAwAAuAMAAOMDAAD2AwAAHwQAACAEAAAiBAAAIwQAACUEAAAmBAAAKAQAACkEAAArBAAA
LAQAAC8EAACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACA
AQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACA
AAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAACoAAAAACAAqQAAAAAwAAAAAAAA
AIAAAACAAQAAqAAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIACpAAAAADAAAAAA
AAAAgAAAAIABAACoAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAAqAAAAAAgAJkAAAAAMAAA
AAAAAACAAAAAgAEAAKwAAAAAIACpIAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAw
AAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAA
ADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACAAQAA1AAAAAAgAKkA
AAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAA
qQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAA
IACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACAAQAA1AAA
AAAgAKkgAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQ
AAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEA
ANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACA
AQAA1AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACA
AAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAA
AIAAAACAAQAA1AAAAAAgAKkgAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAA
AAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAA
AAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAw
AAAAAAAAAIAAAACAAQAA1AAAAAAgAKkgAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAA
ADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkA
AAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAA
mQAAAAAwAAAAAAAAAIAAAACAAQAA1AAAAAAgAKkgAAAAMAAAAAAAAACAAAAAgAEAANAAAAAA
IACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAA
AAAAAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQ
AAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEA
ANQAAAAAIACpIAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACA
AQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACA
AAAAgAEAANQAAAAAIACpIAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAA
AIAAAACAAQAA0AAAAAAgAakAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAAACpAAAAADAAAAAA
AAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAA
AAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqQAAAAAw
AAAAAAAAAIAAAACAAQAA0AAAAAAgAKkgAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAA
ADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkg
AAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAA
qSAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAA
IACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAA
AAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADU
AAAAACAAqSAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEA
ANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACA
AQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAA
AIABAADUAAAAACAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYQAAAFDAAAAAAAAAAgAAAAIAAAAAAAAAAAAAHmEAAABQwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJhAAAAUMAAAAAAAAACAAAAAgAAAAAAAAAAAAAAIAAAAAAAAAAAA
AAAAAAAAAAAdMFQAAAAAAAAHmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAB1iRADAAAAAA
AAAAAAEAAAAAAAAAAAAAAAAAugeYQAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAHWJEAMAAA
AAAAAAAAAQAAAAAAAAAAAAAAAAC6B5hAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAAdYkQAw
AAAAAAAAAAABAAAAAAAAAAAAAAAAALoHmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAB1iR
ADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAugdYkQAwAAAAAAAAAAABAAAAAAAAAAAAAAA0B7oH
AAAAAH8AAACgAAAAoQAAAOkAAADqAAAADAEAADQBAABRAQAAUgEAAFMBAABVAQAAVgEAAHEB
AAByAQAAcwEAAH4BAACXAQAAuwEAAOEBAADiAQAA4wEAAOQBAADlAQAAAAIAAAECAAACAgAA
AwIAACECAAAiAgAAIwIAAFICAABTAgAAVAIAAFUCAABWAgAAgQIAAIICAACDAgAAhAIAAPcC
AAD4AgAAIgMAACMDAAAkAwAARwMAAEgDAABrAwAAbAMAAC8EAABa0QAwABAAAAAAAAABAAAA
CgAAAAEAAAA4YJoHWtEAMAEQAAAAAAAAAQAAABsAAAACAAAA5IsKB1jRADACEAAAAAAAAAIA
AAABAAAAAwAAALhFIAVa0QAwAhAAAAAAAAACAAAAAQAAAAMAAAC4RTMHCEAAAAAQAAAAAAAA
AAAAAAAAHTC2AAAAAwAgBVrRADABEAAAAAAAAAEAAAAKAAEAAAAAAAAAoAda0QAwARAAAAAA
AAABAAAACgABAAAAAAAAAKAHWtEAMAUQAAAAAAAAAQAAABMAAQAAAAAAAAAgB1jRADABEAAA
AAAAAAEAAAAKAAEAAAAAAAAAoAFY0QAwBhAAAAAAAAABAAAAFwAAAAcAAABwjAoHWtEAMAIQ
AAAAAAAAAQAAAAoAAQAAAAAAAACgB1rRADACEAAAAAAAAAEAAAAKAAEAAAAAAAAAoAdY0QAw
AhAAAAAAAAABAAAACgABAAAAAAAAAKABWNEAMAIQAAAAAAAAAQAAAAoAAAADAAAABBeaB1jR
ADALEAAAAAAAAAEAAAATAAAADAAAAPyMCgda0QAwABAAAAAAAAACAAAAAQABAAAAAAAAAKAH
WtEAMAAQAAAAAAAAAgAAAAEAAQAAAAAAAACgB1rRADAAEAAAAAAAAAIAAAABAAEAAAAAAAAA
oAda0QAwBxAAAAAAAAABAAAAAgABAAAAAAAAAKAHWtEAMBMQAAAAAAAAAQAAAA0AAAAUAAAA
3I0KB1jRADAIEAAAAAAAAAEAAAACAAEAAAAAAAAAoAVY0QAwCBAAAAAAAAABAAAAAgABAAAA
AAAAAKAHWtEAMAgQAAAAAAAAAQAAAAIAAQAAAAAAAACgB1rRADAIEAAAAAAAAAEAAAACAAEA
AAAAAAAAoAda0QAwCBAAAAAAAAABAAAAAgAAAAkAAACsF5oHWtEAMBgQAAAAAAAAAQAAAAkA
AAAZAAAAaI4KB1jRADAJEAAAAAAAAAEAAAACAAAACgAAAMgXoAVY0QAwCRAAAAAAAAABAAAA
AgAAAAoAAADIF5oHWtEAMBoQAAAAAAAAAQAAAAgAAAAbAAAAoI4KB1jRADAUEAAAAAAAAAEA
AAAIAAAAFQAAAKDTIAVY0QAwFBAAAAAAAAABAAAACAAAABUAAACg0zMHWtEAMBwQAAAAAAAA
AQAAAAcAAAAdAAAA9CsKB1jRADAeEAAAAAAAAAEAAAAGAAEAAAAAAAAAIAVY0QAwHhAAAAAA
AAABAAAABgABAAAAAAAAACAHWtEAMB4QAAAAAAAAAQAAAAUAAQAAAAAAAAAgB1rRADAPEAAA
AAAAAAIAAAAKAAEAAAAAAAAAIAda0QAwHRAAAAAAAAACAAAAAgABAAAAAAAAACAHWtEAMCEQ
AAAAAAAAAQAAAAMAAAAiAAAAgCwKB1jRADATAAAAAAAAAAIAAAADAAAAFAAAAFA1IAVa0QAw
ExAAAAAAAAACAAAAAwAAABQAAABQNTMHWNEAMBkQAAAAAAAAAQAAAAIAAAAaAAAALNQgBVjR
ADAZEAAAAAAAAAEAAAACAAAAGgAAACzUMwda0QAwIxAAAAAAAAABAAAAAgAAACQAAAC4LAoH
CEAAAAAAAAAAAAAAAAAAAAAABjAnAwAAKgAgBVrRADACEAAAAAAAAAIAAAABAAAAAwAAAOhE
MwdY0QAwAwAAAAAAAAACAAAAAQAAAAQAAAA4TCAFWNEAMAMAAAAAAAAAAgAAAAEAAAAEAAAA
OEwzBwBAAAAAAAAAAAAAAAAAHTDWAwAAMgAABwEAIAWaAAAAAAAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAHAAAAAAMAAAAGAAAABgAAAAkAAAAMAAAADAAAAAwAAAAMAAAADAAAAAwAAAAMAAAA
DAAAAA8AAAAABgAAJgsAAC4MAAAHAAAAFQAAAAAGAABbCAAAowgAAFMJAABzCQAA4gkAAAIK
AAAiCgAAUwoAAIMKAADkCgAAIwsAAEcLAABrCwAAIAwAAC4MAAAIAAAACgAAAAsAAAAMAAAA
DQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQAAAAWAAAAFwAAABgAAAAABgAALQwAAAkA
AAAPAADwOAAAAAAABvAYAAAAAggAAAIAAAABAAAAAQAAAAEAAAACAAAAQAAe8RAAAAD//wAA
AAD/AICAgAD3AAAQAA8AAvCSAAAAEAAI8AgAAAABAAAAAQQAAA8AA/AwAAAADwAE8CgAAAAB
AAnwEAAAAAAAAAAAAAAAAAAAAAAAAAACAArwCAAAAAAEAAAFAAAADwAE8EIAAAASAArwCAAA
AAEEAAAADgAAUwAL8B4AAAC/AQAAEADLAQAAAAD/AQAACAAEAwkAAAA/AwEAAQAAABHwBAAA
AAEAAAAAAAAABwAAAAkAAAARAAAAEwAAABQAAAAdAAAAHgAAACAAAAA2AAAAOAAAAIUAAACf
AAAArgAAALEAAADSAAAA5wAAAMEBAADgAQAAOAIAADsCAABNAgAAUAIAALwCAADHAgAAzgIA
ANcCAADqAgAA9QIAACwDAABEAwAAuAMAANcDAADiAwAAFQQAAB4EAAAgBAAAIAQAACIEAAAi
BAAAIwQAACMEAAAlBAAAJgQAACgEAAApBAAAKwQAACwEAAAvBAAABwAcAAcAHAAHABwABwAc
AAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAHABwABwAc
AAcABAAHAAQAAgAEAAcABAAHAAQABwAEAAIAAAAAALgDAAAgBAAAIAQAACIEAAAiBAAAIwQA
ACMEAAAlBAAAJgQAACgEAAApBAAAKwQAACwEAAAvBAAABwAHAAQABwAEAAIABAAHAAQABwAE
AAcABAACAAAAAAC4AwAAIAQAACAEAAAiBAAAIgQAACMEAAAjBAAAJQQAACYEAAAoBAAAKQQA
ACsEAAAsBAAALwQAAAcABwAEAAcABAACAAQABwAEAAcABAAHAAQAAgABAMsULDUAAAAAAAAA
AAABAgACAB4AAAAEAAAACAAAAOUAAAAAAAAAHQAAAMhhFQDuDBgAp0wdANAUHwD9NiQAOE0/
AOltQQANfk4ATAFdAAZfZQDvTm8A5VlxAONUqgBRfK0AQ1OxAFtXsQAZQ7MA92q6ANxYvQD6
O88AnhLcAO0o4wDFZ+cAzX7nAB406ADcEeoA9DHyAK0t9QDMWfwAM2T+AAAAAAABAAAACgAA
ABQAAAAhAAAAOQAAADoAAABbAAAAXAAAAH4AAAB/AAAAoAAAAKEAAACiAAAAowAAAMwAAADp
AAAA6gAAAAwBAAA0AQAAUQEAAFIBAABTAQAAVAEAAFUBAABWAQAAcQEAAHIBAABzAQAAdAEA
AH4BAACXAQAAuwEAAOEBAADiAQAA4wEAAOQBAADlAQAAAAIAAAECAAACAgAAAwIAAAQCAAAF
AgAAIAIAACECAAAiAgAAIwIAACQCAAAlAgAAUQIAAFICAABTAgAAVAIAAFUCAABWAgAAgQIA
AIICAACDAgAAhAIAAIUCAAC2AgAA4wIAAOQCAAD3AgAA+AIAAAIDAAADAwAAIQMAACIDAAAj
AwAAJAMAACUDAAAmAwAARQMAAEYDAABHAwAASAMAAEkDAABKAwAAaQMAAGoDAABrAwAAbAMA
AC8EAAAAAAAAAgEAAAIBAAACAQAAAgEAAAIBAAAeAQAAAgEAAAIBAAACAQAAAgEAAAIBAAAe
AQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEA
AAIBAAACAQAAAgEAAB4BAAACAQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEAAAIBAAAC
AQAAAgEAAB4BAAACAQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEAAAIBAAACAQAAAgEA
AB4BAAACAQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEAAAIBAAACAQAAAgEAAB4BAAAC
AQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEAAAIBAAACAQAAAgEAAB4BAAACAQAAAgEA
AAIBAAACAQAAAgEAABYBAAD/QAssAQAAAAAAbAMAANSnBwEBAAIAAQAAAA4ABAABAAAAUQWU
EQIQAAAAAAAAAC4EAABgAAAQAEAAAP//AQAAAAcAVQBuAGsAbgBvAHcAbgD//wEACAAAAAAA
AAAAAAAA//8BAAAAAAD//wAAAgD//wAAAAD//wAAAgD//wAAAAAEAAAARxaQAQAAAgIGAwUE
BQIDBId6ACAAAACACAAAAAAAAAD/AQAAAAAAAFQAaQBtAGUAcwAgAE4AZQB3ACAAUgBvAG0A
YQBuAAAANRaQAQIABQUBAgEHBgIFBwAAAAAAAAAQAAAAAAAAAAAAAACAAAAAAFMAeQBtAGIA
bwBsAAAAMyaQAQAAAgsGBAICAgICBId6ACAAAACACAAAAAAAAAD/AQAAAAAAAEEAcgBpAGEA
bAAAADUmAAAAAAILBgQDBQQEAgSHegBhAAAAgAgAAAAAAAAA/wEBAAAAAABUAGEAaABvAG0A
YQAAACIABAAxCIgYAPDQAgAAaAEAAAAAo2TLZtNry4YAAAAABgBxAAAAjgAAACoDAAABAAEA
AAAEAAMQBgAAAI4AAAAqAwAAAQABAAAABgAAAAAAAAAhAwDwEAAAAAEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgBaAFtAC0AIGBEjQAABAAGQBkAAAAGQAAALcD
AAC3AwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAygxEA8BAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAASFAAAAAACfD/DwEAAT8AAOQEAAD///9/////f////3////9/////f////3////9/
7SjjAAAAAAAyAAAAAAAAAAAAAAAAAAEAAAD//xIAAAAAAAAACQBCAGUAaABhAHYAZQAgAFcA
RwAAAAAAAAANAGUAZAAgAGoAYQBuAGsAaQBlAHcAaQBjAHoADQBlAGQAIABqAGEAbgBrAGkA
ZQB3AGkAYwB6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAFAQIAAAAAAAAAAAAAAAAAAAAAAAEA
AADghZ/y+U9oEKuRCAArJ7PZMAAAAIABAAARAAAAAQAAAJAAAAACAAAAmAAAAAMAAACsAAAA
BAAAALgAAAAFAAAA0AAAAAYAAADcAAAABwAAAOgAAAAIAAAA+AAAAAkAAAAQAQAAEgAAABwB
AAAKAAAAPAEAAAwAAABIAQAADQAAAFQBAAAOAAAAYAEAAA8AAABoAQAAEAAAAHABAAATAAAA
eAEAAAIAAADkBAAAHgAAAAwAAABCZWhhdmUgV0cAAAAeAAAABAAAAAAAAAAeAAAAEAAAAGVk
IGphbmtpZXdpY3oAAAAeAAAABAAAAAAAAAAeAAAABAAAAAAAAAAeAAAACAAAAE5vcm1hbAAA
HgAAABAAAABlZCBqYW5raWV3aWN6AAAAHgAAAAQAAAA2AAAAHgAAABgAAABNaWNyb3NvZnQg
T2ZmaWNlIFdvcmQAAABAAAAAAOYxyQ8AAABAAAAAAKpXRx9FyQFAAAAAANI/EM1FyQEDAAAA
AQAAAAMAAACOAAAAAwAAACoDAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABQECAAAAAAAAAAAAAAAAAAAAAAABAAAAAtXN1Zwu
GxCTlwgAKyz5rjAAAAAAAQAADAAAAAEAAABoAAAADwAAAHAAAAAFAAAAjAAAAAYAAACUAAAA
EQAAAJwAAAAXAAAApAAAAAsAAACsAAAAEAAAALQAAAATAAAAvAAAABYAAADEAAAADQAAAMwA
AAAMAAAA4gAAAAIAAADkBAAAHgAAABQAAABTUkkgSW50ZXJuYXRpb25hbAAAAAMAAAAGAAAA
AwAAAAEAAAADAAAAtwMAAAMAAAAPJwsACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAA
AAAeEAAAAQAAAAoAAABCZWhhdmUgV0cADBAAAAIAAAAeAAAABgAAAFRpdGxlAAMAAAABAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAQAAAAIAAAADAAAABAAAAAUAAAAGAAAABwAAAAgAAAAJAAAACgAAAAsA
AAAMAAAADQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQAAAAVAAAAFgAAABcAAAAYAAAA
GQAAAP7///8bAAAAHAAAAB0AAAAeAAAAHwAAACAAAAAhAAAA/v///yMAAAAkAAAAJQAAACYA
AAAnAAAAKAAAACkAAAAqAAAAKwAAACwAAAAtAAAALgAAAC8AAAAwAAAAMQAAADIAAAAzAAAA
/v///zUAAAA2AAAANwAAADgAAAA5AAAAOgAAADsAAAD+////PQAAAD4AAAA/AAAAQAAAAEEA
AABCAAAAQwAAAP7////9////RgAAAP7////+/////v//////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////9SAG8AbwB0ACAARQBuAHQA
cgB5AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFgAFAf//
////////AwAAAAYJAgAAAAAAwAAAAAAAAEYAAAAAAAAAAAAAAACw+I8RzUXJAUgAAACAAAAA
AAAAAEQAYQB0AGEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAKAAIB////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAGgAAAAAQAAAAAAAAMQBUAGEAYgBsAGUAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4AAgEBAAAABgAAAP////8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAiAAAAliMAAAAAAABXAG8AcgBkAEQA
bwBjAHUAbQBlAG4AdAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
GgACAQIAAAAFAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAA3MgAAAAAAAAUAUwB1AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAoAAIB////////////////AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAANAAAAAAQAAAAAAAABQBEAG8AYwB1AG0AZQBuAHQAUwB1AG0A
bQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAAAAAAADgAAgEEAAAA////////
//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8AAAAABAAAAAAAAABAEMA
bwBtAHAATwBiAGoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAEgACAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAABxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////////////////AAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAP7/////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
//////////8BAP7/AwoAAP////8GCQIAAAAAAMAAAAAAAABGHwAAAE1pY3Jvc29mdCBPZmZp
Y2UgV29yZCBEb2N1bWVudAAKAAAATVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9Dmy
cQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==

--Boundary_(ID_8rOH84tSdFXxWPvpmHGuVQ)--



From owner-v6ops@ops.ietf.org  Sun Nov 16 12:49:57 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4592F3A68A0
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 16 Nov 2008 12:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 6pASFmr1mBOz
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sun, 16 Nov 2008 12:49:56 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 951A23A6405
	for <v6ops-archive@lists.ietf.org>; Sun, 16 Nov 2008 12:49:55 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L1oTz-000AEN-CF
	for v6ops-data@psg.com; Sun, 16 Nov 2008 20:44:35 +0000
Received: from [2001:670:87:2::25] (helo=lemland.kurtis.pp.se)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <kurtis@kurtis.pp.se>)
	id 1L1oTt-000AE7-CG
	for v6ops@ops.ietf.org; Sun, 16 Nov 2008 20:44:32 +0000
Received: from [IPv6:2001:df8::16:21d:4fff:fefc:b8f3] (unknown [IPv6:2001:df8:0:16:21d:4fff:fefc:b8f3])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client did not present a certificate)
	by lemland.kurtis.pp.se (Postfix) with ESMTP id C1E7078C2B
	for <v6ops@ops.ietf.org>; Sun, 16 Nov 2008 22:44:26 +0200 (EET)
Message-Id: <54CF5DE8-5375-4DF3-A3F1-0328D19C0FC9@kurtis.pp.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: IPv6 Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Updated agenda
Date: Sun, 16 Nov 2008 20:00:46 +0100
X-Pgp-Agent: GPGMail d53 (v53, Leopard)
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

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



1. Agenda bash, 5 mins, Chairs
2. Current WG document status, Chairs
	- draft-ietf-v6ops-addcon-10.txt
	- draft-ietf-v6ops-cpe-simple-security-03.txt
	- draft-ietf-v6ops-nat64-pb-statement-req-00.txt
	- draft-ietf-v6ops-ra-guard-01.txt
	- draft-ietf-v6ops-tunnel-security-concerns-01.txt
1. draft-wbeebee-ipv6-cpe-router-03.txt,  Wes Beebe
2. draft-thaler-v6ops-teredo-extensions-02.txt, Dave Thaler
3. draft-boot-autoconf-brdp-01.txt & draft-boot-brdp-based- 
routing-00.txt, Teco Boot
4. IPv6 usage in Sweden - Kurtis Lindqvist 15 mins
5. IPv6 statistics at Google, Harald Alvestrand

Best regards,

- - kurtis -



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkgbd4ACgkQAFdZ6xrc/t4enACglGbn0Mmg7H7x6+sgbHettXmw
HCIAn1K2WHO2DezFam00Qiv/70nBU9Dz
=bTCb
-----END PGP SIGNATURE-----



From owner-v6ops@ops.ietf.org  Sun Nov 16 12:49:58 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A1CF3A6405
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 16 Nov 2008 12:49:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.6
X-Spam-Level: 
X-Spam-Status: No, score=-104.6 tagged_above=-999 required=5 tests=[AWL=2.000,
	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 l9wmR6bqvPWR
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sun, 16 Nov 2008 12:49:56 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62])
	by core3.amsl.com (Postfix) with ESMTP id CF4ED3A684A
	for <v6ops-archive@lists.ietf.org>; Sun, 16 Nov 2008 12:49:56 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L1oTT-000ADG-L6
	for v6ops-data@psg.com; Sun, 16 Nov 2008 20:44:03 +0000
Received: from [2001:670:87:2::25] (helo=lemland.kurtis.pp.se)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <kurtis@kurtis.pp.se>)
	id 1L1oTM-000ACj-Im
	for v6ops@ops.ietf.org; Sun, 16 Nov 2008 20:44:00 +0000
Received: from [IPv6:2001:df8::80:21d:4fff:fefc:b8f3] (unknown [IPv6:2001:df8:0:80:21d:4fff:fefc:b8f3])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client did not present a certificate)
	by lemland.kurtis.pp.se (Postfix) with ESMTP id 2D39578C2D
	for <v6ops@ops.ietf.org>; Sun, 16 Nov 2008 22:43:52 +0200 (EET)
Message-Id: <54CF5DE8-5375-4DF3-A3F1-0328D19C0FC9@kurtis.pp.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: IPv6 Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Updated agenda
Date: Sun, 16 Nov 2008 20:00:46 +0100
X-Pgp-Agent: GPGMail d53 (v53, Leopard)
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

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



1. Agenda bash, 5 mins, Chairs
2. Current WG document status, Chairs
	- draft-ietf-v6ops-addcon-10.txt
	- draft-ietf-v6ops-cpe-simple-security-03.txt
	- draft-ietf-v6ops-nat64-pb-statement-req-00.txt
	- draft-ietf-v6ops-ra-guard-01.txt
	- draft-ietf-v6ops-tunnel-security-concerns-01.txt
1. draft-wbeebee-ipv6-cpe-router-03.txt,  Wes Beebe
2. draft-thaler-v6ops-teredo-extensions-02.txt, Dave Thaler
3. draft-boot-autoconf-brdp-01.txt & draft-boot-brdp-based- 
routing-00.txt, Teco Boot
4. IPv6 usage in Sweden - Kurtis Lindqvist 15 mins
5. IPv6 statistics at Google, Harald Alvestrand

Best regards,

- - kurtis -



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkgbd4ACgkQAFdZ6xrc/t4enACglGbn0Mmg7H7x6+sgbHettXmw
HCIAn1K2WHO2DezFam00Qiv/70nBU9Dz
=bTCb
-----END PGP SIGNATURE-----



From owner-v6ops@ops.ietf.org  Sun Nov 16 19:36:46 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC3353A686B
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 16 Nov 2008 19:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5
	tests=[AWL=-1.002, 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 WgZZcWQSMqUt
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sun, 16 Nov 2008 19:36:46 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6C27C3A684C
	for <v6ops-archive@lists.ietf.org>; Sun, 16 Nov 2008 19:36:45 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L1uo6-0007nV-S4
	for v6ops-data@psg.com; Mon, 17 Nov 2008 03:29:46 +0000
Received: from [209.85.198.227] (helo=rv-out-0506.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <brian.e.carpenter@gmail.com>)
	id 1L1uo0-0007mO-Dx
	for v6ops@ops.ietf.org; Mon, 17 Nov 2008 03:29:42 +0000
Received: by rv-out-0506.google.com with SMTP id b25so2310587rvf.41
        for <v6ops@ops.ietf.org>; Sun, 16 Nov 2008 19:29:40 -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=pPikeLlNvxFG/iTFx/QBg6oJ7Rs/Mk+hjjKaezLBhBQ=;
        b=DsgTrUnLJE9IoD9iey8n4vE7e9o1YmXgfrkE8jRzCEUEqvRRFY5B96wyfvuEOgr2l/
         mLqFyAUqs8CbVv5TE3pfJmR+P7axhX/Av6fh8zWBoy0A2atF6Ad1Wfp1mrXh3PhzUV1j
         RyrUdnHKGOR0jUSDK8HK+bi6rjR0BbAyScuT0=
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=JujvkDcg0h3ofPNxLpq/J0SnqCJyGWSllNZvbJxHnYFYAKThris0K51+0NeZj+ve0D
         QqYEpIMppvcfCslzDlX4wR+mlGfMJnxNf1JEoQO993ZfH4yYIkLnMrE601eoHfC1Lnqr
         i52zAqzOGCFRVSv4JdIkK7Oj6a/ZWW+Kih/lU=
Received: by 10.141.88.3 with SMTP id q3mr1996408rvl.54.1226892580066;
        Sun, 16 Nov 2008 19:29:40 -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 k2sm8339137rvb.1.2008.11.16.19.29.38
        (version=SSLv3 cipher=RC4-MD5);
        Sun, 16 Nov 2008 19:29:39 -0800 (PST)
Message-ID: <4920E51C.7070007@gmail.com>
Date: Mon, 17 Nov 2008 16:29:32 +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: james woodyatt <jhw@apple.com>
CC: Eric Klein <EricLKlein@softhome.net>, 
 IPv6 Operations <v6ops@ops.ietf.org>,
 Behave WG <behave@ietf.org>
Subject: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
References: <4911B9E7.8090108@free.fr>	<BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com>	<courier.4912CE09.00003CB8@softhome.net>	<BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com>	<6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com>	<courier.4914868B.00003F53@softhome.net>	<9937716B-A667-4FB6-8337-9596AD356901@muada.com>	<courier.4917F518.00002B4D@softhome.net>	<20081110143243.GI89033@Space.Net>	<courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com>
In-Reply-To: <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 2008-11-11 11:24, james woodyatt wrote:
...
> That said, I'm not impressed by the arguments put forward by the
> opponents of RFC 4864 local network protection who, in my view, are
> greatly exaggerating the seriousness of the network renumbering
> problem.   

James, and anyone else who is still able to focus on this thread:

Please read draft-carpenter-renum-needs-work-00.txt and send
comments and suggestions to its authors.

    Brian



From owner-v6ops@ops.ietf.org  Mon Nov 17 11:29:32 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFFD93A6A01
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 17 Nov 2008 11:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	NO_RELAYS=-0.001, 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 9AGGP991Nnfd
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 17 Nov 2008 11:29:32 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2FDD93A69D8
	for <v6ops-archive@lists.ietf.org>; Mon, 17 Nov 2008 11:29:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L29i9-000DeH-SS
	for v6ops-data@psg.com; Mon, 17 Nov 2008 19:24:37 +0000
Received: from [2001:670:87:2::25] (helo=lemland.kurtis.pp.se)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <kurtis@kurtis.pp.se>)
	id 1L29i2-000DdH-Kc
	for v6ops@ops.ietf.org; Mon, 17 Nov 2008 19:24:34 +0000
Received: from [IPv6:2001:df8::96:21d:4fff:fefc:b8f3] (unknown [IPv6:2001:df8:0:96:21d:4fff:fefc:b8f3])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client did not present a certificate)
	by lemland.kurtis.pp.se (Postfix) with ESMTP id E445A78C2B
	for <v6ops@ops.ietf.org>; Mon, 17 Nov 2008 21:24:26 +0200 (EET)
Message-Id: <E71C6B2C-9245-4660-A647-509684CDF213@kurtis.pp.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: IPv6 Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Volunteers for scribes....
Date: Mon, 17 Nov 2008 20:05:13 +0100
X-Pgp-Agent: GPGMail d53 (v53, Leopard)
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

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

	

Trying to be a bit pro-active, if you are willing to serve as scribe  
and/or Jabber scribe in the v6ops meeting, please contact me and/or  
Fred...

Thanks!

Best regards,

- - kurtis -



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkhwGkACgkQAFdZ6xrc/t7S0ACfekuE0tmbzeCfJu+BT2yRD2C6
C1QAoIh6OsSH4grRvAuaa3C8PTLujY9x
=kwkk
-----END PGP SIGNATURE-----



From owner-v6ops@ops.ietf.org  Mon Nov 17 21:28:52 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70EC83A6851
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 17 Nov 2008 21:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.347
X-Spam-Level: 
X-Spam-Status: No, score=-104.347 tagged_above=-999 required=5
	tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, J_CHICKENPOX_22=0.6,
	RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, 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 r8IOKO3MADvh
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 17 Nov 2008 21:28:51 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 04C673A67E1
	for <v6ops-archive@lists.ietf.org>; Mon, 17 Nov 2008 21:28:51 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2J2j-000JIy-0q
	for v6ops-data@psg.com; Tue, 18 Nov 2008 05:22:29 +0000
Received: from [17.254.13.23] (helo=mail-out4.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1L2J2X-000JI4-Lp
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 05:22:25 +0000
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out4.apple.com (Postfix) with ESMTP id 956FB4745B0B;
	Mon, 17 Nov 2008 21:22:16 -0800 (PST)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Brightmail Gateway) with ESMTP id 79C21464002;
	Mon, 17 Nov 2008 21:22:16 -0800 (PST)
X-AuditID: 11807135-a5378bb000000d45-b2-49225107e1b2
Received: from [17.151.125.17] (unknown [17.151.125.17])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay12.apple.com (Apple SCV relay) with ESMTP id A2C66420003;
	Mon, 17 Nov 2008 21:22:15 -0800 (PST)
Cc: Eric Klein <EricLKlein@softhome.net>,
 IPv6 Operations <v6ops@ops.ietf.org>,
 Behave WG <behave@ietf.org>
Message-Id: <60FD682C-1436-493F-995D-4B2A7241D398@apple.com>
From: james woodyatt <jhw@apple.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4920E51C.7070007@gmail.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
Date: Mon, 17 Nov 2008 23:22:14 -0600
References: <4911B9E7.8090108@free.fr> <BB56240F3A190F469C52A57138047A03014762B5@xmb-rtp-211.amer.cisco.com> <courier.4912CE09.00003CB8@softhome.net> <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 16, 2008, at 21:29, Brian E Carpenter wrote:
> On 2008-11-11 11:24, james woodyatt wrote:
> ...
>> That said, I'm not impressed by the arguments put forward by the
>> opponents of RFC 4864 local network protection who, in my view, are
>> greatly exaggerating the seriousness of the network renumbering
>> problem.
>
> James, and anyone else who is still able to focus on this thread:
>
> Please read draft-carpenter-renum-needs-work-00.txt and send
> comments and suggestions to its authors.

I'm delighted to read this draft.  I remain unconvinced by arguments =20
that the network renumbering problem is a compelling argument for the =20=

need to insert thirty gazillion PI routes into the DFZ.

----

Some thoughts on section 2.2, Existing Host-related Mechanisms =3D> =
PPP...

For IPv4, PPP endpoints acquire (during IPCP negotiation) both their =20
own address and the address of their peer, which may be assumed to be =20=

the default router if no routing protocol is operating.  Renumbering =20
events arise when IPCP negotiation is restarted on an existing link, =20
when LCP is terminated and restarted, or when the point-to-point =20
medium is reconnected.  (I can't remember right now whether NCP must =20
be renegotiated if an authentication protocol is restarted while NCP =20
is up.)  Peers may propose either the local or remote address or =20
require the other peer to do so.  Negotiation is complete when both =20
peers are in agreement.  In practice, if no routing protocol is used, =20=

then the provider proposes both addresses and requires the subscriber =20=

either to accept the connection or abort.

For IPv6, PPP endpoints acquire both local and remote addresses during =20=

IP6CP negotiation in much the same way as for IPv4, but the addresses =20=

are link-local scope only.  In practice, each side can propose its own =20=

address and renegotiation is only necessary when there is a =20
collision.  Once link-local addresses are assigned and IP6CP is =20
complete, automatic assignment of global scope addresses is performed =20=

by the same methods as with multipoint links, i.e. either SLAAC or =20
DHCP6, which are described in the subsequent sections of the draft.

----

Also: section 2.5 about DNS... this section really, really, really =20
ought to at least think about mentioning DNS-SD (for which the =20
relevant Internet Drafts-- for reasons that continue to plague the =20
twilight of my waking dreams-- are categorized as Informational, and =20
not Standards Track).

If you've never heard of DNS-SD before, then please look at...

	<http://www.dns-sd.org/>

...and follow the links from there.  The executive summary is that not =20=

only can we dynamically update the DNS with host address records, we =20
can even do it with *service* instances too, which are pointers to =20
service records that reference host records.  It works pretty well.  =20
Really.  I renumber some of my networks *dozens* *of* *times* *per* =20
*DAY*.  Some of these are *virtual* networks.  It's not even remotely =20=

painful until I start trying to do it a few dozen times per *hour*.  =20
That's pretty good!

Yes, DNS-SD and DNSSEC are quite compatible.  Really.  Come join us in =20=

the Future=99.  It's nice here.  Stuff just works.

-----

The M&O bits.  I'm one of those who thinks that ICMP6 is the protocol =20=

that ought to be used for control and management of the Internet.  I =20
think that DHCP (with DHCP6, it's 2nd-system-effect offspring) is a =20
monster that slipped its leash a long time, and we're all poorer for =20
it now.  So, it should not be a surprise that I favor resolving the so-=20=

called "M&O ambiguity" by clarifying the specification to say that =20
starting the DHCP6 client is *always* OPTIONAL and that nodes *always* =20=

MAY self-assign a global scope address after receiving any RA =20
containing a PIO with A=3D1.

I recognize that my preferred approach poses some problems (many of =20
which are the subject of ongoing work in the SAVI and V6OPS working =20
groups), but I contend that we will all be better off if *those* are =20
the problems we choose to make for ourselves and we proceed now to set =20=

our minds to solving them.  The other problems we invite for ourselves =20=

resolving the M&O ambiguity by different means are more troubling, I =20
say.  We might as well just get rid of SLAAC altogether and require =20
DHCP6 everywhere.  I know that would make some people happy, but not =20
me.  I rather like zero configuration networking.

-----

On section 4.1.2, Transport Layer Issues... let me just say that SCTP =20=

is made of the purest elegance and beauty.  We should deprecate TCP =20
over IPv6 in favor of SCTP, it's so good.  Oh wait... worse is =20
better.  I keep forgetting.

So, if we *can't* migrate to SCTP, and we MUST find a way to live with =20=

TCP and UDP, then we're just going to have to lump it when renumbering =20=

causes failurage on TCP/UDP flows.  But that shouldn't be so bad, =20
really.  You want SCTP-style multihoming with your TCP transports?  =20
Then you can implement it in your session^H^H^H^H^H^H^H application =20
layer.  (If I wanted to be especially curmudgeonly, I'd suggest a BEEP =20=

tuning profile for the TCP transport mapping, but I'll go easy on that =20=

for now.)

-----

On section 4.1.4, Application Layer Issues... the following quote is =20
the understatement literally of the decade:
> The sensitivity depends on whether the implementation stores IP =20
> addresses in such a way that it may refer back to them later, =20
> without allowing for the fact that they may no longer be valid.
                            =20
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This, in my view, is the main reason why IPv6 renumbering should be =20
regarded as "still needs some work" instead of "why are we worrying =20
about this?"  But the work in question isn't IETF work, I contend.  =20
It's just mundane code-wrangling work.

I've highlighted what I regard as the crucial phrase.  We're talking =20
about software bugs.  We're talking about software bugs of a general =20
class, i.e. cache coherency failures, that cannot really be mitigated =20=

by sacrificing fundamental principles of the Internet architecture to =20=

make the renumbering events that expose them less frequent.  There are =20=

so many other ways, which have nothing to do with network renumbering =20=

events, that bugs of this class can make expensive software failures =20
happen.  I'd prefer we find ways to build better coders, than we were =20=

to expend any effort trying to take Internet address renumbering off =20
the long list of interesting ways that incoherent caches can break =20
software.

My employers have a developer technote on their website that speaks to =20=

this general class of software problem in networked applications.  The =20=

tenth anniversary [!] of its original composition came and went a few =20=

days ago.  The document is here:

	<http://developer.apple.com/technotes/tn/tn1145.html>

Seriously.  Check it out.  Application layer issues with renumbering =20
events would not be expensive if the platform-independent lessons of =20
that technical note were more widely applied.

I am so *so* tired of making excuses for bad code.  Just once, I'd =20
like to be able to say, "I see your coders thought it would be a good =20=

idea to store IP addresses in a persistent store without any cache =20
coherency protocol, and now you can't renumber your network without =20
eating the time and expense of qualifying a radical new implementation =20=

of your hugely business-critical software application.  You know =20
what?  That's your own fault.  Not ours.  p.s. I bet you'll read that =20=

tech-note next time, right?"


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Tue Nov 18 10:17:01 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D5AE3A682E
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 10:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 3vubFL4pOpDR
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 10:17:00 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B31543A6808
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 10:16:59 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2V3a-0007a3-5J
	for v6ops-data@psg.com; Tue, 18 Nov 2008 18:12:10 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <iljitsch@muada.com>)
	id 1L2V3T-0007ZV-IE
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 18:12:06 +0000
Received: from [IPv6:2001:df8::16:223:12ff:fe56:36b2] ([IPv6:2001:df8:0:16:223:12ff:fe56:36b2])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id mAIIBCuY096425
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <v6ops@ops.ietf.org>; Tue, 18 Nov 2008 19:11:14 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Message-Id: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: v6ops Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: draft-wbeebee-ipv6-cpe-router-03
Date: Tue, 18 Nov 2008 12:11:56 -0600
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

I think an important question is how firm we want to be on the issue  
of cascading CPEs.

With IPv4, you can nest/cascade CPEs that do NAT, which makes life  
harder on NAT traversal protocols but otherwise works without trouble.  
Because with IPv6, each CPE needs a prefix for its LAN interface(s)  
cascading CPEs without some kind of support from the ISP and upstream  
CPEs isn't possible. Basically, what needs to happen is that the first  
CPE gets a prefix from the ISP, and then implement a DHCPv6 server  
that delegates smaller prefixes to downstream CPEs.

The first CPE can't simply relay the request to the ISP, because even  
if we can presume the ISP to be generous and give more than one prefix  
to a single subscriber, the first CPE needs to install this prefix in  
its routing table. So that would require extensive DHCP relaying  
logic. So the situation where the CPE acts as a DHCPv6 server makes  
more sense. (Note that in the case where the cascading happens, we  
would also want the upstream CPE to disable its firewall for addresses  
in the delegated prefix to avoid double firewalling.)

Now I could see how vendors (especially of cheap) CPEs may not want to  
implement all of this. But in the case where such a CPE is provided by  
a broadband ISP and has a non-ethernet WAN port, the end-user would be  
unable to buy a premium CPE and be stuck with whatever suboptimal  
features the ISP-provided CPE incorporates. This is bad for everyone.  
The situation where the customer can go out and buy a better CPE is  
good for:

- the CPE vendors: more CPEs sold
- the ISPs: the ISP-provided CPEs don't have to be all things to all  
people
- the consumers: choice

So in the case that a CPE vendor doesn't want to implement the DHCPv6  
server necessary for cascading, I think we should mandate that the  
first CPE, when it detects that a secondary CPE is connected on the  
LAN side, becomes a transparent bridge. (Insert DHCPv6 option to make  
this happen.)

Unfortunately, this mode of operation would be incompatible with  
additional requirements for address assignment/registration and the  
use of a single, known good MAC address that broadband ISPs may  
impose. So I guess when those requirements are present, we're back  
with requiring a DHCPv6 server in the CPE.

Implementing a DHCPv6 server in the CPE rather than relaying DHCPv6  
requests to the ISP also reduces the amount of DHCPv6 traffic seen by  
the ISPs, which could be helpful.

Is the above something we can agree on?


Here are some more detailed comments on the draft:

You point to the IPv6 node requirements. I thought that router  
requirements would be more appropriate, but although there is an IPv4  
router requirements document penned by our esteemed chair, there is no  
such document for IPv6...

       mDNS - Multicast Domain Name System - see http:// 
www.zeroconf.org.

There's a bunch of multicast DNS related drafts floating around, maybe  
you can link to the most relevant one of those?

    If stateful DHCPv6 is not used to obtain other
    IPv6 configuration, then stateless DHCPv6 [RFC3736] must be  
initiated
    by the WAN interface to obtain other IPv6 configuration.

must or MUST?

I don't think there is any reason to use statless DHCPv6, because the  
router must always do stateful DHCPv6 to obtain a prefix anyway. It  
would be extremely unlikely that the server wouldn't return other info  
such as DNS addresses statefully but then provide this information if  
queried again statelessly.

BTW, what happens if the prefix delegation request fails and there is  
no prefix?

5.3.3.  Both Models

    At any instance in time of the CPE Router operation, the router does
    not forward any traffic between its WAN and LAN interface(s) if the
    router has not completed IPv6 provisioning process that involves the
    acquisition of a global IPv6 address by the WAN or if the WAN is
    unnumbered and there is no GUA available to source WAN packets.

A router generally doesn't source packets itself, so the presence of a  
WAN address doesn't really impact the router functionality...

    This document recommends the RA sent out by LAN Interface(S) to be
    configured for SLAAC so that the prefix advertised in the RA is
    derived from the IA_PD assigned to the CPE Router by the Service
    Provider; the O-bit is also set so that the CPE Router can pass
    Domain Name Server(s) IPv6 address(es) to home devices.  The CPE
    Router obtained the Domain Name Server(s) in OPTION_DNS_SERVERS
    option from the DHCPv6 server when the CPE Router WAN interface
    completed DHCPv6.

It would be good if CPEs would also insert DNS addresses in RAs as per  
RFC 5006. If requiring the support of an experimental RFC is a bridge  
too far, at the very least say this is a good idea and point to 5006.

It would be useful to tell people to align the timers in RAs with  
those in the PD delegation for easier renumbering. Note that during  
renumbering hosts may source packets with the old addresses even  
though the new ones are already available. This shouldn't cause  
trouble, but in cases where routes or filter rules are created,  
multiple sets of these are necessary during transition from one prefix  
to another.

For the purpose of shim6 support: it would be possible for a user to  
get service from two different ISPs and then hook up a third CPE to  
the two connected to these ISPs. This third CPE would then get a  
subdelegated prefix from each ISP. So either this CPE should support  
this, and use two prefixes at the same time, and send packets with  
source addresses from ISP A to the CPE that gave out addresses from  
ISP A, and packets with B addresses to the B CPE, or it should only  
accept one prefix and then make sure that all packets go to the router  
that delegated that prefix.

8.1.  Path MTU Discovery Support

When the WAN MTU is less than 1500 (such as in the case of PPPoE), the  
router should put the WAN MTU in the RA MTU option on the LAN side so  
the hosts use the reduced MTU and adjust their TCP MSS accordingly,  
reducing the likelihood of trouble because of PMTUD black holes.

8.2.  Optional RIPng Support

Is this useful?

8.3.  Firewall

There must be a way for the user to disable the firewall if desired.

These CPEs will be dual stack but they may be connected to an IPv4- 
only or even IPv6-only network. (Intentionally or by mistake, maybe  
one protocol has failed but the other still works, we certainly don't  
want fait sharing here...)

In the case where IPv4 is non-functional, a router MAY still advertise  
private addresses, which can be used for configuration or DNS lookups  
(if the CPE is a DNS forwarder, useful in the case of OSes that can't  
do DNS over IPv6 transport (Windows XP) or have no autoconfiguration  
of IPv6 DNS addresses (MacOS)) but MUST NOT provide a default gateway  
so that the hosts know they can't send packets towards IPv4  
destinations so long timeouts are avoided.

In the case of non-functional IPv6 but working IPv4, it's probably  
best to not let hosts autoconfigure addresses and also not have RAs  
create default gateways, because some OSes take the former to mean  
that there is working IPv6 and others the latter.

Please let me know what of the above is non-controversial and I'll  
submit text, if desired.



From owner-v6ops@ops.ietf.org  Tue Nov 18 11:26:27 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CAAB3A6B17
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 11:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.495
X-Spam-Level: 
X-Spam-Status: No, score=-108.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1, 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 qqu0J0sRS6wF
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 11:26:26 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 826933A6B0B
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 11:26:26 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2WAS-000Bk0-Sf
	for v6ops-data@psg.com; Tue, 18 Nov 2008 19:23:20 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L2WAN-000Bjc-8v
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 19:23:18 +0000
X-IronPort-AV: E=Sophos;i="4.33,626,1220227200"; 
   d="scan'208";a="26042357"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
  by ams-iport-1.cisco.com with ESMTP; 18 Nov 2008 19:23:13 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAIJNDOS000667;
	Tue, 18 Nov 2008 20:23:13 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAIJND3u000468;
	Tue, 18 Nov 2008 19:23:13 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 20:23:13 +0100
Received: from [130.129.95.58] ([10.21.146.34]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 20:23:12 +0100
Message-Id: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
From: Fred Baker <fred@cisco.com>
To: v6ops@ops.ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Rogue RA WGLC
Date: Tue, 18 Nov 2008 13:22:02 -0600
Cc: kurtis@kurtis.pp.se, rbonica@juniper.net
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 18 Nov 2008 19:23:12.0466 (UTC) FILETIME=[19076B20:01C949B3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=666; t=1227036193; x=1227900193;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Rogue=20RA=20WGLC
	|Sender:=20;
	bh=rZkg7BnWnBVolAAkwqg38jzlcgvo9GyIamMe/KUlHb8=;
	b=gPQoKZyH8CrUBZya0JgNxP2vGzhg/vxaSmPlLI4vWxqApkgSolV4M4v1lF
	ax97tPgkS+h3IESXC8W4VhCaDLEWiFtaWf6TpRAN4kaLp0qafnNQiplzqwOD
	yq+a7N+0fZ;
Authentication-Results: ams-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is to initiate a two week working group last call of draft-chown- 
v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt. Please  
read these drafts now. If you find nits (spelling errors, minor  
suggested wording changes, etc), comment to the authors; if you find  
greater issues, such as disagreeing with a statement or finding  
additional issues that need to be addressed, please post your comments  
to the list.

We are looking specifically for comments on the importance of the  
document as well as its content. If you have read the document and  
believe it to be of operational utility, that is also an important  
comment to make.



From owner-v6ops@ops.ietf.org  Tue Nov 18 11:55:07 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1298B3A6B0D
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 11:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 iRS6YUjv67RM
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 11:55:06 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 50B483A6AF1
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 11:55:06 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2WdX-000DUo-Mw
	for v6ops-data@psg.com; Tue, 18 Nov 2008 19:53:23 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <iljitsch@muada.com>)
	id 1L2WdR-000DUJ-VU
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 19:53:20 +0000
Received: from [IPv6:2001:df8::16:223:12ff:fe56:36b2] ([IPv6:2001:df8:0:16:223:12ff:fe56:36b2])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id mAIJqREP000951
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 18 Nov 2008 20:52:29 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Message-Id: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: v6ops Operations <v6ops@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: NAT64 support in CPE?
Date: Tue, 18 Nov 2008 13:53:11 -0600
Cc: marcelo bagnulo <marcelo@it.uc3m.es>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Fred,

I looked over draft-baker-behave-v4v6-framework-00 again, but I  
couldn't find any place where the CPE would perform any actions to  
enable NAT64 or make NAT64 work better. Did I miss something?

There are some DNS64 corner cases, but in general I don't believe CPEs  
would have to do anything to make a NAT64 type solution work.



From owner-v6ops@ops.ietf.org  Tue Nov 18 12:35:00 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D71728C1F3
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 12:35:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.415
X-Spam-Level: 
X-Spam-Status: No, score=-105.415 tagged_above=-999 required=5
	tests=[AWL=-0.920, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 bGxiWWPtKk-Y
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 12:34:59 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 59C0528C15F
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 12:34:59 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2XEt-000Fo4-IY
	for v6ops-data@psg.com; Tue, 18 Nov 2008 20:31:59 +0000
Received: from [171.68.10.87] (helo=sj-iport-5.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L2XEo-000Fna-73
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 20:31:56 +0000
X-IronPort-AV: E=Sophos;i="4.33,627,1220227200"; 
   d="scan'208";a="53303876"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
  by sj-iport-5.cisco.com with ESMTP; 18 Nov 2008 20:30:53 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAIKUrV7027889;
	Tue, 18 Nov 2008 12:30:53 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mAIKUrFp002342;
	Tue, 18 Nov 2008 20:30:53 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 12:30:53 -0800
Received: from [130.129.95.58] ([10.21.146.34]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 12:30:52 -0800
Cc: v6ops Operations <v6ops@ops.ietf.org>,
        marcelo bagnulo <marcelo@it.uc3m.es>
Message-Id: <2AAB63BC-9E43-4960-B7AC-BB09FC055AA7@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: NAT64 support in CPE?
Date: Tue, 18 Nov 2008 14:30:51 -0600
References: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 18 Nov 2008 20:30:53.0222 (UTC) FILETIME=[8D6D9C60:01C949BC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3379; t=1227040253; x=1227904253;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20NAT64=20support=20in=20CPE?
	|Sender:=20;
	bh=8NfYZvf8DQOCoRpGWfVBVngOusSeSNzByDyyagLJi9g=;
	b=nmRVvxSgnfjB08L66MyqJiQ0m0GLNN4h5bSZuWgU4UAqlG2ZpIuSIXxo9p
	pfJziOmu26Ye1Y8tHpb70GRzIwutxO5JIBqflXPKmmN465TP5IHBrQks50iA
	EJkwMTRc7i;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 18, 2008, at 1:53 PM, Iljitsch van Beijnum wrote:

> Fred,
>
> I looked over draft-baker-behave-v4v6-framework-00 again, but I  
> couldn't find any place where the CPE would perform any actions to  
> enable NAT64 or make NAT64 work better. Did I miss something?
>
> There are some DNS64 corner cases, but in general I don't believe  
> CPEs would have to do anything to make a NAT64 type solution work.

For those that miss the referent, look at
http://tools.ietf.org/html/draft-baker-behave-v4v6-framework
   "Framework for IPv4/IPv6 Translation", Fred Baker, 26-Oct-08,
   <draft-baker-behave-v4v6-framework-00.txt>


The case that comes quickly to mind is the second case discussed in  
1.5.1. The following is cut/paste from the draft:

                    ----------
                 ///          \\\
                //    IPv6      \\              192.168.1.0/24
              //      ISP         \\    +------+2001:db8:0:1::0/64
             |/                    \|   |      +---------------
             |  Allocates           |   |      |
            |   2001:db8::/60 to     |  |CPE   |192.168.2.0/24
            |   Customer             |  |Router|2001:db8:0:2::0/64
            |                        +--+      +---------------
            |   Doesn't know it,     |  |      |
             |  but sees customer   |   |      |192.168.3.0/24
             |\ IPv4 as            /|   |      |2001:db8:0:3::0/64
              \\2001:db8::a.b.c.d //    |      +---------------
                \\              //      +------+
                 \\\          ///
                    ----------     LIR prefix is 2001:db8::0/96

                    Figure 2: Customer dual stack network

    Figure 2 creates transition options to a customer network connected
    to an IPv6-only ISP, or some equivalent relationship.  The customer
    might internally be using traditional IPv4 with NAT services, and  
the
    ISP might change its connection to an IPv6-only network and  
encourage
    it to transition.  If the ISP assigns a /60 prefix to a SOHO, for
    example, the CPE router in the SOHO could distribute several dual
    stack subnets internally, one for wireless and one for each of
    several fixed LANs (the entertainment system, his office, her  
office,
    etc).  One of the /64 prefixes would be dedicated to representing  
the
    SOHO's IPv4 addresses in the ISP or the IPv4 network beyond it, and
    the other prefixes for the various internal subnets.  Internally,  
the
    subnets might carry prefix pairs 192.168.n.0/24 and 2001:db8:0.n::/ 
64
    for n in 1..15 (1..0xF), and externally might appear as 2001:db8:0:
    n::/64 for the IPv6 subnets and 2001:db8::192.168.n.0/120 for the
    IPv4 devices.  Note that to connect to an IPv4-only network beyond,
    RFC 1918 addresses would have to be statefully mapped using
    traditional IPv4 mechanisms somewhere; if this is done by the ISP,
    collusion on address mapping is required, and the case in
    Section 1.5.4 is probably a better choice.

    In this environment, the key issue is that one wants a prefix that
    enables the entire [RFC1918] address space to be embedded in a  
single
    /64 prefix, with the assumption that any routing structure behind  
the
    translator is managed by IPv4 routing.





From owner-v6ops@ops.ietf.org  Tue Nov 18 12:35:10 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C8A128C204
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 12:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.338
X-Spam-Level: 
X-Spam-Status: No, score=-105.338 tagged_above=-999 required=5
	tests=[AWL=-0.843, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 Ro9RxuaiNIoo
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 12:35:09 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6000528C1F3
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 12:35:09 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2XGU-000Ful-GW
	for v6ops-data@psg.com; Tue, 18 Nov 2008 20:33:38 +0000
Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L2XGH-000Ft1-Ao
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 20:33:28 +0000
X-IronPort-AV: E=Sophos;i="4.33,627,1220227200"; 
   d="scan'208";a="197106121"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
  by sj-iport-6.cisco.com with ESMTP; 18 Nov 2008 20:33:20 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAIKXKWS006393;
	Tue, 18 Nov 2008 12:33:20 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mAIKXK7T004751;
	Tue, 18 Nov 2008 20:33:20 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 12:33:18 -0800
Received: from [130.129.95.58] ([10.21.146.34]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 12:33:18 -0800
Cc: v6ops Operations <v6ops@ops.ietf.org>,
        marcelo bagnulo <marcelo@it.uc3m.es>
Message-Id: <6DB49E41-FFDF-462E-B07B-1E73C4345940@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: NAT64 support in CPE?
Date: Tue, 18 Nov 2008 14:33:17 -0600
References: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 18 Nov 2008 20:33:18.0677 (UTC) FILETIME=[E4204850:01C949BC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=463; t=1227040400; x=1227904400;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20NAT64=20support=20in=20CPE?
	|Sender:=20;
	bh=+rQ0JhdzltCwM7+LPHT40+F4iqbGLrzPEn+wrzQmXtk=;
	b=Z0Tndg7Uw9r3NsF7Innl6y+9zrddyr9bFxr/YKmfaJHzqHPdmHFk5KkECv
	3h8uQ4lK4ams7mtLxYr4Wb20sPOdj9NHGl2WHsNC4JCLOiwEl0VVbDlUqpoE
	cNVcJQci844UM1pa36UU8WsSGlNtCMTS2p+pWazAUBGHI7xeKyTq8=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 18, 2008, at 1:53 PM, Iljitsch van Beijnum wrote:
> I looked over draft-baker-behave-v4v6-framework-00 again, but I  
> couldn't find any place where the CPE would perform any actions to  
> enable NAT64 or make NAT64 work better. Did I miss something?

By the way, as I recall the outcome of the Montreal interim, the  
question isn't "nat64", it is "the outcome of behave", which is a  
merger of IVI and NAT64. Did you understand differently?




From owner-v6ops@ops.ietf.org  Tue Nov 18 12:39:08 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEE333A67D1
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 12:39:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 XONE8z1UzZFB
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 12:39:07 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B062B3A677C
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 12:39:07 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2XKp-000GC1-4B
	for v6ops-data@psg.com; Tue, 18 Nov 2008 20:38:07 +0000
Received: from [2001:1888:0:1:230:48ff:fe5b:3b8c] (helo=outgoing02.lava.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <tony@lava.net>)
	id 1L2XKh-000GBR-15
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 20:38:04 +0000
Received: from malasada.lava.net (malasada.lava.net [64.65.64.17])
	by outgoing02.lava.net (Postfix) with ESMTPS id 2264D170BBA;
	Tue, 18 Nov 2008 10:37:51 -1000 (HST)
Date: Tue, 18 Nov 2008 10:37:51 -1000 (HST)
From: Antonio Querubin <tony@lava.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: v6ops Operations <v6ops@ops.ietf.org>
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
In-Reply-To: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com>
Message-ID: <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net>
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Tue, 18 Nov 2008, Iljitsch van Beijnum wrote:

> So in the case that a CPE vendor doesn't want to implement the DHCPv6 server 
> necessary for cascading, I think we should mandate that the first CPE, when 
> it detects that a secondary CPE is connected on the LAN side, becomes a 
> transparent bridge. (Insert DHCPv6 option to make this happen.)

I'd prefer that each CPE router default to sub-delegating a fraction 
(user-configurable but with reasonable defaults) of the prefix delegated 
from it's 'upstream' CPE router.  The fraction would determine how many 
levels of nesting are possible and how large the downstream CPE fan-out is 
at each nesting level.  This might be more scalable since it means more 
consistent CPE behaviour regardless of whether it's the first downstream 
CPE router or the last.  One problem though is how does a CPE know when to 
actually delegate/reserve prefixes to a connected device which may or may 
not be a router.

> In the case of non-functional IPv6 but working IPv4, it's probably best to 
> not let hosts autoconfigure addresses and also not have RAs create default 
> gateways, because some OSes take the former to mean that there is working 
> IPv6 and others the latter.

How about auto-enabling 6to4 assuming it can actually reach a 
192.88.99l.1 gateway?


Antonio Querubin
whois:  AQ7-ARIN



From owner-v6ops@ops.ietf.org  Tue Nov 18 12:46:17 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 379D13A6895
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 12:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 XHuj4psWzSyV
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 12:46:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 656573A677C
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 12:46:16 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2XRM-000Gjw-U2
	for v6ops-data@psg.com; Tue, 18 Nov 2008 20:44:52 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <iljitsch@muada.com>)
	id 1L2XRG-000Gj7-1h
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 20:44:49 +0000
Received: from [IPv6:2001:df8::16:223:12ff:fe56:36b2] ([IPv6:2001:df8:0:16:223:12ff:fe56:36b2])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id mAIKhq57002000
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 18 Nov 2008 21:43:54 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Cc: v6ops Operations <v6ops@ops.ietf.org>,
        marcelo bagnulo <marcelo@it.uc3m.es>
Message-Id: <1EA3753F-33C6-4FD0-B753-44D7F716C959@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <6DB49E41-FFDF-462E-B07B-1E73C4345940@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: NAT64 support in CPE?
Date: Tue, 18 Nov 2008 14:44:37 -0600
References: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com> <6DB49E41-FFDF-462E-B07B-1E73C4345940@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 18 nov 2008, at 14:33, Fred Baker wrote:

>> I looked over draft-baker-behave-v4v6-framework-00 again, but I  
>> couldn't find any place where the CPE would perform any actions to  
>> enable NAT64 or make NAT64 work better. Did I miss something?

> By the way, as I recall the outcome of the Montreal interim, the  
> question isn't "nat64", it is "the outcome of behave", which is a  
> merger of IVI and NAT64. Did you understand differently?

I just use "NAT64" as "any type of translation between IPv6 clients  
and IPv4 servers" here because I only have limited room for fast  
changing terminology in my head...



From owner-v6ops@ops.ietf.org  Tue Nov 18 13:09:02 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D5E33A6B2B
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 13:09:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.369
X-Spam-Level: 
X-Spam-Status: No, score=-1.369 tagged_above=-999 required=5
	tests=[AWL=-0.874, 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 jDyttYYjLbfe
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 13:09:01 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 418D63A682A
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 13:09:01 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2Xmv-000Ibc-CW
	for v6ops-data@psg.com; Tue, 18 Nov 2008 21:07:09 +0000
Received: from [209.85.198.224] (helo=rv-out-0506.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <brian.e.carpenter@gmail.com>)
	id 1L2Xmp-000IbM-NC
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 21:07:06 +0000
Received: by rv-out-0506.google.com with SMTP id b25so3143403rvf.41
        for <v6ops@ops.ietf.org>; Tue, 18 Nov 2008 13:07:03 -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=HHqNSu6Hji+DGyGaQNiZUeXYCTK7qk1kayn8kofWb6A=;
        b=FAdr436qLbD+P7nRFnzWCa6FgU52LvC+MHBCZKa4VUE17KD54GeXljFrocW41ytXFk
         9BixO10HhzsB4QTlWetqSb42SiSnN9vJyJr6Ewqtb6DCDhvLiAWkhvEkSS6goRr2pDMG
         YQKJx4y+1/OL/BAt8KgrK50ZeGcj2NoG14Sfc=
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=FQyem0aQ42U2klYJYjZqBcMfS1Bg7KQ+iIAtQaLHnRusdAFJXNvM0LjRh+sqRVLmmn
         4nn+oMHY+ixbtMx407kkBkTtY89TqGz313xu9H2N2gkroFc/zy2ZBHVArnS0vL+8V/PT
         sYqqi5TQxZcOkYBV2Z+S37ik3fFaw867Epq8o=
Received: by 10.140.185.1 with SMTP id i1mr153093rvf.72.1227042423166;
        Tue, 18 Nov 2008 13:07:03 -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 g31sm13683706rvb.7.2008.11.18.13.07.01
        (version=SSLv3 cipher=RC4-MD5);
        Tue, 18 Nov 2008 13:07:02 -0800 (PST)
Message-ID: <49232E73.6030400@gmail.com>
Date: Wed, 19 Nov 2008 10:06:59 +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: Antonio Querubin <tony@lava.net>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, 
 v6ops Operations <v6ops@ops.ietf.org>
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com> <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net>
In-Reply-To: <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 2008-11-19 09:37, Antonio Querubin wrote:
...
> 
> How about auto-enabling 6to4 assuming it can actually reach a
> 192.88.99l.1 gateway?

That doesn't guarantee connectivity; you actually need to see an
IPv6 reply before you know that 6to4 is working. So you really
need to enable 6to4, run a reachability test, and disable it if
no response.

    Brian



From owner-v6ops@ops.ietf.org  Tue Nov 18 13:15:56 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 018DF3A6A24
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 13:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.293
X-Spam-Level: 
X-Spam-Status: No, score=-105.293 tagged_above=-999 required=5
	tests=[AWL=-0.798, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 gL-3qK02yw+L
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 13:15:55 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 242AE3A6809
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 13:15:55 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2Xtq-000J2a-Tq
	for v6ops-data@psg.com; Tue, 18 Nov 2008 21:14:18 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L2Xtk-000J1l-UY
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 21:14:16 +0000
X-IronPort-AV: E=Sophos;i="4.33,627,1220227200"; 
   d="scan'208";a="116928130"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
  by sj-iport-3.cisco.com with ESMTP; 18 Nov 2008 21:14:12 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAILECKs013660;
	Tue, 18 Nov 2008 13:14:12 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAILE4F6025530;
	Tue, 18 Nov 2008 21:14:12 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 13:14:11 -0800
Received: from [130.129.95.58] ([10.21.126.176]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 13:14:10 -0800
Cc: v6ops Operations <v6ops@ops.ietf.org>,
        marcelo bagnulo <marcelo@it.uc3m.es>
Message-Id: <739DAF2A-7702-45F1-A017-0DFFC2CF8A05@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <1EA3753F-33C6-4FD0-B753-44D7F716C959@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: NAT64 support in CPE?
Date: Tue, 18 Nov 2008 15:14:09 -0600
References: <D34A86EB-FF52-4F13-ACBB-9891D8C5F6E0@muada.com> <6DB49E41-FFDF-462E-B07B-1E73C4345940@cisco.com> <1EA3753F-33C6-4FD0-B753-44D7F716C959@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 18 Nov 2008 21:14:10.0543 (UTC) FILETIME=[998D57F0:01C949C2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=722; t=1227042852; x=1227906852;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20NAT64=20support=20in=20CPE?
	|Sender:=20;
	bh=JoHP1oldtIozdGBA1TNlxYP6+C4mcEwh9FzoBqpfV1s=;
	b=kWWLnsJ6yWoZZXL1OxK8l7VeDBD59O7D2uCi9EKj2Il5jImJsvVzGsI6qQ
	mIO1UQj03/eKxv6P2sEvdj0fWrPYnzlWDil4/qfCqhS2h9U1cGmp2lN/rv4q
	LO12+Y3ZGz;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 18, 2008, at 2:44 PM, Iljitsch van Beijnum wrote:

> On 18 nov 2008, at 14:33, Fred Baker wrote:
>
>>> I looked over draft-baker-behave-v4v6-framework-00 again, but I  
>>> couldn't find any place where the CPE would perform any actions to  
>>> enable NAT64 or make NAT64 work better. Did I miss something?
>
>> By the way, as I recall the outcome of the Montreal interim, the  
>> question isn't "nat64", it is "the outcome of behave", which is a  
>> merger of IVI and NAT64. Did you understand differently?
>
> I just use "NAT64" as "any type of translation between IPv6 clients  
> and IPv4 servers" here because I only have limited room for fast  
> changing terminology in my head...

:-)



From owner-v6ops@ops.ietf.org  Tue Nov 18 14:05:09 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D607128C27F
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 14:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.937
X-Spam-Level: 
X-Spam-Status: No, score=-0.937 tagged_above=-999 required=5
	tests=[AWL=-0.500, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, 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 bdnVhwL6VL4L
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 14:05:09 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E6F153A677E
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 14:05:08 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2Ydq-000LsI-VN
	for v6ops-data@psg.com; Tue, 18 Nov 2008 22:01:50 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1L2Yde-000Lqy-QC
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 22:01:48 +0000
Received: (qmail 70721 invoked by uid 1007); 18 Nov 2008 22:01:37 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=oEZEd8Ywo6pOHyUK9ZNGhG+FZowqTBsC8z7K5C1V1OW+2joOKG4We4Uo2yvaclBZ  ;
Date: Tue, 18 Nov 2008 23:01:37 +0100
From: Gert Doering <gert@space.net>
To: james woodyatt <jhw@apple.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>,
  Eric Klein <EricLKlein@softhome.net>, IPv6 Operations <v6ops@ops.ietf.org>,
  Behave WG <behave@ietf.org>
Subject: Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
Message-ID: <20081118220136.GE89033@Space.Net>
References: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com> <60FD682C-1436-493F-995D-4B2A7241D398@apple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <60FD682C-1436-493F-995D-4B2A7241D398@apple.com>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Hi,

On Mon, Nov 17, 2008 at 11:22:14PM -0600, james woodyatt wrote:
> I am so *so* tired of making excuses for bad code.  Just once, I'd  
> like to be able to say, "I see your coders thought it would be a good  
> idea to store IP addresses in a persistent store without any cache  
> coherency protocol, and now you can't renumber your network without  
> eating the time and expense of qualifying a radical new implementation  
> of your hugely business-critical software application.  You know  
> what?  That's your own fault.  Not ours.  p.s. I bet you'll read that  
> tech-note next time, right?"

OK, I bite.  What answer do you give to folks that need to renumber
things like site-to-site VPN endpoints, which affects lots of configuration 
to be changed by *other* folks (their VPN peers)?

This happens to be the one of the main issues being brought forward by
people that want stable addresses.

(I'll go through the draft itself some time tomorrow)

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From owner-v6ops@ops.ietf.org  Tue Nov 18 14:34:17 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EAB3728C291
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 14:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001,
	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 FbgMDpJ2vm67
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 14:34:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 8973D3A6B29
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 14:34:15 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2Z7G-000NZ5-9r
	for v6ops-data@psg.com; Tue, 18 Nov 2008 22:32:14 +0000
Received: from [2001:41d0:1:a0d6::401:1983] (helo=yop.chewa.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <rdenis@simphalempin.com>)
	id 1L2Z7A-000NYb-GK
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 22:32:11 +0000
Received: from leon.remlab.net (unknown [IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id 381453B03;
	Tue, 18 Nov 2008 23:32:06 +0100 (CET)
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <rdenis@simphalempin.com>
Organization: Remlab.net
To: Antonio Querubin <tony@lava.net>
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
Date: Wed, 19 Nov 2008 00:32:00 +0200
User-Agent: KMail/1.9.10
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
 v6ops Operations <v6ops@ops.ietf.org>
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com> <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net>
In-Reply-To: <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200811190032.00983.rdenis@simphalempin.com>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Tuesday 18 November 2008 22:37:51 Antonio Querubin, you wrote:
> > In the case of non-functional IPv6 but working IPv4, it's probably best
> > to not let hosts autoconfigure addresses and also not have RAs create
> > default gateways, because some OSes take the former to mean that there =
is
> > working IPv6 and others the latter.
>
> How about auto-enabling 6to4 assuming it can actually reach a
> 192.88.99l.1 gateway?

How do you measure that? How do you know that there is no stateful firewall=
 in=20
front of your public IPv4 address?

I suspect broken automagic 6to4 gatewaying is the single most common reason=
=20
for broken IPv6 connectivity in the real world right now.

=2D-=20
R=E9mi Denis-Courmont



From owner-v6ops@ops.ietf.org  Tue Nov 18 14:36:17 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B14123A67AB
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 14:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001,
	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 P3f4-grxZIDc
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 14:36:17 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 03B523A68A0
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 14:36:17 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2ZAH-000NnB-Mu
	for v6ops-data@psg.com; Tue, 18 Nov 2008 22:35:21 +0000
Received: from [2001:41d0:1:a0d6::401:1983] (helo=yop.chewa.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <rdenis@simphalempin.com>)
	id 1L2ZAC-000Nmh-Pc
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 22:35:18 +0000
Received: from leon.remlab.net (unknown [IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id 61B0D3B06;
	Tue, 18 Nov 2008 23:35:12 +0100 (CET)
From: "=?utf-8?q?R=C3=A9mi?= Denis-Courmont" <rdenis@simphalempin.com>
Organization: Remlab.net
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
Date: Wed, 19 Nov 2008 00:35:08 +0200
User-Agent: KMail/1.9.10
Cc: Antonio Querubin <tony@lava.net>,
 Iljitsch van Beijnum <iljitsch@muada.com>,
 v6ops Operations <v6ops@ops.ietf.org>
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com> <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net> <49232E73.6030400@gmail.com>
In-Reply-To: <49232E73.6030400@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811190035.08299.rdenis@simphalempin.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Tuesday 18 November 2008 23:06:59 Brian E Carpenter, you wrote:
> On 2008-11-19 09:37, Antonio Querubin wrote:
> ...
>
> > How about auto-enabling 6to4 assuming it can actually reach a
> > 192.88.99l.1 gateway?
>
> That doesn't guarantee connectivity; you actually need to see an
> IPv6 reply before you know that 6to4 is working. So you really
> need to enable 6to4, run a reachability test, and disable it if
> no response.

Even then. It might be working... until the stateful firewall expires your=
=20
proto-41 pinhole. Here comes the 6to4 blackhole.

=2D-=20
R=C3=A9mi Denis-Courmont



From owner-v6ops@ops.ietf.org  Tue Nov 18 15:30:12 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A313E3A6945
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 15:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.57
X-Spam-Level: 
X-Spam-Status: No, score=-4.57 tagged_above=-999 required=5 tests=[AWL=-0.676,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4,
	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 7+DMbNHxRp-h
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 15:30:11 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1E04D3A6819
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 15:30:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2Zyd-000167-7E
	for v6ops-data@psg.com; Tue, 18 Nov 2008 23:27:23 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <shemant@cisco.com>)
	id 1L2ZyX-00015s-LL
	for v6ops@ops.ietf.org; Tue, 18 Nov 2008 23:27:20 +0000
X-IronPort-AV: E=Sophos;i="4.33,627,1220227200"; 
   d="scan'208,217";a="28311831"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
  by rtp-iport-1.cisco.com with ESMTP; 18 Nov 2008 23:27:16 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAINRGwe020980;
	Tue, 18 Nov 2008 18:27:16 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mAINRGP9002943;
	Tue, 18 Nov 2008 23:27:16 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Tue, 18 Nov 2008 18:27:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C949D5.30F7D011"
Subject: strong host model sentence in cpe rtr -03 version 
Date: Tue, 18 Nov 2008 18:27:15 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42797@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: strong host model sentence in cpe rtr -03 version 
Thread-Index: AclJ1TAs3j0ZOSvbQUGeVycujVPdng==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>, <v6ops@ops.ietf.org>
Cc: "Shin Miyakawa" <miyakawa@nttv6.jp>
X-OriginalArrivalTime: 18 Nov 2008 23:27:16.0221 (UTC) FILETIME=[31631AD0:01C949D5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5143; t=1227050836; x=1227914836;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20strong=20host=20model=20sentence=20in=20cpe=20r
	tr=20-03=20version=20
	|Sender:=20
	|To:=20=22Dave=20Thaler=22=20<dthaler@windows.microsoft.com
	>,=20<v6ops@ops.ietf.org>;
	bh=ktPZMSTfDP14WW5GW/fzEQUINLdJdkHxz4n26UPpcxs=;
	b=G53aYrH5ZUxqGh4Fa3sG3q6sWS8D+RmviY1b+mrbuuROpUCnjj+v6r6H2o
	sImE4KxHFLELpZYeK+uFbP6dKARAhOAHroY9BBGkMf/HAoBMCrQl4HBMHhJe
	rjaysWLoad;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C949D5.30F7D011
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dave,
=20
Since you questioned strong host model during our IETF 73 v6ops prezo,
here is a closure once I had time to recollect my thoughts on the
subject.  First, I take the strong vs. weak host models for traffic
forwarding by a host on received traffic.  As we told in the prezo that
NTT in Japan runs routing code NTT developed for a Windows PC.  So for
their deployment if Windows OS changes between pre-Vista to Vista from
weak to strong host model, then we do have a problem for the NTT routing
software running on Vista.  In the CPE Rtr Unnumbered model, the WAN
interface of the Rtr has only a Link-local address.   A strong host
model needs a global IPv6 address on the WAN interface to receive global
IPV6 traffic - NTT runs PPPOE.  That is why the text below was added to
the -03 version of the CPE Rtr.
=20
[The Unnumbered model is incompatible with the strong host model on the
CPE router. The unnumbered model may be inappropriate for use with
certain deployments where a device that uses the strong host model can
operate as a CPE Router.]
=20
http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-router-03.txt
=20
I don't have any more details on the NTT deployment like if any other
hosts are behind their Windows PC that is being used as a CPE Rtr - if
we did have such host behind the rtr PC, the the global address assigned
to the other PCs via IA_PD sub-delegation, then the global address on
the LAN could be used to source packet our the WAN interface to the SP.
I am told the same Windows PC acting as a CPE Rtr, is also the PC being
used by the user at home for using Internet services etc.  =20
=20
Hemant

------_=_NextPart_001_01C949D5.30F7D011
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2>Dave,</FONT></SPAN></DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial size=3D2>Since =
you questioned=20
strong host model during our IETF 73 v6ops prezo, here is a closure once =
I had=20
time to recollect my thoughts on the subject.&nbsp; First, I take the =
strong vs.=20
weak host models for traffic forwarding by a host on received =
traffic.&nbsp; As=20
we told in the prezo that NTT in Japan runs routing code NTT developed =
for a=20
Windows PC.&nbsp; So for their deployment if Windows OS changes between=20
pre-Vista to Vista from weak to strong host model, then we do have a =
problem for=20
the NTT routing software running on Vista.&nbsp; In the CPE Rtr =
Unnumbered=20
model, the WAN interface of the Rtr has only a Link-local =
address.&nbsp;&nbsp; A=20
strong host model needs a global IPv6 address on the WAN interface to =
receive=20
global IPV6 traffic - NTT runs PPPOE. &nbsp;That is why the text below =
was added=20
to the -03 version of the CPE Rtr.</FONT></SPAN></DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D939065322-18112008>[The Unnumbered model is =
incompatible with=20
the strong host model on the CPE router. The unnumbered model may be=20
inappropriate for use with certain deployments where a device that uses =
the=20
strong host model can operate as a CPE Router.]</SPAN></DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-router=
-03.txt">http://www.ietf.org/internet-drafts/draft-wbeebee-ipv6-cpe-route=
r-03.txt</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial size=3D2>I =
don't have any=20
more details on the NTT deployment like if any other hosts are behind =
their=20
Windows PC that is being used as a CPE Rtr - if we&nbsp;did have such =
host=20
behind the&nbsp;rtr PC, the the&nbsp;global address assigned to the =
other PCs=20
via IA_PD sub-delegation, then the global address on the LAN could be=20
used&nbsp;to source packet&nbsp;our the WAN&nbsp;interface to the SP. =
&nbsp;I am=20
told the same Windows PC acting as a CPE Rtr, is also the PC being used =
by the=20
user at home for using Internet services etc.&nbsp;&nbsp; =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D939065322-18112008><FONT face=3DArial=20
size=3D2>Hemant</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C949D5.30F7D011--



From owner-v6ops@ops.ietf.org  Tue Nov 18 16:33:54 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC6953A6B2F
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 16:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.234
X-Spam-Level: 
X-Spam-Status: No, score=-105.234 tagged_above=-999 required=5
	tests=[AWL=-0.739, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 bDiOTE8KOZqA
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 16:33:54 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C9A2B3A6947
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 16:33:53 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2axF-00054F-Nr
	for v6ops-data@psg.com; Wed, 19 Nov 2008 00:30:01 +0000
Received: from [17.254.13.23] (helo=mail-out4.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1L2axA-00053N-Px
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 00:29:59 +0000
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52])
	by mail-out4.apple.com (Postfix) with ESMTP id 4631B4762E6C;
	Tue, 18 Nov 2008 16:29:56 -0800 (PST)
Received: from relay14.apple.com (unknown [127.0.0.1])
	by relay14.apple.com (Symantec Brightmail Gateway) with ESMTP id 2D8C328090;
	Tue, 18 Nov 2008 16:29:56 -0800 (PST)
X-AuditID: 11807134-a6bbcbb000000f08-1a-49235e033dd1
Received: from [17.151.119.116] (unknown [17.151.119.116])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay14.apple.com (Apple SCV relay) with ESMTP id CBAFD28043;
	Tue, 18 Nov 2008 16:29:55 -0800 (PST)
Cc: IPv6 Operations <v6ops@ops.ietf.org>,
 Behave WG <behave@ietf.org>
Message-Id: <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com>
From: james woodyatt <jhw@apple.com>
To: Gert Doering <gert@space.net>
In-Reply-To: <20081118220136.GE89033@Space.Net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
Date: Tue, 18 Nov 2008 18:29:54 -0600
References: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com> <60FD682C-1436-493F-995D-4B2A7241D398@apple.com> <20081118220136.GE89033@Space.Net>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 18, 2008, at 16:01, Gert Doering wrote:
> On Mon, Nov 17, 2008 at 11:22:14PM -0600, james woodyatt wrote:
>> I am so *so* tired of making excuses for bad code.  Just once, I'd
>> like to be able to say, "I see your coders thought it would be a good
>> idea to store IP addresses in a persistent store without any cache
>> coherency protocol, and now you can't renumber your network without
>> eating the time and expense of qualifying a radical new  
>> implementation
>> of your hugely business-critical software application.  You know
>> what?  That's your own fault.  Not ours.  p.s. I bet you'll read that
>> tech-note next time, right?"
>
> OK, I bite.  What answer do you give to folks that need to renumber
> things like site-to-site VPN endpoints, which affects lots of  
> configuration
> to be changed by *other* folks (their VPN peers)?

Please, help me understand why solving this problem requires storing  
IP addresses in persistent storage without a coherent caching  
protocol.  I'm not seeing it-- probably because I'm not sure I  
understand the nature and scope of the problem very well.

For the sake of argument, I'll accept that reasonable people currently  
perceive it to be necessary.  My hunch is that those folks should  
probably be using DNS-SD instead of the fragile cruftiness they're  
struggling against now.  Maybe if I understood the problem better, I  
could suggest a more detailed alternative to their current solution.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Tue Nov 18 22:31:47 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC9443A6A18
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 22:31:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.384
X-Spam-Level: 
X-Spam-Status: No, score=-102.384 tagged_above=-999 required=5
	tests=[AWL=0.215, BAYES_00=-2.599, 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 s-RSKI0oxJSJ
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 22:31:47 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0C6743A6990
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 22:31:47 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2gV1-000OlF-KJ
	for v6ops-data@psg.com; Wed, 19 Nov 2008 06:25:15 +0000
Received: from [2001:670:86:3001::1] (helo=netcore.fi)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <pekkas@netcore.fi>)
	id 1L2gUu-000Okb-HA
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 06:25:11 +0000
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id mAJ6NtGE023068;
	Wed, 19 Nov 2008 08:23:55 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id mAJ6Ns8O023065;
	Wed, 19 Nov 2008 08:23:54 +0200
Date: Wed, 19 Nov 2008 08:23:54 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Fred Baker <fred@cisco.com>
cc: v6ops@ops.ietf.org, kurtis@kurtis.pp.se, rbonica@juniper.net
Subject: Re: Rogue RA WGLC
In-Reply-To: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
Message-ID: <alpine.LRH.2.00.0811190822300.22834@netcore.fi>
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.94.1/8649/Wed Nov 19 00:31:11 2008 on otso.netcore.fi
X-Virus-Status: Clean
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Tue, 18 Nov 2008, Fred Baker wrote:
> This is to initiate a two week working group last call of 
> draft-chown-v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt.

At least according to the I-D tracker, the former is not even a WG 
document yet, so it's not clear how we could have a WG LC on it. Is 
this an omission in I-D tracker document state or something else?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



From owner-v6ops@ops.ietf.org  Tue Nov 18 22:37:30 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 840C23A6883
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 18 Nov 2008 22:37:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5
	tests=[AWL=0.195, BAYES_00=-2.599, 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 c5x4GKhfNlz2
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 18 Nov 2008 22:37:29 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id A207F3A63EC
	for <v6ops-archive@lists.ietf.org>; Tue, 18 Nov 2008 22:37:29 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2geu-000PPC-23
	for v6ops-data@psg.com; Wed, 19 Nov 2008 06:35:28 +0000
Received: from [2001:670:86:3001::1] (helo=netcore.fi)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <pekkas@netcore.fi>)
	id 1L2gen-000POW-U4
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 06:35:24 +0000
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id mAJ6Z3AJ023341;
	Wed, 19 Nov 2008 08:35:03 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id mAJ6Z2TY023337;
	Wed, 19 Nov 2008 08:35:03 +0200
Date: Wed, 19 Nov 2008 08:35:02 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: Antonio Querubin <tony@lava.net>,
        Iljitsch van Beijnum <iljitsch@muada.com>,
        v6ops Operations <v6ops@ops.ietf.org>
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
In-Reply-To: <49232E73.6030400@gmail.com>
Message-ID: <alpine.LRH.2.00.0811190825240.22834@netcore.fi>
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com> <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net> <49232E73.6030400@gmail.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.94.1/8649/Wed Nov 19 00:31:11 2008 on otso.netcore.fi
X-Virus-Status: Clean
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Wed, 19 Nov 2008, Brian E Carpenter wrote:
>> How about auto-enabling 6to4 assuming it can actually reach a
>> 192.88.99l.1 gateway?
>
> That doesn't guarantee connectivity; you actually need to see an
> IPv6 reply before you know that 6to4 is working. So you really
> need to enable 6to4, run a reachability test, and disable it if
> no response.

Well, while this is one possible approach, and it may be the simplest 
test from a human perspective, an implementation could do a test 
without enabling 6to4.

You just need to craft a packet using a raw socket that resembles that 
kind of 6to4 packet, and watch for replies.  As an example of how 
Microsoft has done it, the implementation sends a proto-41 packet with 
IPv6 TTL=1 to an IPv6 address corresponding relay's v4 address, so the 
relay will return _something_ if connectivity at least up to the relay 
is working, the relay has v6 enabled, etc.

Live example from a relay:

08:31:01.202671 IP (tos 0x0, ttl 119, id 174, offset 0, flags [none], proto IPv6 (41), length 68) 93.106.184.x > 192.88.99.1: IP6 (hlim 1, next-header ICMPv6 (58) payload length: 8) 2002:5d6a:b8xx::5d6a:b8xx > 2002:c058:6301::c058:6301: [icmp6 sum ok] ICMP6, echo request, length 8, seq 2
08:31:01.202752 IP (tos 0x0, ttl 40, id 32297, offset 0, flags [none], proto IPv6 (41), length 116) 192.88.99.1 > 93.106.184.x: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 56) 2002:c058:6301::1741 > 2002:5d6a:b8xx::5d6a:b8xx: [icmp6 sum ok] ICMP6, time exceeded in-transit, length 56 for 2002:c058:6301::c058:6301

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



From owner-v6ops@ops.ietf.org  Wed Nov 19 01:25:33 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF51E28C0E4
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 01:25:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.606
X-Spam-Level: 
X-Spam-Status: No, score=-0.606 tagged_above=-999 required=5
	tests=[AWL=-0.769, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_33=0.6, 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 Pf24KO8vvtKz
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 01:25:33 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id BFA8F3A6B29
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 01:25:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2jGC-0008Dk-CO
	for v6ops-data@psg.com; Wed, 19 Nov 2008 09:22:08 +0000
Received: from [195.30.1.100] (helo=moebius2.Space.Net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <gert@Space.Net>)
	id 1L2jG7-0008DO-37
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 09:22:05 +0000
Received: (qmail 47942 invoked by uid 1007); 19 Nov 2008 09:22:01 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=testkey; d=space.net;
  b=fkrRtWow5bqcEy36rYv1T5pLq8a7UF9ESejzZWWMzB9IxnlnGqxnagd2MfW9SiZt  ;
Date: Wed, 19 Nov 2008 10:22:01 +0100
From: Gert Doering <gert@space.net>
To: james woodyatt <jhw@apple.com>
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ops.ietf.org>,
  Behave WG <behave@ietf.org>
Subject: Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
Message-ID: <20081119092201.GI89033@Space.Net>
References: <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com> <60FD682C-1436-493F-995D-4B2A7241D398@apple.com> <20081118220136.GE89033@Space.Net> <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1wmxjYP1x3BSmbSx"
Content-Disposition: inline
In-Reply-To: <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com>
User-Agent: Mutt/1.4.2.1i
X-NCC-RegID: de.space
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


--1wmxjYP1x3BSmbSx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Nov 18, 2008 at 06:29:54PM -0600, james woodyatt wrote:
> >OK, I bite.  What answer do you give to folks that need to renumber
> >things like site-to-site VPN endpoints, which affects lots of =20
> >configuration
> >to be changed by *other* folks (their VPN peers)?
>=20
> Please, help me understand why solving this problem requires storing =20
> IP addresses in persistent storage without a coherent caching =20
> protocol.  I'm not seeing it-- probably because I'm not sure I =20
> understand the nature and scope of the problem very well.

Uh, well, people usually configure their VPN endpoints (site-to-site,=20
not roadwarrior-to-home) with IP addresses.

> For the sake of argument, I'll accept that reasonable people currently =
=20
> perceive it to be necessary.  My hunch is that those folks should =20
> probably be using DNS-SD instead of the fragile cruftiness they're =20
> struggling against now.  Maybe if I understood the problem better, I =20
> could suggest a more detailed alternative to their current solution.

Well.  Yes.  I've spent some time after my e-mail yesterday to think about
this, and actually using DNS (plus some sort of "not completely braindead
IPSEC implementation") might just work, provided one can get old+new=20
addresses working for long enough to DNS to propagate. =20

Which is not instantaneous, as soon as it leaves the local domain.

Now *this* aspect reduces itself to "educated people that DNS is good"
and "educate firewall vendors to write useful IPSEC code".


Another thing that is regularily mentioned regarding "why renumbering is=20
hard" is access-lists (aka "firewall rules").  DNS as well?

Gert Doering
        -- NetMaster
--=20
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

--1wmxjYP1x3BSmbSx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQCVAwUBSSPauakuBuNlUUl1AQJPSAQArtHelTu3w67CHbD91Rnv0CboASmsgY2A
piHE6wmj2mHAr2Ccjj4UUftFLw4E+dKP4aYqxDbdnAhA4ZncatJLPaqT1a1RGVxe
sRR9c7prVRA7PDZwdAbjFz4AnW17YIl4thtn0eBHpq4As3VoWC4V0siydgoVKv3J
fL9DDVmulQ4=
=4EYg
-----END PGP SIGNATURE-----

--1wmxjYP1x3BSmbSx--



From owner-v6ops@ops.ietf.org  Wed Nov 19 02:09:17 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4EED3A68FC
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 02:09:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5
	tests=[AWL=0.200, BAYES_00=-2.599, 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 URJI9OE07uSZ
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 02:09:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 81CA73A67F5
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 02:09:16 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2jx2-000AvE-Pz
	for v6ops-data@psg.com; Wed, 19 Nov 2008 10:06:24 +0000
Received: from [2001:630:d0:f102:230:48ff:fe77:96e] (helo=owl.ecs.soton.ac.uk)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <tjc@ecs.soton.ac.uk>)
	id 1L2jww-000Aug-GQ
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 10:06:21 +0000
X-ECS-MailScanner-Watermark: 1227693938.5495@sjet1aTe06C5JRtjABaJuA
Received: from gander.ecs.soton.ac.uk ([IPv6:2001:630:d0:f102:21d:9ff:fe22:9fc])
	by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id mAJA5Z4q007296;
	Wed, 19 Nov 2008 10:05:37 GMT
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12])
	by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id mAJA5sgd012252
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 19 Nov 2008 10:05:54 GMT
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1])
	by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id mAJA5sC8009893;
	Wed, 19 Nov 2008 10:05:54 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id mAJA5rTX009892;
	Wed, 19 Nov 2008 10:05:53 GMT
Date: Wed, 19 Nov 2008 10:05:53 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Fred Baker <fred@cisco.com>, v6ops@ops.ietf.org, kurtis@kurtis.pp.se,
        rbonica@juniper.net
Subject: Re: Rogue RA WGLC
Message-ID: <20081119100552.GA9207@login.ecs.soton.ac.uk>
Mail-Followup-To: Pekka Savola <pekkas@netcore.fi>,
	Fred Baker <fred@cisco.com>, v6ops@ops.ietf.org,
	kurtis@kurtis.pp.se, rbonica@juniper.net
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <alpine.LRH.2.00.0811190822300.22834@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.00.0811190822300.22834@netcore.fi>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner-ID: mAJA5sgd012252
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: mAJA5Z4q007296
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Wed, Nov 19, 2008 at 08:23:54AM +0200, Pekka Savola wrote:
> On Tue, 18 Nov 2008, Fred Baker wrote:
> >This is to initiate a two week working group last call of 
> >draft-chown-v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt.
> 
> At least according to the I-D tracker, the former is not even a WG 
> document yet, so it's not clear how we could have a WG LC on it. Is 
> this an omission in I-D tracker document state or something else?

That was my mistake - I believe it was agreed to be adopted in Dublin, 
but I submitted it as a personal -02 rather than a WG -00 text.

If it helps, I can resubmit it as a WG -00, just let me know.

-- 
Tim





From owner-v6ops@ops.ietf.org  Wed Nov 19 02:45:03 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 878803A683A
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 02:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.545
X-Spam-Level: 
X-Spam-Status: No, score=-0.545 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35,
	HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1,
	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 S1gGIi0l9P5Q
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 02:45:02 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 7D2083A67B2
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 02:45:01 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2kVQ-000D4F-83
	for v6ops-data@psg.com; Wed, 19 Nov 2008 10:41:56 +0000
Received: from [195.101.245.16] (helo=p-mail2.rd.francetelecom.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <jeanfrancois.cadiou@orange-ftgroup.com>)
	id 1L2kVK-000D3s-PG
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 10:41:53 +0000
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 19 Nov 2008 11:41:48 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: draft-wbeebee-ipv6-cpe-router-03
Date: Wed, 19 Nov 2008 11:41:47 +0100
Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE07D7F58B@ftrdmel3>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-ipv6-cpe-router-03
Thread-Index: AclJqvaY5MatB68BQ8aFd5vJapCiQAAgmImw
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com>
From: <jeanfrancois.cadiou@orange-ftgroup.com>
To: <iljitsch@muada.com>,
	<v6ops@ops.ietf.org>
X-OriginalArrivalTime: 19 Nov 2008 10:41:48.0146 (UTC) FILETIME=[6C88C520:01C94A33]
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Dear all,

I am following the different mails exchanges from the beginning on the =
IPv6 CPE document but never contributed.  I would like to make a comment =
on the following proposals
---------------------------------------
" It would be good if CPEs would also insert DNS addresses in RAs as per =
RFC 5006. If requiring the support of an experimental RFC is a bridge =
too far, at the very least say this is a good idea and point to 5006."
---------------------------------------

Moreover some mail exchanges also occurs with proposal made by Tony =
Hain. See the mail below.
---------------------------------------
De : ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] De la part de =
Brian E Carpenter Envoy=E9 : lundi 17 novembre 2008 04:07 =C0 : =
alh-ietf@tndh.net Cc : john.loughney@nokia.com; 'Brian Haberman'; =
ipv6@ietf.org Objet : Re: Node Requirement: New issue 5: Support for RFC =
5006
Has anyone reported implementation experience with 5006?
If so, we could discuss reclassifying it IMHO. But perhaps we should =
separate that question from progressing the node-req update.
   Brian
On 2008-11-16 07:39, Tony Hain wrote:
> The experimental designation is just wrong. We have to break the=20
> current requirement to deploy both RA & DHCP if you want to have a =
working network.
> Each model should be able to stand on its own, and 5006 fills a hole=20
> on that side. The 'experiment' is simply there to placate those that=20
> want a DHCP-only model. Change the status of the RFC & make it a node=20
> requirement...
>=20
> Tony
---------------------------------------

I am seconding this proposal in order to support also a simpler model as =
an alternative to a local DHCPv6 server.=20
The minimum set of requirements for an end device to communicate is to =
get its IP address, DNS server address and default gateway address.=20
Assuming that some end devices could later discover its =
autoconfiguration server in the Broad Band Forum terminology, via =
initial factory provisionning or some automatic process, RFC5006 support =
is more that enough in the home gateway to reach this goal in this =
model. We could then avoid the use of a local DHCP server in the CPE for =
complex provisionning which has also the drawback of linking service =
evolutions and CPE evolutions.=20
Even if support of RFC5006 is very poor in end devices with the =
exception of latest linux distributions and apart the fact that RFC5006 =
is experimental, it is a problem of chicken and egg. If not supported in =
end devices then we do not want it in the CPE and vice et versa. =
Including it in the CPE is a way/opportunity to move forward and propose =
an alternative to the DHCP model.=20

Regards

JFC




-----Message d'origine-----
De : owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] De la =
part de Iljitsch van Beijnum
Envoy=E9 : mardi 18 novembre 2008 19:12
=C0 : v6ops Operations
Objet : draft-wbeebee-ipv6-cpe-router-03

[...]

It would be good if CPEs would also insert DNS addresses in RAs as per =
RFC 5006. If requiring the support of an experimental RFC is a bridge =
too far, at the very least say this is a good idea and point to 5006.

It would be useful to tell people to align the timers in RAs with those =
in the PD delegation for easier renumbering. Note that during =
renumbering hosts may source packets with the old addresses even though =
the new ones are already available. This shouldn't cause trouble, but in =
cases where routes or filter rules are created, multiple sets of these =
are necessary during transition from one prefix to another.

[...]



From owner-v6ops@ops.ietf.org  Wed Nov 19 04:30:29 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11F003A6872
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 04:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.272
X-Spam-Level: 
X-Spam-Status: No, score=-102.272 tagged_above=-999 required=5
	tests=[AWL=0.327, BAYES_00=-2.599, 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 q6IbnfXkwiFL
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 04:30:28 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0658E3A67B2
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 04:30:28 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2m99-000JSK-IT
	for v6ops-data@psg.com; Wed, 19 Nov 2008 12:27:03 +0000
Received: from [2001:670:86:3001::1] (helo=netcore.fi)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <pekkas@netcore.fi>)
	id 1L2m92-000JRO-UO
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 12:27:00 +0000
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id mAJCMlwb030506;
	Wed, 19 Nov 2008 14:22:47 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id mAJCMlZr030502;
	Wed, 19 Nov 2008 14:22:47 +0200
Date: Wed, 19 Nov 2008 14:22:46 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: Fred Baker <fred@cisco.com>, v6ops@ops.ietf.org, kurtis@kurtis.pp.se,
        rbonica@juniper.net
Subject: Re: Rogue RA WGLC
In-Reply-To: <20081119100552.GA9207@login.ecs.soton.ac.uk>
Message-ID: <alpine.LRH.2.00.0811191420580.30430@netcore.fi>
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <alpine.LRH.2.00.0811190822300.22834@netcore.fi> <20081119100552.GA9207@login.ecs.soton.ac.uk>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.94.1/8649/Wed Nov 19 00:31:11 2008 on otso.netcore.fi
X-Virus-Status: Clean
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Wed, 19 Nov 2008, Tim Chown wrote:
> On Wed, Nov 19, 2008 at 08:23:54AM +0200, Pekka Savola wrote:
>> On Tue, 18 Nov 2008, Fred Baker wrote:
>>> This is to initiate a two week working group last call of
>>> draft-chown-v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt.
>>
>> At least according to the I-D tracker, the former is not even a WG
>> document yet, so it's not clear how we could have a WG LC on it. Is
>> this an omission in I-D tracker document state or something else?
>
> That was my mistake - I believe it was agreed to be adopted in Dublin,
> but I submitted it as a personal -02 rather than a WG -00 text.
>
> If it helps, I can resubmit it as a WG -00, just let me know.

OK.  The secretariat can also mark non-draft-ietf-<wg> drafts as WG 
documents and then they show up properly in I-D tracker (and probably 
also on tools.ietf.org).  I know some WG chairs use this feature if 
the time between acceptance and submitting a WG -00 is long, or folks 
don't want to rename a draft.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



From owner-v6ops@ops.ietf.org  Wed Nov 19 14:46:49 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 98D753A6AC1
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 14:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.397
X-Spam-Level: 
X-Spam-Status: No, score=-0.397 tagged_above=-999 required=5 tests=[AWL=0.098,
	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 Gksx6iMGGrsN
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 14:46:48 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id BEB393A6961
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 14:46:48 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2vkL-000E0E-FD
	for v6ops-data@psg.com; Wed, 19 Nov 2008 22:42:05 +0000
Received: from [209.85.198.233] (helo=rv-out-0506.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <brian.e.carpenter@gmail.com>)
	id 1L2vkF-000Dzf-Re
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 22:42:02 +0000
Received: by rv-out-0506.google.com with SMTP id b25so149574rvf.41
        for <v6ops@ops.ietf.org>; Wed, 19 Nov 2008 14:41:58 -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=lXi2vl5l3DDyNRdt9n2tXOv/9KBTQnOTjTX+68yqb+4=;
        b=J6OjuoI6fR7j7H6rf/MLZAscusMzl4oZS4WmX4JxkxXdiy9A6quKZ5D7i/mmiTKOw5
         paoQlPMDs+X0r1u7o61MHPye8JsHrcWGr/lTWOR+cp8ltZswaj5n7a/5MwIPdR0T3j6b
         vUWkw5fFDg4vPWdwoK4elUpO5683x9FdQYlu0=
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=JqbGl6vY7nZiSKbyZNkmLlPD63iVtrqCz/cmB+VuVqnQqTkhDggk0dcsey+Sm80pfY
         H8q+agTMkRS5a1K1MsQL70nnmZ+Ja9NakOc0j7iOxP9VUSSRzd1J7G7PZawJ/S8VLq1d
         eeZyKmn7MGM1v0eu0CrvJRHqrXR54HLZpeRs8=
Received: by 10.141.105.18 with SMTP id h18mr852318rvm.109.1227134518866;
        Wed, 19 Nov 2008 14:41:58 -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 f21sm353215rvb.5.2008.11.19.14.41.57
        (version=SSLv3 cipher=RC4-MD5);
        Wed, 19 Nov 2008 14:41:58 -0800 (PST)
Message-ID: <49249633.8090602@gmail.com>
Date: Thu, 20 Nov 2008 11:41:55 +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: Pekka Savola <pekkas@netcore.fi>
CC: Antonio Querubin <tony@lava.net>, 
 Iljitsch van Beijnum <iljitsch@muada.com>,
 v6ops Operations <v6ops@ops.ietf.org>
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com> <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net> <49232E73.6030400@gmail.com> <alpine.LRH.2.00.0811190825240.22834@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0811190825240.22834@netcore.fi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Pekka,

On 2008-11-19 19:35, Pekka Savola wrote:
> On Wed, 19 Nov 2008, Brian E Carpenter wrote:
>>> How about auto-enabling 6to4 assuming it can actually reach a
>>> 192.88.99l.1 gateway?
>>
>> That doesn't guarantee connectivity; you actually need to see an
>> IPv6 reply before you know that 6to4 is working. So you really
>> need to enable 6to4, run a reachability test, and disable it if
>> no response.
> 
> Well, while this is one possible approach, and it may be the simplest
> test from a human perspective, an implementation could do a test without
> enabling 6to4.
> 
> You just need to craft a packet using a raw socket that resembles that
> kind of 6to4 packet, and watch for replies.  As an example of how
> Microsoft has done it, the implementation sends a proto-41 packet with
> IPv6 TTL=1 to an IPv6 address corresponding relay's v4 address, so the
> relay will return _something_ if connectivity at least up to the relay
> is working, the relay has v6 enabled, etc.

Sure, but it is not sure that the 6to4 path is symmetric - the
reply packets might come from a completely different relay.

   Brian

> 
> Live example from a relay:
> 
> 08:31:01.202671 IP (tos 0x0, ttl 119, id 174, offset 0, flags [none],
> proto IPv6 (41), length 68) 93.106.184.x > 192.88.99.1: IP6 (hlim 1,
> next-header ICMPv6 (58) payload length: 8) 2002:5d6a:b8xx::5d6a:b8xx >
> 2002:c058:6301::c058:6301: [icmp6 sum ok] ICMP6, echo request, length 8,
> seq 2
> 08:31:01.202752 IP (tos 0x0, ttl 40, id 32297, offset 0, flags [none],
> proto IPv6 (41), length 116) 192.88.99.1 > 93.106.184.x: IP6 (hlim 64,
> next-header ICMPv6 (58) payload length: 56) 2002:c058:6301::1741 >
> 2002:5d6a:b8xx::5d6a:b8xx: [icmp6 sum ok] ICMP6, time exceeded
> in-transit, length 56 for 2002:c058:6301::c058:6301
> 



From owner-v6ops@ops.ietf.org  Wed Nov 19 15:10:02 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C234A3A6BC7
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 15:10:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.397
X-Spam-Level: 
X-Spam-Status: No, score=-106.397 tagged_above=-999 required=5
	tests=[AWL=-1.902, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 7Y965nhV797Q
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 15:10:02 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id DD6B53A6ABC
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 15:10:01 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2w9x-000FEc-0e
	for v6ops-data@psg.com; Wed, 19 Nov 2008 23:08:33 +0000
Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L2w9r-000FEA-M1
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 23:08:29 +0000
X-IronPort-AV: E=Sophos;i="4.33,634,1220227200"; 
   d="scan'208";a="197927353"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
  by sj-iport-6.cisco.com with ESMTP; 19 Nov 2008 23:08:27 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id mAJN8RcF025622;
	Wed, 19 Nov 2008 15:08:27 -0800
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.13.8) with ESMTP id mAJN8RoN022662;
	Wed, 19 Nov 2008 23:08:27 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 19 Nov 2008 15:08:26 -0800
Received: from [130.129.79.33] ([10.21.69.253]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 19 Nov 2008 15:08:26 -0800
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, v6ops@ops.ietf.org, kurtis@kurtis.pp.se,
        rbonica@juniper.net
Message-Id: <BA2BBDAC-00FC-49B3-9178-3514193C617A@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0811191420580.30430@netcore.fi>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Rogue RA WGLC
Date: Wed, 19 Nov 2008 17:08:25 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <alpine.LRH.2.00.0811190822300.22834@netcore.fi> <20081119100552.GA9207@login.ecs.soton.ac.uk> <alpine.LRH.2.00.0811191420580.30430@netcore.fi>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 19 Nov 2008 23:08:26.0561 (UTC) FILETIME=[BA786B10:01C94A9B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=499; t=1227136107; x=1228000107;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Rogue=20RA=20WGLC
	|Sender:=20;
	bh=4ohs1XLltTM33bSWQPc7Awyj9m4kp6T3yDNNVv4i084=;
	b=b7svYCyGvMytA5EPkia8qaFS7ydl1/u5IPg5Gsxz4VZ38DIGve2tmZ5DZC
	oKit1rE+olnW1pXqcaWe205PniOkpRbxnQJOT70tdNoq7NOnpWSy+avm7Ak0
	OQG0Q/ybVv;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 19, 2008, at 6:22 AM, Pekka Savola wrote:

> OK.  The secretariat can also mark non-draft-ietf-<wg> drafts as WG  
> documents and then they show up properly in I-D tracker (and  
> probably also on tools.ietf.org).  I know some WG chairs use this  
> feature if the time between acceptance and submitting a WG -00 is  
> long, or folks don't want to rename a draft.

I have simply presumed that Ron can advance it accordingly. If he  
wants it resubmitted-or-whatever, so be it.



From owner-v6ops@ops.ietf.org  Wed Nov 19 15:12:08 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F38D3A6953
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 15:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.547
X-Spam-Level: 
X-Spam-Status: No, score=-105.547 tagged_above=-999 required=5
	tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 0JL4q0hSM-pT
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 15:12:07 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 62E7F3A6949
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 15:12:07 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2wCh-000FPB-4W
	for v6ops-data@psg.com; Wed, 19 Nov 2008 23:11:23 +0000
Received: from [17.254.13.22] (helo=mail-out3.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1L2wCb-000FOm-Kg
	for v6ops@ops.ietf.org; Wed, 19 Nov 2008 23:11:19 +0000
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48])
	by mail-out3.apple.com (Postfix) with ESMTP id 1F42D458ED3F;
	Wed, 19 Nov 2008 15:11:17 -0800 (PST)
Received: from relay11.apple.com (unknown [127.0.0.1])
	by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id 09DF728091;
	Wed, 19 Nov 2008 15:11:17 -0800 (PST)
X-AuditID: 11807130-aab18bb000000eb5-b5-49249d14bdbb
Received: from [17.151.112.174] (unknown [17.151.112.174])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay11.apple.com (Apple SCV relay) with ESMTP id B08A128085;
	Wed, 19 Nov 2008 15:11:16 -0800 (PST)
Cc: v6ops Operations <v6ops@ops.ietf.org>
Message-Id: <29A63497-21FE-40D9-8EEB-60FEBB3A906E@apple.com>
From: james woodyatt <jhw@apple.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <49249633.8090602@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: draft-wbeebee-ipv6-cpe-router-03
Date: Wed, 19 Nov 2008 17:11:15 -0600
References: <21F9CB48-B8D7-4C41-BE74-7E61258E46B5@muada.com> <Pine.BSI.4.64.0811181014220.21019@malasada.lava.net> <49232E73.6030400@gmail.com> <alpine.LRH.2.00.0811190825240.22834@netcore.fi> <49249633.8090602@gmail.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 19, 2008, at 16:41, Brian E Carpenter wrote:
>
> Sure, but it is not sure that the 6to4 path is symmetric - the
> reply packets might come from a completely different relay.

It's impossible to test all the possible reverse paths that might ever  
be used, but a test to see whether the node at the 6to4 anycast  
address is actually a router running a functioning 6to4 relay is a  
worthwhile test for a CPE router to perform.

I don't think it's strictly necessary to shut down all IPv6 routing  
just because the anycast 6to4 relay isn't responding, because you can  
still reach all the other 6to4 sites over encapsulated direct IPv4,  
but it's certainly an exception condition worthy of asynchronous  
notification to a network manager... however that's done in the  
residential CPE environment.  (Apple has a proprietary method for  
doing that, but one could imagine specifying an SNMP trap message, for  
example.)


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Wed Nov 19 16:34:21 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA7DA28C1C9
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 16:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001,
	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 Lghmzyvb76bz
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 16:34:21 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0413328C1C2
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 16:34:21 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2xRt-000JvL-K6
	for v6ops-data@psg.com; Thu, 20 Nov 2008 00:31:09 +0000
Received: from [2001:41d0:1:a0d6::401:1983] (helo=yop.chewa.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <rdenis@simphalempin.com>)
	id 1L2xRm-000Jv0-Sk
	for v6ops@ops.ietf.org; Thu, 20 Nov 2008 00:31:05 +0000
Received: from leon.remlab.net (unknown [IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id 838857C7;
	Thu, 20 Nov 2008 01:31:01 +0100 (CET)
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <rdenis@simphalempin.com>
Organization: Remlab.net
To: v6ops@ops.ietf.org,
 tjc@ecs.soton.ac.uk,
 venaas@uninett.no
Subject: Re: Rogue RA WGLC
Date: Thu, 20 Nov 2008 02:30:55 +0200
User-Agent: KMail/1.9.10
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
In-Reply-To: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811200230.55313.rdenis@simphalempin.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

	Hello,

As promised, here is my review.

I am a bit concerned that the document seems (at least in certain places) t=
o=20
focus solely on getting an incorrect default gateway. Rogue RAs cause hosts=
=20
to assume wrong prefixes for their SLAAC addresses. In case of mixing "good=
"=20
and "bad" RAs, the host might keep on using the "good" default gateway, but=
=20
pick a wrong source address. This is highly likely to break, due to ingress=
=20
filtering or lack of return routability.

Because of this, I am even more suspicious about the usefulness of the DHCP=
v6=20
solution than the authors are.

Last, please s/Courmant/Courmont/ :)

On Tuesday 18 November 2008 21:22:02 Fred Baker, you wrote:
> This is to initiate a two week working group last call of draft-chown-
> v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt. Please
> read these drafts now. If you find nits (spelling errors, minor
> suggested wording changes, etc), comment to the authors; if you find
> greater issues, such as disagreeing with a statement or finding
> additional issues that need to be addressed, please post your comments
> to the list.
>
> We are looking specifically for comments on the importance of the
> document as well as its content. If you have read the document and
> believe it to be of operational utility, that is also an important
> comment to make.



=2D-=20
R=E9mi Denis-Courmont



From owner-v6ops@ops.ietf.org  Wed Nov 19 16:59:40 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09F7F3A6BC9
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 19 Nov 2008 16:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.796
X-Spam-Level: 
X-Spam-Status: No, score=-104.796 tagged_above=-999 required=5
	tests=[AWL=-0.901, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4,
	RDNS_NONE=0.1, 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 DwUpFl4IwSYx
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 19 Nov 2008 16:59:39 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D406D3A6BE0
	for <v6ops-archive@lists.ietf.org>; Wed, 19 Nov 2008 16:59:38 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L2xrr-000LG8-FP
	for v6ops-data@psg.com; Thu, 20 Nov 2008 00:57:59 +0000
Received: from [17.254.13.23] (helo=mail-out4.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1L2xrm-000LFW-8b
	for v6ops@ops.ietf.org; Thu, 20 Nov 2008 00:57:56 +0000
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48])
	by mail-out4.apple.com (Postfix) with ESMTP id DE6554789D44;
	Wed, 19 Nov 2008 16:57:53 -0800 (PST)
Received: from relay11.apple.com (unknown [127.0.0.1])
	by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id C88E928091;
	Wed, 19 Nov 2008 16:57:53 -0800 (PST)
X-AuditID: 11807130-ad31dbb000000eb5-9a-4924b6114a51
Received: from [17.151.107.177] (unknown [17.151.107.177])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay11.apple.com (Apple SCV relay) with ESMTP id 65E522808A;
	Wed, 19 Nov 2008 16:57:53 -0800 (PST)
Cc: IPv6 Operations <v6ops@ops.ietf.org>,
 Behave WG <behave@ietf.org>
Message-Id: <5E35A200-5C5A-42D8-B02F-31D92649F0C6@apple.com>
From: james woodyatt <jhw@apple.com>
To: Gert Doering <gert@space.net>
In-Reply-To: <20081119092201.GI89033@Space.Net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: The renumbering problem [Re: [BEHAVE] Comments on the NAT66 draft]
Date: Wed, 19 Nov 2008 18:57:52 -0600
References: <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com> <60FD682C-1436-493F-995D-4B2A7241D398@apple.com> <20081118220136.GE89033@Space.Net> <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com> <20081119092201.GI89033@Space.Net>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 19, 2008, at 03:22, Gert Doering wrote:
> On Tue, Nov 18, 2008 at 06:29:54PM -0600, james woodyatt wrote:
>>
>>
>> Please, help me understand why solving this problem requires  
>> storing IP addresses in persistent storage without a coherent  
>> caching protocol.  I'm not seeing it-- probably because I'm not  
>> sure I understand the nature and scope of the problem very well.
>
> Uh, well, people usually configure their VPN endpoints (site-to-site,
> not roadwarrior-to-home) with IP addresses.

Ah.  I've given this more thought now, and I'm going to assume that  
we're talking about L3 VPN's and not L2VPN's (but I'm not sure that's  
warranted here).

>> For the sake of argument, I'll accept that reasonable people  
>> currently
>> perceive it to be necessary.  My hunch is that those folks should
>> probably be using DNS-SD instead of the fragile cruftiness they're
>> struggling against now.  Maybe if I understood the problem better, I
>> could suggest a more detailed alternative to their current solution.
>
> Well.  Yes.  I've spent some time after my e-mail yesterday to think  
> about
> this, and actually using DNS (plus some sort of "not completely  
> braindead
> IPSEC implementation") might just work, provided one can get old+new
> addresses working for long enough to DNS to propagate.
>
> Which is not instantaneous, as soon as it leaves the local domain.
>
> Now *this* aspect reduces itself to "educated people that DNS is good"
> and "educate firewall vendors to write useful IPSEC code".

Now that I've had a chance to think about this more carefully, I'm  
reminded of the old, old days when I used to work in an enterprise  
that managed its routing table by copying static routes around with / 
usr/bin/rcp.  This eventually became painful enough that some bright  
soul noticed that networked computers can executed distributed route- 
computation algorithms, e.g. Bellman-Ford, link-state, etc.

I suspect that large enterprise sites with massive collections of  
static VPN tunnel configurations, which need their tunnel endpoint  
addresses renumbered when adding or dropping a PA allocation, would do  
well to think about how such distributed algorithms could be used to  
ease the pain of renumbering.

I would imagine that enterprises with this problem would have an  
incentive to develop a standard protocol for automatically managing  
the routes for complicated VPN topologies.  (I'll even go so far to  
say that something like BGP might be easily adapted to serve in this  
capacity, but I'm not sure.)  I do feel pretty certain about this  
point: before we set about systematically dismantling the utility of  
the provider aggregated addressing architecture in IPv6 as it relates  
to our problems maintaining the scalability of the default-free zone,  
I'd like to see an explanation for why enterprises view automating VPN  
tunnel management as a non-viable alternative solution.

> Another thing that is regularily mentioned regarding "why  
> renumbering is
> hard" is access-lists (aka "firewall rules").  DNS as well?

Sigh.  It's probably a good idea for large sites to use network  
operations and management systems that recognize the distinction  
between the network prefix and the host identifier parts of IPv6  
address.

I recognize that not all IPv6 addresses have such a distinction, but  
enterprises worried about this could conceivably choose IPv6  
deployments where the distinction is significant-- because they can  
use [or build] tools that easily allow access-lists to be composed  
automagickally by combining the host identifiers (don't need  
renumbering) with network identifiers (do need renumbering) without  
requiring a human person to have to sweat all that tedious arithmetic  
and typing.

I anticipate a rebuttal to my arguments above along the lines of this:  
"That's nice, James... but those routing protocols and network  
management tools don't exist today, and we need them!"  My response is  
quite simple: "True, but those are problems worth solving, and I don't  
see how it's a good idea to *avoid* the work of solving them at the  
cost of A) introducing NAT66 into the Internet architecture and/or B)  
exploding the routing tables in the default-free zone."

I could be wrong about that, but I remain unconvinced.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Thu Nov 20 08:21:26 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B71A28C169
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 20 Nov 2008 08:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.447
X-Spam-Level: 
X-Spam-Status: No, score=-105.447 tagged_above=-999 required=5
	tests=[AWL=-1.252, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4,
	RDNS_NONE=0.1, 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 jngV8qkQE5vF
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 20 Nov 2008 08:21:25 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 4FAAF28C111
	for <v6ops-archive@lists.ietf.org>; Thu, 20 Nov 2008 08:21:25 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3CB8-000DEj-98
	for v6ops-data@psg.com; Thu, 20 Nov 2008 16:14:50 +0000
Received: from [171.71.176.71] (helo=sj-iport-2.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L3CB3-000DE2-7s
	for v6ops@ops.ietf.org; Thu, 20 Nov 2008 16:14:47 +0000
X-IronPort-AV: E=Sophos;i="4.33,639,1220227200"; 
   d="scan'208";a="107273121"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
  by sj-iport-2.cisco.com with ESMTP; 20 Nov 2008 16:14:44 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id mAKGEh5F030832;
	Thu, 20 Nov 2008 08:14:43 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mAKGEhK9015194;
	Thu, 20 Nov 2008 16:14:43 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 20 Nov 2008 08:14:43 -0800
Received: from [130.129.95.58] ([10.21.69.168]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 20 Nov 2008 08:14:42 -0800
Cc: v6ops@ops.ietf.org, tjc@ecs.soton.ac.uk, venaas@uninett.no
Message-Id: <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com>
From: Fred Baker <fred@cisco.com>
To: =?ISO-8859-1?Q?=22R=E9mi_Denis-Courmont=22?= <rdenis@simphalempin.com>
In-Reply-To: <200811200230.55313.rdenis@simphalempin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Rogue RA WGLC
Date: Thu, 20 Nov 2008 10:14:41 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Nov 2008 16:14:43.0026 (UTC) FILETIME=[18E75320:01C94B2B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1701; t=1227197683; x=1228061683;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Rogue=20RA=20WGLC
	|Sender:=20;
	bh=R3h5R5QtaY5gU09cHETLKD09ZRfamKvZN5YSc7p0xFo=;
	b=HJ7U5ASzfoWWk67ENoePV+QcmeUIe/YbaSvfKRwYPdsfIsXBrMG7/j6nKG
	PBqCI+9HfxbPsYGLT4DOSNJsBp6jkE+zoMiQnxYCIGCqSyNxAHaMX+e7Og6d
	c/uKU2/bzn;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

So I understand your comment as less than supportive of the document. =20=

In what ways do you believe it needs to change?

On Nov 19, 2008, at 6:30 PM, R=E9mi Denis-Courmont wrote:

> 	Hello,
>
> As promised, here is my review.
>
> I am a bit concerned that the document seems (at least in certain =20
> places) to
> focus solely on getting an incorrect default gateway. Rogue RAs =20
> cause hosts
> to assume wrong prefixes for their SLAAC addresses. In case of =20
> mixing "good"
> and "bad" RAs, the host might keep on using the "good" default =20
> gateway, but
> pick a wrong source address. This is highly likely to break, due to =20=

> ingress
> filtering or lack of return routability.
>
> Because of this, I am even more suspicious about the usefulness of =20
> the DHCPv6
> solution than the authors are.
>
> Last, please s/Courmant/Courmont/ :)
>
> On Tuesday 18 November 2008 21:22:02 Fred Baker, you wrote:
>> This is to initiate a two week working group last call of draft-=20
>> chown-
>> v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt. Please
>> read these drafts now. If you find nits (spelling errors, minor
>> suggested wording changes, etc), comment to the authors; if you find
>> greater issues, such as disagreeing with a statement or finding
>> additional issues that need to be addressed, please post your =20
>> comments
>> to the list.
>>
>> We are looking specifically for comments on the importance of the
>> document as well as its content. If you have read the document and
>> believe it to be of operational utility, that is also an important
>> comment to make.
>
>
>
> --=20
> R=E9mi Denis-Courmont
>




From owner-v6ops@ops.ietf.org  Thu Nov 20 08:42:21 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4DF028C21B
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 20 Nov 2008 08:42:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001,
	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 al-n50wtJ9+o
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 20 Nov 2008 08:42:21 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1304328C223
	for <v6ops-archive@lists.ietf.org>; Thu, 20 Nov 2008 08:42:21 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3Ca0-000EhI-Db
	for v6ops-data@psg.com; Thu, 20 Nov 2008 16:40:32 +0000
Received: from [2001:41d0:1:a0d6::401:1983] (helo=yop.chewa.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <rdenis@simphalempin.com>)
	id 1L3CZu-000Eh3-Ou
	for v6ops@ops.ietf.org; Thu, 20 Nov 2008 16:40:29 +0000
Received: from leon.remlab.net (unknown [IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id 600C1E99;
	Thu, 20 Nov 2008 17:40:25 +0100 (CET)
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <rdenis@simphalempin.com>
Organization: Remlab.net
To: Fred Baker <fred@cisco.com>
Subject: Re: Rogue RA WGLC
Date: Thu, 20 Nov 2008 18:40:18 +0200
User-Agent: KMail/1.9.10
Cc: v6ops@ops.ietf.org,
 tjc@ecs.soton.ac.uk,
 venaas@uninett.no
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com>
In-Reply-To: <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811201840.18440.rdenis@simphalempin.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Thursday 20 November 2008 18:14:41 Fred Baker, you wrote:
> So I understand your comment as less than supportive of the document.
> In what ways do you believe it needs to change?

I am just dubious about the DHCPv6 solution. I think it needs to be better=
=20
studied, so that we understand what (if anything) it would solve.

=2D-=20
R=E9mi Denis-Courmont



From owner-v6ops@ops.ietf.org  Thu Nov 20 15:28:26 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47E583A6A56
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 20 Nov 2008 15:28:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.331
X-Spam-Level: 
X-Spam-Status: No, score=-105.331 tagged_above=-999 required=5
	tests=[AWL=-1.136, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4,
	RDNS_NONE=0.1, 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 gUWdloMRDtRX
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 20 Nov 2008 15:28:25 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 5F7FB3A6907
	for <v6ops-archive@lists.ietf.org>; Thu, 20 Nov 2008 15:28:25 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3Ir7-000DMr-48
	for v6ops-data@psg.com; Thu, 20 Nov 2008 23:22:37 +0000
Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L3Ir1-000DMV-VG
	for v6ops@ops.ietf.org; Thu, 20 Nov 2008 23:22:33 +0000
X-IronPort-AV: E=Sophos;i="4.33,639,1220227200"; 
   d="scan'208";a="198668262"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
  by sj-iport-6.cisco.com with ESMTP; 20 Nov 2008 23:22:28 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAKNMS7D005791;
	Thu, 20 Nov 2008 15:22:28 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mAKNMSmm018087;
	Thu, 20 Nov 2008 23:22:28 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 20 Nov 2008 15:22:28 -0800
Received: from [130.129.79.33] ([10.21.113.157]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 20 Nov 2008 15:22:27 -0800
Cc: v6ops@ops.ietf.org, tjc@ecs.soton.ac.uk, venaas@uninett.no
Message-Id: <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com>
From: Fred Baker <fred@cisco.com>
To: =?ISO-8859-1?Q?=22R=E9mi_Denis-Courmont=22?= <rdenis@simphalempin.com>
In-Reply-To: <200811201840.18440.rdenis@simphalempin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Rogue RA WGLC
Date: Thu, 20 Nov 2008 17:22:24 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com> <200811201840.18440.rdenis@simphalempin.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Nov 2008 23:22:28.0106 (UTC) FILETIME=[DA7BBEA0:01C94B66]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1156; t=1227223348; x=1228087348;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Rogue=20RA=20WGLC
	|Sender:=20;
	bh=YJYXjV3TZaqKqzBYElg/xbeFFQF9I9tbkkCWz6n+fjM=;
	b=Yj2xGYEY0r+eb/Is31rbGNwj3lwStWPE34lGLGl49hbKodXhTebCvJwi8e
	Oj4FmacyviGI0TzEsPxqpIDOD2JHieBNbVGgWBc7GfPqsXMPd7O+jbot7kOd
	bp/FkCSb+/u452gH8iBGc2oeMQ14RkihrQ9XU5N7geYhFi5GDVY7Q=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 20, 2008, at 10:40 AM, R=E9mi Denis-Courmont wrote:

> On Thursday 20 November 2008 18:14:41 Fred Baker, you wrote:
>> So I understand your comment as less than supportive of the =20
>> document. In what ways do you believe it needs to change?
>
> I am just dubious about the DHCPv6 solution. I think it needs to be =20=

> better studied, so that we understand what (if anything) it would =20
> solve.

I think operational folks can tell you pretty quickly what it solves. =20=

It enables an operator to specify an address for an end system as =20
opposed to letting the end system dream one up. There are a set of =20
people who think that is important. In this context, it also allows =20
them to specify to a host what default gateway to choose with a view =20
to not choosing others.

If the argument is "I just think people should be using =20
autoconfiguration", I have no problem with autoconfiguration, but I =20
know network managers that do. "I don't like it" is no where near as =20
useful a comment as "I have identified a problem".

Given that context, what do you believe needs to change in the document?=



From owner-v6ops@ops.ietf.org  Thu Nov 20 16:14:54 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3881B3A6935
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 20 Nov 2008 16:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001,
	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 Rzp3wWJRfj2J
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 20 Nov 2008 16:14:53 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 655083A67F0
	for <v6ops-archive@lists.ietf.org>; Thu, 20 Nov 2008 16:14:53 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3Jdz-000GmB-Di
	for v6ops-data@psg.com; Fri, 21 Nov 2008 00:13:07 +0000
Received: from [2001:41d0:1:a0d6::401:1983] (helo=yop.chewa.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <rdenis@simphalempin.com>)
	id 1L3Jdk-000Gkt-96
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 00:12:56 +0000
Received: from leon.remlab.net (unknown [IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id CAEA06B8;
	Fri, 21 Nov 2008 01:12:49 +0100 (CET)
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <rdenis@simphalempin.com>
Organization: Remlab.net
To: Fred Baker <fred@cisco.com>
Subject: Re: Rogue RA WGLC
Date: Fri, 21 Nov 2008 02:12:42 +0200
User-Agent: KMail/1.9.10
Cc: v6ops@ops.ietf.org,
 tjc@ecs.soton.ac.uk,
 venaas@uninett.no
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com>
In-Reply-To: <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811210212.42857.rdenis@simphalempin.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Friday 21 November 2008 01:22:24 Fred Baker, you wrote:
> > I am just dubious about the DHCPv6 solution. I think it needs to be
> > better studied, so that we understand what (if anything) it would
> > solve.
>
> I think operational folks can tell you pretty quickly what it solves.
> It enables an operator to specify an address for an end system as
> opposed to letting the end system dream one up. There are a set of
> people who think that is important.

That I understand, and I don't question.

*But*, in the face of a rogue RA specifying autoconfiguration, SLAAC is=20
re-enabled, regardless of the legitimate RA and DHCPv6 processing. If I'm=20
mistaken and the DHCPv6 solution work, then the document should clearly say=
=20
so. If, as I suspect, it does not solve the problem, then that should also =
be=20
stated.

> Given that context, what do you believe needs to change in the document?

I am not very happy with "[DHCPv6] ramifications remain unclear, and such a=
=20
fundamental change to the IPv6 model of autoconfiguration would need very=20
careful consideration."

But if everybody else thinks that's fine, then I will simply shut up.

=2D-=20
R=E9mi Denis-Courmont



From owner-v6ops@ops.ietf.org  Thu Nov 20 17:23:06 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E580E3A689E
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 20 Nov 2008 17:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.277
X-Spam-Level: 
X-Spam-Status: No, score=-105.277 tagged_above=-999 required=5
	tests=[AWL=-0.782, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 RDCfZSXpNAb8
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 20 Nov 2008 17:23:06 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id CADDE3A68EC
	for <v6ops-archive@lists.ietf.org>; Thu, 20 Nov 2008 17:23:05 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3KgK-000KTm-EL
	for v6ops-data@psg.com; Fri, 21 Nov 2008 01:19:36 +0000
Received: from [17.254.13.22] (helo=mail-out3.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1L3KgE-000KTC-92
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 01:19:32 +0000
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out3.apple.com (Postfix) with ESMTP id 011A645BC048
	for <v6ops@ops.ietf.org>; Thu, 20 Nov 2008 17:19:29 -0800 (PST)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Brightmail Gateway) with ESMTP id DE52C464002
	for <v6ops@ops.ietf.org>; Thu, 20 Nov 2008 17:19:28 -0800 (PST)
X-AuditID: 11807135-a8b7fbb000000d45-71-49260ca00669
Received: from [17.151.78.6] (unknown [17.151.78.6])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay12.apple.com (Apple SCV relay) with ESMTP id A2A0F420002
	for <v6ops@ops.ietf.org>; Thu, 20 Nov 2008 17:19:28 -0800 (PST)
Message-Id: <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com>
From: james woodyatt <jhw@apple.com>
To: IPv6 Operations <v6ops@ops.ietf.org>
In-Reply-To: <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: DHCP6 and RA,M=1,PIO,A=0
Date: Thu, 20 Nov 2008 19:19:27 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 20, 2008, at 17:22, Fred Baker wrote:
> On Nov 20, 2008, at 10:40 AM, R=E9mi Denis-Courmont wrote:
>> On Thursday 20 November 2008 18:14:41 Fred Baker, you wrote:
>>>
>>> So I understand your comment as less than supportive of the =20
>>> document. In what ways do you believe it needs to change?
>>
>> I am just dubious about the DHCPv6 solution. I think it needs to be =20=

>> better studied, so that we understand what (if anything) it would =20
>> solve.
>
> I think operational folks can tell you pretty quickly what it =20
> solves. It enables an operator to specify an address for an end =20
> system as opposed to letting the end system dream one up.

Strictly speaking, it enables an operator to translate the MAC address =20=

of an endpoint interface into its assigned IPv6 interface address.  =20
It's ICMPv6 RA that specifies that an endpoint interface isn't allowed =20=

to dream up its own address.  I mention this distinction because it's =20=

important to the point I make below.

> If the argument is "I just think people should be using =20
> autoconfiguration", I have no problem with autoconfiguration, but I =20=

> know network managers that do. "I don't like it" is no where near as =20=

> useful a comment as "I have identified a problem".

Network managers who think it's important to be able to control the =20
assignment of IPv6 interface addresses to physical interfaces often =20
make the mistake of assuming that MAC addresses are fixed on hardware =20=

manufacturing lines and cannot be changed in user software.

I'm here to say that's a painfully stupid mistake.

Whatever could possibly be the point of disabling address self-=20
assignment on a subnet when the network management system cannot be =20
certain either A) that the device presenting a specific MAC address to =20=

the network is the same device that presented it last time, or B) that =20=

the device presenting you a particular MAC address this time will ever =20=

present that MAC address to you again in the future?

If you deploy a network management system that insist on pairing a MAC =20=

address with a specific managed entity [especially, a *billable* =20
entity], then you will be forcing people like me to make MAC address =20
cloning even easier to do than it already is... (and don't think I'm =20
at a loss for ideas about how to do that).

Is encouraging MAC address cloning what we are trying to do here?  =20
Because I have a hard time believing it.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Fri Nov 21 07:08:19 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CAC9A3A68D3
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri, 21 Nov 2008 07:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.41
X-Spam-Level: 
X-Spam-Status: No, score=-105.41 tagged_above=-999 required=5
	tests=[AWL=-0.915, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 5HZsrwG-2Ub9
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri, 21 Nov 2008 07:08:19 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D12943A67E2
	for <v6ops-archive@lists.ietf.org>; Fri, 21 Nov 2008 07:08:18 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3XaL-000C14-PG
	for v6ops-data@psg.com; Fri, 21 Nov 2008 15:06:17 +0000
Received: from [171.68.10.86] (helo=sj-iport-4.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L3Xa9-000C0Z-DG
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 15:06:11 +0000
X-IronPort-AV: E=Sophos;i="4.33,644,1220227200"; 
   d="scan'208";a="25212572"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
  by sj-iport-4.cisco.com with ESMTP; 21 Nov 2008 15:06:02 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id mALF62iT015638;
	Fri, 21 Nov 2008 07:06:02 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mALF62pE015172;
	Fri, 21 Nov 2008 15:06:02 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 21 Nov 2008 07:06:01 -0800
Received: from [130.129.79.33] ([10.21.147.211]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 21 Nov 2008 07:06:01 -0800
Cc: IPv6 Operations <v6ops@ops.ietf.org>
Message-Id: <5A497F3C-8C97-4632-87E3-6DE832774FCE@cisco.com>
From: Fred Baker <fred@cisco.com>
To: james woodyatt <jhw@apple.com>
In-Reply-To: <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: DHCP6 and RA,M=1,PIO,A=0
Date: Fri, 21 Nov 2008 09:05:59 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com> <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 21 Nov 2008 15:06:01.0717 (UTC) FILETIME=[AAD33A50:01C94BEA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=959; t=1227279962; x=1228143962;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20DHCP6=20and=20RA,M=3D1,PIO,A=3D0
	|Sender:=20;
	bh=QRepC2Jg9KWas6SZm1scb6kIbDmNwDFdnHZCwyrh6Uo=;
	b=iXhki1hHTAdhxLYLMCUYsPKrATT2j/vQxvN2giwLQ1dMhiQLPJwuiS5BXc
	HjdFnHF8gECTxRt9lbaYNuXwd5o3ikhhJd6eyFit1tqkoHAjORwAnl8Jfw63
	kIq2Ea7zEL;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>


On Nov 20, 2008, at 7:19 PM, james woodyatt wrote:

> Network managers who think it's important to be able to control the  
> assignment of IPv6 interface addresses to physical interfaces often  
> make the mistake of assuming that MAC addresses are fixed on  
> hardware manufacturing lines and cannot be changed in user software.
>
> I'm here to say that's a painfully stupid mistake.

Well...

So I use a Mac at work. When NAC first came out, my network managers  
asked me to change my MAC address to one they had chosen to identify  
the device as a Mac. That wasn't too hard on Jaguar or Tiger,  
whichever it was, for the fixed interface; for the wireless interface,  
it was impossible. And btw, on the fixed interface it would  
occasionally revert to the hardware address even though it had been  
changed in the configuration files.

I would be careful about painting people as stupid. There is a lot of  
paint in that can.



From owner-v6ops@ops.ietf.org  Fri Nov 21 07:08:27 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 721383A69F5
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri, 21 Nov 2008 07:08:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.203
X-Spam-Level: 
X-Spam-Status: No, score=-105.203 tagged_above=-999 required=5
	tests=[AWL=-1.008, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4,
	RDNS_NONE=0.1, 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 srQl2odLqMiM
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri, 21 Nov 2008 07:08:26 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 7B6663A67E2
	for <v6ops-archive@lists.ietf.org>; Fri, 21 Nov 2008 07:08:26 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3XWS-000BrX-VQ
	for v6ops-data@psg.com; Fri, 21 Nov 2008 15:02:16 +0000
Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <fred@cisco.com>)
	id 1L3XWN-000Br8-8G
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 15:02:13 +0000
X-IronPort-AV: E=Sophos;i="4.33,644,1220227200"; 
   d="scan'208";a="199094991"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
  by sj-iport-6.cisco.com with ESMTP; 21 Nov 2008 15:02:10 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mALF2AaJ020376;
	Fri, 21 Nov 2008 07:02:10 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mALF2Al9000011;
	Fri, 21 Nov 2008 15:02:10 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 21 Nov 2008 07:02:10 -0800
Received: from [130.129.79.33] ([10.21.147.211]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 21 Nov 2008 07:02:09 -0800
Cc: v6ops@ops.ietf.org, tjc@ecs.soton.ac.uk, venaas@uninett.no
Message-Id: <031D027E-E346-48C7-83FF-039B51FE0F74@cisco.com>
From: Fred Baker <fred@cisco.com>
To: =?ISO-8859-1?Q?=22R=E9mi_Denis-Courmont=22?= <rdenis@simphalempin.com>
In-Reply-To: <200811210212.42857.rdenis@simphalempin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Rogue RA WGLC
Date: Fri, 21 Nov 2008 09:02:08 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com> <200811210212.42857.rdenis@simphalempin.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 21 Nov 2008 15:02:10.0308 (UTC) FILETIME=[20E50440:01C94BEA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1419; t=1227279730; x=1228143730;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Rogue=20RA=20WGLC
	|Sender:=20;
	bh=I/a6fPckEPEaB74uvQtfkeBWqWCXFr0q03HV0byxOwc=;
	b=oWNsgiSoJub3f8pmEKTWFl4HPcbI6vK8QHuQUsuyHW91OvaGNDYBoaXgDH
	nw4tlfIMudcFAc5BWrfWUTe5wsNsbfnQkEQutxVedjINXMPRTpDH+ICITew9
	le2MjskoVDUWJAT0fHUvamlys/yOTjutDFXMCnf3YGiNzsVYQHvvk=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

OK, thanks. Those are two comments that Tim and Stig can clean up.

On Nov 20, 2008, at 6:12 PM, R=E9mi Denis-Courmont wrote:

> On Friday 21 November 2008 01:22:24 Fred Baker, you wrote:
>>> I am just dubious about the DHCPv6 solution. I think it needs to be
>>> better studied, so that we understand what (if anything) it would
>>> solve.
>>
>> I think operational folks can tell you pretty quickly what it solves.
>> It enables an operator to specify an address for an end system as
>> opposed to letting the end system dream one up. There are a set of
>> people who think that is important.
>
> That I understand, and I don't question.
>
> *But*, in the face of a rogue RA specifying autoconfiguration, SLAAC =20=

> is
> re-enabled, regardless of the legitimate RA and DHCPv6 processing. =20
> If I'm
> mistaken and the DHCPv6 solution work, then the document should =20
> clearly say
> so. If, as I suspect, it does not solve the problem, then that =20
> should also be
> stated.
>
>> Given that context, what do you believe needs to change in the =20
>> document?
>
> I am not very happy with "[DHCPv6] ramifications remain unclear, and =20=

> such a
> fundamental change to the IPv6 model of autoconfiguration would need =20=

> very
> careful consideration."
>
> But if everybody else thinks that's fine, then I will simply shut up.
>
> --=20
> R=E9mi Denis-Courmont




From owner-v6ops@ops.ietf.org  Fri Nov 21 08:26:21 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0037B3A68AC
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri, 21 Nov 2008 08:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.317
X-Spam-Level: 
X-Spam-Status: No, score=-105.317 tagged_above=-999 required=5
	tests=[AWL=-0.822, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1,
	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 6T4-boBmYs0a
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri, 21 Nov 2008 08:26:20 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2B8763A6851
	for <v6ops-archive@lists.ietf.org>; Fri, 21 Nov 2008 08:26:20 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3YlY-000FwX-FB
	for v6ops-data@psg.com; Fri, 21 Nov 2008 16:21:56 +0000
Received: from [17.254.13.22] (helo=mail-out3.apple.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jhw@apple.com>)
	id 1L3YlR-000Fvz-WC
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 16:21:53 +0000
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48])
	by mail-out3.apple.com (Postfix) with ESMTP id 732A445D24BF
	for <v6ops@ops.ietf.org>; Fri, 21 Nov 2008 08:21:49 -0800 (PST)
Received: from relay11.apple.com (unknown [127.0.0.1])
	by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id 599E428084
	for <v6ops@ops.ietf.org>; Fri, 21 Nov 2008 08:21:49 -0800 (PST)
X-AuditID: 11807130-a630fbb000000eb5-1b-4926e01dcd18
Received: from [17.151.111.81] (unknown [17.151.111.81])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay11.apple.com (Apple SCV relay) with ESMTP id 2439628087
	for <v6ops@ops.ietf.org>; Fri, 21 Nov 2008 08:21:49 -0800 (PST)
Message-Id: <16D25B0A-F762-496D-B538-A18C6CC2BAAB@apple.com>
From: james woodyatt <jhw@apple.com>
To: IPv6 Operations <v6ops@ops.ietf.org>
In-Reply-To: <5A497F3C-8C97-4632-87E3-6DE832774FCE@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: DHCP6 and RA,M=1,PIO,A=0
Date: Fri, 21 Nov 2008 10:21:46 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com> <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com> <5A497F3C-8C97-4632-87E3-6DE832774FCE@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Nov 21, 2008, at 09:05, Fred Baker wrote:
>
> I would be careful about painting people as stupid. There is a lot  
> of paint in that can.

Point taken.  I'd like to take it back and use "shortsighted"  
instead.  I'd like to leave the qualifying word "painfully" in place,  
however...


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering





From owner-v6ops@ops.ietf.org  Fri Nov 21 12:16:16 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C9263A6814
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri, 21 Nov 2008 12:16:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.681
X-Spam-Level: 
X-Spam-Status: No, score=-4.681 tagged_above=-999 required=5
	tests=[AWL=-0.186, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 9P+vL0ke4eHu
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri, 21 Nov 2008 12:16:15 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 8285C3A688B
	for <v6ops-archive@lists.ietf.org>; Fri, 21 Nov 2008 12:16:15 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3cLH-000PnZ-1Q
	for v6ops-data@psg.com; Fri, 21 Nov 2008 20:11:03 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <rdroms@cisco.com>)
	id 1L3cLB-000Pn5-S4
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 20:11:00 +0000
X-IronPort-AV: E=Sophos;i="4.33,645,1220227200"; 
   d="scan'208";a="28691699"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
  by rtp-iport-1.cisco.com with ESMTP; 21 Nov 2008 20:10:39 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mALKAdLf014309;
	Fri, 21 Nov 2008 15:10:39 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mALKAdqC006054;
	Fri, 21 Nov 2008 20:10:39 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 21 Nov 2008 15:10:39 -0500
Received: from [10.1.128.151] ([10.86.243.191]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 21 Nov 2008 15:10:38 -0500
Cc: Ralph Droms <rdroms@cisco.com>, IPv6 Operations <v6ops@ops.ietf.org>
Message-Id: <2AEE9769-0EA0-4B87-9565-CD6FCC010E1E@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: james woodyatt <jhw@apple.com>
In-Reply-To: <16D25B0A-F762-496D-B538-A18C6CC2BAAB@apple.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: DHCP6 and RA,M=1,PIO,A=0
Date: Fri, 21 Nov 2008 15:10:36 -0500
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com> <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com> <5A497F3C-8C97-4632-87E3-6DE832774FCE@cisco.com> <16D25B0A-F762-496D-B538-A18C6CC2BAAB@apple.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 21 Nov 2008 20:10:38.0980 (UTC) FILETIME=[38EC3C40:01C94C15]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=692; t=1227298239; x=1228162239;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20DHCP6=20and=20RA,M=3D1,PIO,A=3D0
	|Sender:=20
	|To:=20james=20woodyatt=20<jhw@apple.com>;
	bh=+uZHRBDauqstff8YJkNEye5XBxP9o+PoR0qXyUuL9pY=;
	b=V/ZEox6VN8U4xI3rwASOssytu1oxOkJhCTsUIkaw6ZnNs45Wv9rZ+nDnA0
	PZ3moM/mB3TRFY8K50WngQ24c1bYhJpu+5CkA7Yp5LlblOpNdi5IPEnQYVaf
	HE769F5rZq;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Wonder if anyone else notices the irony of these adjectives coming  
from a company that refuses to deploy any DHCPv6 service with its  
products?

- Ralph, who takes a size 40R asbestos suit...

On Nov 21, 2008, at Nov 21, 2008,11:21 AM, james woodyatt wrote:

> On Nov 21, 2008, at 09:05, Fred Baker wrote:
>>
>> I would be careful about painting people as stupid. There is a lot  
>> of paint in that can.
>
> Point taken.  I'd like to take it back and use "shortsighted"  
> instead.  I'd like to leave the qualifying word "painfully" in  
> place, however...
>
>
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>
>
>




From owner-v6ops@ops.ietf.org  Fri Nov 21 13:53:13 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 682053A6977
	for <ietfarch-v6ops-archive@core3.amsl.com>; Fri, 21 Nov 2008 13:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5
	tests=[AWL=-1.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 ICZznK+z-p1z
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Fri, 21 Nov 2008 13:53:12 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 762033A68DC
	for <v6ops-archive@lists.ietf.org>; Fri, 21 Nov 2008 13:53:12 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L3dtF-0004nm-Ly
	for v6ops-data@psg.com; Fri, 21 Nov 2008 21:50:13 +0000
Received: from [130.76.64.48] (helo=slb-smtpout-01.boeing.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <Fred.L.Templin@boeing.com>)
	id 1L3dtB-0004nX-KO
	for v6ops@ops.ietf.org; Fri, 21 Nov 2008 21:50:11 +0000
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id mALLnuud005186
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Fri, 21 Nov 2008 13:49:56 -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 mALLntMm019491;
	Fri, 21 Nov 2008 15:49:55 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id mALLnk8v019220;
	Fri, 21 Nov 2008 15:49:55 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Fri, 21 Nov 2008 13:49:50 -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
Subject: RE: DHCP6 and RA,M=1,PIO,A=0
Date: Fri, 21 Nov 2008 13:49:50 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1053EF936@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <2AEE9769-0EA0-4B87-9565-CD6FCC010E1E@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DHCP6 and RA,M=1,PIO,A=0
Thread-Index: AclMF4dYWExRVTZeTx+w5tF66m4/wgAC0owg
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811200230.55313.rdenis@simphalempin.com> <58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com> <200811201840.18440.rdenis@simphalempin.com> <7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com> <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com> <5A497F3C-8C97-4632-87E3-6DE832774FCE@cisco.com> <16D25B0A-F762-496D-B538-A18C6CC2BAAB@apple.com> <2AEE9769-0EA0-4B87-9565-CD6FCC010E1E@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Ralph Droms" <rdroms@cisco.com>, "james woodyatt" <jhw@apple.com>
Cc: "IPv6 Operations" <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 21 Nov 2008 21:49:50.0673 (UTC) FILETIME=[14688410:01C94C23]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-5.500.1027-16292.001
X-TM-AS-Result: No--29.956900-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

DHCPv6 would indeed be very nice.

Fred
fred.l.templin@boeing.com

>-----Original Message-----
>From: Ralph Droms [mailto:rdroms@cisco.com]
>Sent: Friday, November 21, 2008 12:11 PM
>To: james woodyatt
>Cc: Ralph Droms; IPv6 Operations
>Subject: Re: DHCP6 and RA,M=3D1,PIO,A=3D0
>
>Wonder if anyone else notices the irony of these adjectives coming
>from a company that refuses to deploy any DHCPv6 service with its
>products?
>
>- Ralph, who takes a size 40R asbestos suit...
>
>On Nov 21, 2008, at Nov 21, 2008,11:21 AM, james woodyatt wrote:
>
>> On Nov 21, 2008, at 09:05, Fred Baker wrote:
>>>
>>> I would be careful about painting people as stupid. There is a lot
>>> of paint in that can.
>>
>> Point taken.  I'd like to take it back and use "shortsighted"
>> instead.  I'd like to leave the qualifying word "painfully" in
>> place, however...
>>
>>
>> --
>> james woodyatt <jhw@apple.com>
>> member of technical staff, communications engineering
>>
>>
>>
>




From owner-v6ops@ops.ietf.org  Sat Nov 22 15:39:44 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CE583A6814
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat, 22 Nov 2008 15:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.677
X-Spam-Level: 
X-Spam-Status: No, score=-0.677 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_AU=0.377,
	RCVD_IN_DNSWL_LOW=-1, RDNS_NONE=0.1, RELAY_IS_203=0.994]
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 4eRj0hgj9uvM
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat, 22 Nov 2008 15:39:43 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 23D223A6807
	for <v6ops-archive@lists.ietf.org>; Sat, 22 Nov 2008 15:39:43 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L41y7-0000qO-0r
	for v6ops-data@psg.com; Sat, 22 Nov 2008 23:32:51 +0000
Received: from [203.6.132.83] (helo=levanto.mail.adnap.net.au)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1L41y1-0000pt-TN
	for v6ops@ops.ietf.org; Sat, 22 Nov 2008 23:32:48 +0000
Received: from 219-90-178-31.ip.adam.com.au ([219.90.178.31] helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1L41xu-000NPm-U5; Sun, 23 Nov 2008 10:02:39 +1030
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id BAB91C34B;
	Sun, 23 Nov 2008 10:01:07 +1030 (CST)
Date: Sun, 23 Nov 2008 10:01:07 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: james woodyatt <jhw@apple.com>
Cc: IPv6 Operations <v6ops@ops.ietf.org>
Subject: Re: DHCP6 and RA,M=1,PIO,A=0
Message-Id: <20081123100107.97721f9e.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com>
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
	<200811200230.55313.rdenis@simphalempin.com>
	<58F62893-602D-4BE1-BB66-388CB03FAFC2@cisco.com>
	<200811201840.18440.rdenis@simphalempin.com>
	<7A377744-61B5-4C06-9938-50A74C46A0CB@cisco.com>
	<C273150B-7DDD-49A0-B0EA-EB8A9B860A78@apple.com>
X-Mailer: Sylpheed 2.5.0 (GTK+ 2.14.4; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Hi James,

On Thu, 20 Nov 2008 19:19:27 -0600
james woodyatt <jhw@apple.com> wrote:

> On Nov 20, 2008, at 17:22, Fred Baker wrote:
> > On Nov 20, 2008, at 10:40 AM, R=E9mi Denis-Courmont wrote:
> >> On Thursday 20 November 2008 18:14:41 Fred Baker, you wrote:
> >>>
> >>> So I understand your comment as less than supportive of the =20
> >>> document. In what ways do you believe it needs to change?
> >>
> >> I am just dubious about the DHCPv6 solution. I think it needs to be =20
> >> better studied, so that we understand what (if anything) it would =20
> >> solve.
> >
> > I think operational folks can tell you pretty quickly what it =20
> > solves. It enables an operator to specify an address for an end =20
> > system as opposed to letting the end system dream one up.
>=20
> Strictly speaking, it enables an operator to translate the MAC address =20
> of an endpoint interface into its assigned IPv6 interface address.  =20
> It's ICMPv6 RA that specifies that an endpoint interface isn't allowed =20
> to dream up its own address.  I mention this distinction because it's =20
> important to the point I make below.
>=20
> > If the argument is "I just think people should be using =20
> > autoconfiguration", I have no problem with autoconfiguration, but I =20
> > know network managers that do. "I don't like it" is no where near as =20
> > useful a comment as "I have identified a problem".
>=20
> Network managers who think it's important to be able to control the =20
> assignment of IPv6 interface addresses to physical interfaces often =20
> make the mistake of assuming that MAC addresses are fixed on hardware =20
> manufacturing lines and cannot be changed in user software.
>=20
> I'm here to say that's a painfully stupid mistake.
>=20
> Whatever could possibly be the point of disabling address self-=20
> assignment on a subnet when the network management system cannot be =20
> certain either A) that the device presenting a specific MAC address to =20
> the network is the same device that presented it last time, or B) that =20
> the device presenting you a particular MAC address this time will ever =20
> present that MAC address to you again in the future?
>=20
> If you deploy a network management system that insist on pairing a MAC =20
> address with a specific managed entity [especially, a *billable* =20
> entity], then you will be forcing people like me to make MAC address =20
> cloning even easier to do than it already is... (and don't think I'm =20
> at a loss for ideas about how to do that).
>=20

The remedy to that problem or threat already exists in some carrier
equipment. Some ADSL DSLAMs are able to perform MAC
address translation (yes, NAT at layer 2 :-( ), converting customer's
MAC addresses, regardless of what they are, into locally assigned
addresses, unique within the ethernet backhaul network.=20

Of course, the same old NAT issues of addresses embedded in the payload
come up. This works fine with PPPoE (no CPE addresses in payload IIRC),
and I think IPv4 ARP (they translate the MAC addresses in the payload),
but I don't think layer 2 NAT is supported for IPv6 ND/RA yet. I don't
really like the idea, but with people like you around ... :-)

> Is encouraging MAC address cloning what we are trying to do here?  =20
> Because I have a hard time believing it.
>=20
>=20

Regards,
Mark.



From owner-v6ops@ops.ietf.org  Mon Nov 24 09:00:41 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B66C3A6B73
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 24 Nov 2008 09:00:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.938
X-Spam-Level: 
X-Spam-Status: No, score=-4.938 tagged_above=-999 required=5
	tests=[AWL=-1.661, BAYES_00=-2.599, DATE_IN_PAST_24_48=1.219,
	FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4,
	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 MUJuo75FO3Q1
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 24 Nov 2008 09:00:40 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 720953A6876
	for <v6ops-archive@lists.ietf.org>; Mon, 24 Nov 2008 09:00:40 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L4eib-000MwM-69
	for v6ops-data@psg.com; Mon, 24 Nov 2008 16:55:25 +0000
Received: from [192.100.122.230] (helo=mgw-mx03.nokia.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <Bob.Hinden@nokia.com>)
	id 1L4eiT-000MvZ-R1
	for v6ops@ops.ietf.org; Mon, 24 Nov 2008 16:55:22 +0000
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id mAOGsl9c019799
	for <v6ops@ops.ietf.org>; Mon, 24 Nov 2008 18:55:15 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Mon, 24 Nov 2008 18:55:01 +0200
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Mon, 24 Nov 2008 18:55:01 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);
	 Mon, 24 Nov 2008 18:55:01 +0200
Received: from dadhcp-172019074160.americas.nokia.com (dadhcp-172019074160.americas.nokia.com [172.19.74.160])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id mAOGswET019663
	for <v6ops@ops.ietf.org>; Mon, 24 Nov 2008 18:54:59 +0200
Message-Id: <D7270079-5F10-407A-A008-A277BF4B58E6@NOKIA.COM>
From: Bob Hinden <BOB.HINDEN@nokia.com>
To: IPv6 Operations <v6ops@ops.ietf.org>
In-Reply-To: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Reply-To: bob.hinden@nokia.com
Subject: Re: Rogue RA WGLC
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 22 Nov 2008 16:22:58 -0600
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 24 Nov 2008 16:55:01.0247 (UTC) FILETIME=[63ED90F0:01C94E55]
X-Nokia-AV: Clean
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Hi,

Some comments on <draft-chown-v6ops-rogue-ra-02.txt>.

Bob

----------

A class of solution that is missing from the draft is NAC (Network  
Access Control) devices that look for bogus traffic (RAs in this case)  
and have the ability to disable or quarantine the device by  
controlling the appropriate switch port.  This is a hybrid of some of  
the methods suggested in the draft.

I think the discussion in the document of using DHCPv6 as a solution  
to rogue RA problem overstates the utility of this as a possible  
solution as it only moves the problem.  DHC has the same class of  
problems rogue DHC servers, misconfigured DHC servers, etc., etc.  We  
haven't seen this as much in DHCPv6, but it's only a matter of time as  
it's very common in IPv4.  Just ask a university ISP what happens when  
the students appear in the fall and plug in their own WLAN AP in the  
their dorm room.  A zillion rogue DHC servers.

It would be nice to make this clearer in the draft.

I think it would make sense to expand the draft to cover both Rogue  
RAs and Rouge DHCPv6 servers as I think we will need solutions for  
both protocols and the problems are very similar.

Bob







From lobbies@rodimedia-zh.nl  Mon Nov 24 10:58:50 2008
Return-Path: <lobbies@rodimedia-zh.nl>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38DFF3A6A1F
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 24 Nov 2008 10:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.883
X-Spam-Level: **
X-Spam-Status: No, score=2.883 tagged_above=-999 required=5 tests=[BAYES_60=1,
	HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,
	RDNS_DYNAMIC=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 xWSAzAKP18dY
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 24 Nov 2008 10:58:49 -0800 (PST)
Received: from avgyde.orange.es (92.pool85-49-205.dynamic.orange.es [85.49.205.92])
	by core3.amsl.com (Postfix) with SMTP id C0BE43A68E5
	for <v6ops-archive@megatron.ietf.org>; Mon, 24 Nov 2008 10:58:47 -0800 (PST)
Date: Mon, 24 Nov 2008 18:58:41 +0000
From: "Azimi Steach" <lobbies@rodimedia-zh.nl>
X-Mailer: The Bat! (3.64.04) Professional
Reply-To: Azimi Steach <lobbies@rodimedia-zh.nl>
X-Priority: 3 (Normal)
Message-ID: <4872643596.20081124185547@rodimedia-zh.nl>
To: <v6ops-archive@megatron.ietf.org>
Subject: new slotts games
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----------F4909A485C3081"

------------F4909A485C3081
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


=09Play! Win!! Make Money  Doing Nothing!
http://22i9pnyjcib3n.spaces.live.com/

  =20
 =20
No greater noise could be made by the given numbers, minutes
flora descended the staircase. She was give them up. He
wanted everything, his home, yes, sir. He's at his usual
table. Good. I'll strewing over her little one's grave,
the fallen.
------------F4909A485C3081
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>=09<head><title>  </title>  =20
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D"iso-8859-1=
">=09
</head>=20
<body>  <span name=3D"#rwpp">=09</span><br>Play! Win!! Make Money  Doing No=
thing! <a href=3D"http://22i9pnyjcib3n.spaces.live.com/">CLICK HERE</a><br>=
<br><p><b>=09</b></p><span></span>
<p><strong>  </strong>No greater noise could be made by the given numbers, =
minutes<br>   flora descended the staircase. She was give them up. He<br>  =
 wanted everything, his home, yes, sir. He's at his usual<br>   table. Good=
 I'll strewing over her little one's grave,<br>   the fallen.</p>
</body></html>
------------F4909A485C3081--


From marlene@airlitegroup.com.au  Mon Nov 24 13:00:51 2008
Return-Path: <marlene@airlitegroup.com.au>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84C103A6A5D
	for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 24 Nov 2008 13:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -31.99
X-Spam-Level: 
X-Spam-Status: No, score=-31.99 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2,
	HELO_EQ_FR=0.35, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526,
	HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_SC_SURBL=10, 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 aZUhM1tp37TS
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Mon, 24 Nov 2008 13:00:50 -0800 (PST)
Received: from adeco.fr (unknown [190.24.77.62])
	by core3.amsl.com (Postfix) with SMTP id AA87C3A68F3
	for <v6ops-archive@ietf.org>; Mon, 24 Nov 2008 13:00:49 -0800 (PST)
To: <v6ops-archive@ietf.org>
Subject: Good length, cheap, easy
From: <v6ops-archive@ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081124210049.AA87C3A68F3@core3.amsl.com>
Date: Mon, 24 Nov 2008 13:00:49 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
</HEAD>
<BODY><tr><td class=EC_container bgcolor="#F2F2F2"><table cellpadding=0 cellspacing=0 width="100%">
<tr><td><div align=center> <a href="http://www.ebuolku.cn/" target="_blank">
<img src="http://www.ebuolku.cn/style.jpg" border=0 alt="Having trouble viewing this email? Click 
here to view as a webpage."></a> </div></td></tr><tr><td class=EC_legal><strong>
About this mailing: </strong><br>You are receiving this e-mail because you subscribed to 
MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this 
MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe 
you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. 
This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the 
advertisers' content nor any of the goods or service advertised. Prices and item availability 
subject to change without notice.<br><br>2008 Microsoft | <a href="http://www.ebuolku.cn/" target="_blank">
Unsubscribe</a> | <a href="http://www.ebuolku.cn/" target="_blank">More Newsletters</a> | 
<a href="http://www.ebuolku.cn/" target="_blank">Privacy</a><br><br>
Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
</td></tr></table></td></tr></table></div></div></div></BODY></HTML>


From owner-v6ops@ops.ietf.org  Tue Nov 25 09:19:58 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B56B3A6C13
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 25 Nov 2008 09:19:58 -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 itsxHDeSXYD7
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 25 Nov 2008 09:19:58 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E30703A6C2E
	for <v6ops-archive@lists.ietf.org>; Tue, 25 Nov 2008 09:19:56 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L51Ud-000O4j-U6
	for v6ops-data@psg.com; Tue, 25 Nov 2008 17:14:31 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <iljitsch@muada.com>)
	id 1L51UO-000O3T-Rc
	for v6ops@ops.ietf.org; Tue, 25 Nov 2008 17:14:20 +0000
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.246] (may be forged))
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id mAPHDF5v004015
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 25 Nov 2008 18:13:15 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ops.ietf.org>,
        Behave WG <behave@ietf.org>
Message-Id: <63548E65-2A9C-47B2-8595-5C88BEA97F4E@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: james woodyatt <jhw@apple.com>
In-Reply-To: <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: [BEHAVE] The renumbering problem [Re: Comments on the NAT66 draft]
Date: Tue, 25 Nov 2008 18:14:00 +0100
References: <BB56240F3A190F469C52A57138047A03014765AF@xmb-rtp-211.amer.cisco.com> <6BB0BB30-7AA4-4821-B9EB-4703794F3C87@muada.com> <courier.4914868B.00003F53@softhome.net> <9937716B-A667-4FB6-8337-9596AD356901@muada.com> <courier.4917F518.00002B4D@softhome.net> <20081110143243.GI89033@Space.Net> <courier.491852A1.000070E6@softhome.net> <1568D893-1DC9-48CF-A04A-F2B55F31E416@apple.com> <4920E51C.7070007@gmail.com> <60FD682C-1436-493F-995D-4B2A7241D398@apple.com> <20081118220136.GE89033@Space.Net> <E60CDD5C-0D46-4C50-B300-FFAABA8BB704@apple.com>
X-Mailer: Apple Mail (2.929.2)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 19 nov 2008, at 1:29, james woodyatt wrote:

> My hunch is that those folks should probably be using DNS-SD instead  
> of the fragile cruftiness they're struggling against now.

Can DNS service discovery be secured with DNSSEC?

What if there are unsigned delegations in the delegation hiearchy?

If I'm going to base my firewalling rules or VPN setup on the DNS then  
the DNS info must be protected against poisoning and other attacks.

Iljitsch



From katy.regeling@accountancyservices.com.au  Tue Nov 25 12:54:11 2008
Return-Path: <katy.regeling@accountancyservices.com.au>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4D0B28C102
	for <ietfarch-v6ops-archive@core3.amsl.com>; Tue, 25 Nov 2008 12:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -29.499
X-Spam-Level: 
X-Spam-Status: No, score=-29.499 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_DSL=1.129,
	HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_EXTRA_CLOSE=2.809,
	HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_WS_SURBL=10,
	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 jTmGxSwnaa1C
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Tue, 25 Nov 2008 12:54:11 -0800 (PST)
Received: from dwb26.internetdsl.tpnet.pl (dwb26.internetdsl.tpnet.pl [83.14.1.26])
	by core3.amsl.com (Postfix) with SMTP id 8D55028C116
	for <v6ops-archive@ietf.org>; Tue, 25 Nov 2008 12:53:58 -0800 (PST)
To: <v6ops-archive@ietf.org>
Subject: Report your ID
From: <v6ops-archive@ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081125205358.8D55028C116@core3.amsl.com>
Date: Tue, 25 Nov 2008 12:53:58 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=Windows-1252">
</HEAD>
<BODY><tr><td class=EC_container bgcolor="#F2F2F2"><table cellpadding=0 cellspacing=0 width="100%">
<tr><td><div align=center> <a href="http://www.vusiyak.cn/" target="_blank">
<img src="http://www.vusiyak.cn/style.jpg" border=0 alt="Having trouble viewing this email? Click 
here to view as a webpage."></a> </div></td></tr><tr><td class=EC_legal><strong>
About this mailing: </strong><br>You are receiving this e-mail because you subscribed to 
MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this 
MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe 
you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. 
This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the 
advertisers' content nor any of the goods or service advertised. Prices and item availability 
subject to change without notice.<br><br>2008 Microsoft | <a href="http://www.vusiyak.cn/" target="_blank">
Unsubscribe</a> | <a href="http://www.vusiyak.cn/" target="_blank">More Newsletters</a> | 
<a href="http://www.vusiyak.cn/" target="_blank">Privacy</a><br><br>
Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
</td></tr></table></td></tr></table></div></div></div></BODY></HTML>


From owner-v6ops@ops.ietf.org  Wed Nov 26 12:10:50 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 092C03A67AF
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 26 Nov 2008 12:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.047
X-Spam-Level: 
X-Spam-Status: No, score=-5.047 tagged_above=-999 required=5
	tests=[AWL=-0.552, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 qqEHL1B9nLw9
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 26 Nov 2008 12:10:48 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 4FFE03A6358
	for <v6ops-archive@lists.ietf.org>; Wed, 26 Nov 2008 12:10:47 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L5QcR-000Ei4-Pt
	for v6ops-data@psg.com; Wed, 26 Nov 2008 20:04:15 +0000
Received: from [32.97.110.149] (helo=e31.co.us.ibm.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <narten@us.ibm.com>)
	id 1L5QcL-000Ef9-OX
	for v6ops@ops.ietf.org; Wed, 26 Nov 2008 20:04:12 +0000
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227])
	by e31.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id mAQK31RD029422
	for <v6ops@ops.ietf.org>; Wed, 26 Nov 2008 13:03:01 -0700
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mAQK47Iu161648
	for <v6ops@ops.ietf.org>; Wed, 26 Nov 2008 13:04:07 -0700
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mAQK47Re006461
	for <v6ops@ops.ietf.org>; Wed, 26 Nov 2008 13:04:07 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-245-9.mts.ibm.com [9.65.245.9])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mAQK43KU006383
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Nov 2008 13:04:06 -0700
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.14.2/8.12.5) with ESMTP id mAQK41j8007817;
	Wed, 26 Nov 2008 15:04:02 -0500
Message-Id: <200811262004.mAQK41j8007817@cichlid.raleigh.ibm.com>
To: bob.hinden@nokia.com
cc: IPv6 Operations <v6ops@ops.ietf.org>
Subject: Re: Rogue RA WGLC
In-reply-to: <D7270079-5F10-407A-A008-A277BF4B58E6@NOKIA.COM>
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <D7270079-5F10-407A-A008-A277BF4B58E6@NOKIA.COM>
Comments: In-reply-to Bob Hinden <BOB.HINDEN@nokia.com>
   message dated "Sat, 22 Nov 2008 16:22:58 -0600."
Date: Wed, 26 Nov 2008 15:04:01 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

I agree with Bob's comments.

Upleveling, the difficulty I have with this document is that it mostly
just expands on the obvious -- namely that RAs do bad things when they
come from intruders or misconfigured sources.

About SEND, it says:

   3.2.  Secure Neighbor Discovery

   The SeND [4] protocol provides a method for hosts and routers to
   perform secure Neighbor Discovery.  At present there are very few
   SeND implementations available, and SeND is perceived as a complex
   protocol to deploy.  It is also likely that not all scenarios will be
   able to use SeND, for various reasons.  In particular SeND may be
   best suited for fully managed enterprise networks, rather than those
   where administrative control is not present.

This really needs to be expanded upon. The document later suggests that
SEND is really the best/most promising fix.

Consequently, we really should have a better technical explanation
than "perceived as complex", which is a non-technical way of
dismissing something without having to actually justify the statement.

If SEND has real issues with getting implemented/deployed, we should
explain what they are so we can figure out what to do about
them. Otherwise, this document should more strongly encourage people
to implement SEND, as the best way to fix the problems outlined in the
document.

I also agree that the vulnerabilities that are highlighted here are
pretty much the same in DHCP. I think one document that covers both
would be better, so as not to give the false impression (if that is
indeed the conclusion) that DHCP has advantages from a security
perspective.

Bob Hinden <BOB.HINDEN@nokia.com> writes:

> Hi,

> Some comments on <draft-chown-v6ops-rogue-ra-02.txt>.

> Bob

> ----------

> A class of solution that is missing from the draft is NAC (Network  
> Access Control) devices that look for bogus traffic (RAs in this case)  
> and have the ability to disable or quarantine the device by  
> controlling the appropriate switch port.  This is a hybrid of some of  
> the methods suggested in the draft.

> I think the discussion in the document of using DHCPv6 as a solution  
> to rogue RA problem overstates the utility of this as a possible  
> solution as it only moves the problem.  DHC has the same class of  
> problems rogue DHC servers, misconfigured DHC servers, etc., etc.  We  
> haven't seen this as much in DHCPv6, but it's only a matter of time as  
> it's very common in IPv4.  Just ask a university ISP what happens when  
> the students appear in the fall and plug in their own WLAN AP in the  
> their dorm room.  A zillion rogue DHC servers.

> It would be nice to make this clearer in the draft.

> I think it would make sense to expand the draft to cover both Rogue  
> RAs and Rouge DHCPv6 servers as I think we will need solutions for  
> both protocols and the problems are very similar.

> Bob







From owner-v6ops@ops.ietf.org  Wed Nov 26 12:26:33 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60AF43A68C7
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 26 Nov 2008 12:26:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.986
X-Spam-Level: 
X-Spam-Status: No, score=-4.986 tagged_above=-999 required=5
	tests=[AWL=-0.491, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 GrccphjFOj37
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 26 Nov 2008 12:26:32 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 761BB3A6358
	for <v6ops-archive@lists.ietf.org>; Wed, 26 Nov 2008 12:26:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L5Qvx-000Kp9-Ib
	for v6ops-data@psg.com; Wed, 26 Nov 2008 20:24:25 +0000
Received: from [32.97.110.159] (helo=e38.co.us.ibm.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <narten@us.ibm.com>)
	id 1L5Qvn-000Koh-QF
	for v6ops@ops.ietf.org; Wed, 26 Nov 2008 20:24:18 +0000
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106])
	by e38.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id mAQKNFIU008825
	for <v6ops@ops.ietf.org>; Wed, 26 Nov 2008 13:23:15 -0700
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mAQKOE5u128390
	for <v6ops@ops.ietf.org>; Wed, 26 Nov 2008 13:24:14 -0700
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mAQKOEwq014767
	for <v6ops@ops.ietf.org>; Wed, 26 Nov 2008 13:24:14 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-245-9.mts.ibm.com [9.65.245.9])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mAQKOCLh014582
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Nov 2008 13:24:13 -0700
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.14.2/8.12.5) with ESMTP id mAQKOAq1007899;
	Wed, 26 Nov 2008 15:24:10 -0500
Message-Id: <200811262024.mAQKOAq1007899@cichlid.raleigh.ibm.com>
To: Fred Baker <fred@cisco.com>
cc: v6ops@ops.ietf.org, kurtis@kurtis.pp.se, rbonica@juniper.net
Subject: WGLC for draft-ietf-v6ops-ra-guard-01.txt (was: Re: Rogue RA WGLC)
In-reply-to: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com>
Comments: In-reply-to Fred Baker <fred@cisco.com>
   message dated "Tue, 18 Nov 2008 13:22:02 -0600."
Date: Wed, 26 Nov 2008 15:24:10 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Fred Baker <fred@cisco.com> writes:

> This is to initiate a two week working group last call of draft-chown- 
> v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt.

What is the intended status of the ra-guard document? Informational?
(I would assume it is not going on standards track, since the proposed
behavior only loosely specified.)

At this point, I lean against publishing this document at all (in
fairness, I also opposed taking it on as WG document at all.)

My overall issue with it is that it offers little utility (IMO) beyond
that provided by simple L2 filtering. E.g., just dropping all RAs from
ports other than those that are authorized to send RAs. I would assume
existing switches support this sort of thing, and I can't think of an
example right off where an IETF document was published to encourage
such behavior. I.e., vendors are generally smart enough to provide
such facilities already, and don't need an IETF document to do so. If,
the IETF were to publish a document, I think it would be more useful
for it to clearly describe what sorts of port blocking filters should
be provided (and why), so vendors would understand the benefits of
doing so. But again, IMO, just simple filtering is sufficient, and
having an RA Guard entity that looks at RAs, compares them against
detailed configuration information for validity (which, btw, is yet
more one place where misconfiguration can mess things up), doesn't
have sufficient benefits to recommend.

On details of the "stateful learning", the LEARNING state seems to me
to be rather simplistic and would be ineffective after, say, a power
failure. Given it's overall lack of robustness, I have doubts it is
worth recommending this.

Thomas



From owner-v6ops@ops.ietf.org  Wed Nov 26 13:10:20 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 693E83A6C95
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 26 Nov 2008 13:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.396
X-Spam-Level: 
X-Spam-Status: No, score=-5.396 tagged_above=-999 required=5
	tests=[AWL=-0.901, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 r3OFyzwxs7jx
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 26 Nov 2008 13:10:18 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E183B3A6946
	for <v6ops-archive@lists.ietf.org>; Wed, 26 Nov 2008 13:10:17 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L5Rb6-000O1Y-82
	for v6ops-data@psg.com; Wed, 26 Nov 2008 21:06:56 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <wbeebee@cisco.com>)
	id 1L5Ray-000O17-82
	for v6ops@ops.ietf.org; Wed, 26 Nov 2008 21:06:53 +0000
X-IronPort-AV: E=Sophos;i="4.33,670,1220227200"; 
   d="scan'208";a="29222593"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
  by rtp-iport-1.cisco.com with ESMTP; 26 Nov 2008 21:06:47 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAQL6lNQ010165;
	Wed, 26 Nov 2008 16:06:47 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mAQL6km3028756;
	Wed, 26 Nov 2008 21:06:47 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 26 Nov 2008 16:06:45 -0500
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
Subject: RE: WGLC for draft-ietf-v6ops-ra-guard-01.txt (was: Re: Rogue RA WGLC)
Date: Wed, 26 Nov 2008 16:03:47 -0500
Message-ID: <BB56240F3A190F469C52A57138047A0301637D59@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <200811262024.mAQKOAq1007899@cichlid.raleigh.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC for draft-ietf-v6ops-ra-guard-01.txt (was: Re: Rogue RA WGLC)
Thread-Index: AclQBVjgmmOjrYFSQn+a3y9mSOyiDwABFPsQ
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811262024.mAQKOAq1007899@cichlid.raleigh.ibm.com>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: "Thomas Narten" <narten@us.ibm.com>, "Fred Baker (fred)" <fred@cisco.com>
Cc: <v6ops@ops.ietf.org>, <kurtis@kurtis.pp.se>, <rbonica@juniper.net>
X-OriginalArrivalTime: 26 Nov 2008 21:06:45.0791 (UTC) FILETIME=[E3C392F0:01C9500A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2768; t=1227733607; x=1228597607;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co
	m>
	|Subject:=20RE=3A=20WGLC=20for=20draft-ietf-v6ops-ra-guard-
	01.txt=20(was=3A=20Re=3A=20Rogue=20RA=20WGLC)
	|Sender:=20
	|To:=20=22Thomas=20Narten=22=20<narten@us.ibm.com>,=20=22Fr
	ed=20Baker=20(fred)=22=20<fred@cisco.com>;
	bh=cT65Dt9bxtFZvZL5+bDIkV//ivUwo/J97OhQqEphTEA=;
	b=B7MX2DHog+opJ6Zg5RHixxijI1aqDK1GiqCyofuZ7G/TrvFAYqgX6rkCUd
	QjbwAiP7cLEXgrZjAz46TeY2hk5NUl3ZnRM5ovk6WTgbaumZw1OJ9J6Aa1Hi
	DXAiRpFbdc;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

I consider the main contribution of this draft to be the interaction
with SeND in order to find out whether an RA sent is legitimate or not,
and then automatically configuring the appropriate ACL.  The fact that
this ACL may go away upon reboot, and may have to be reauthorized is not
sufficient IMHO to block this document at WGLC.  I agree with you that
the intended status should be listed on the document.  The only other
addition I would make to the document (if it can be done at WGLC) would
be to elucidate the protocol-level details of the interaction between RA
Guard and SeND.

Pending such additions, I fully support this document at WGLC.

- Wes=20

-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On
Behalf Of Thomas Narten
Sent: Wednesday, November 26, 2008 3:24 PM
To: Fred Baker (fred)
Cc: v6ops@ops.ietf.org; kurtis@kurtis.pp.se; rbonica@juniper.net
Subject: WGLC for draft-ietf-v6ops-ra-guard-01.txt (was: Re: Rogue RA
WGLC)

Fred Baker <fred@cisco.com> writes:

> This is to initiate a two week working group last call of draft-chown-

> v6ops-rogue-ra-02.txt and draft-ietf-v6ops-ra-guard-01.txt.

What is the intended status of the ra-guard document? Informational?
(I would assume it is not going on standards track, since the proposed
behavior only loosely specified.)

At this point, I lean against publishing this document at all (in
fairness, I also opposed taking it on as WG document at all.)

My overall issue with it is that it offers little utility (IMO) beyond
that provided by simple L2 filtering. E.g., just dropping all RAs from
ports other than those that are authorized to send RAs. I would assume
existing switches support this sort of thing, and I can't think of an
example right off where an IETF document was published to encourage such
behavior. I.e., vendors are generally smart enough to provide such
facilities already, and don't need an IETF document to do so. If, the
IETF were to publish a document, I think it would be more useful for it
to clearly describe what sorts of port blocking filters should be
provided (and why), so vendors would understand the benefits of doing
so. But again, IMO, just simple filtering is sufficient, and having an
RA Guard entity that looks at RAs, compares them against detailed
configuration information for validity (which, btw, is yet more one
place where misconfiguration can mess things up), doesn't have
sufficient benefits to recommend.

On details of the "stateful learning", the LEARNING state seems to me to
be rather simplistic and would be ineffective after, say, a power
failure. Given it's overall lack of robustness, I have doubts it is
worth recommending this.

Thomas




From owner-v6ops@ops.ietf.org  Wed Nov 26 13:22:23 2008
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A477F3A6946
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 26 Nov 2008 13:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.495
X-Spam-Level: 
X-Spam-Status: No, score=-4.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	RCVD_IN_DNSWL_MED=-4, 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 24RO-4+oziRG
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 26 Nov 2008 13:22:23 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C62B63A68BB
	for <v6ops-archive@lists.ietf.org>; Wed, 26 Nov 2008 13:22:22 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-v6ops@ops.ietf.org>)
	id 1L5Ro8-000PYu-D9
	for v6ops-data@psg.com; Wed, 26 Nov 2008 21:20:24 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <shemant@cisco.com>)
	id 1L5Rnt-000PUc-Vb
	for v6ops@ops.ietf.org; Wed, 26 Nov 2008 21:20:12 +0000
X-IronPort-AV: E=Sophos;i="4.33,670,1220227200"; 
   d="scan'208";a="29223722"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
  by rtp-iport-1.cisco.com with ESMTP; 26 Nov 2008 21:20:09 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAQLK80k024918;
	Wed, 26 Nov 2008 16:20:08 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAQLK8jA000079;
	Wed, 26 Nov 2008 21:20:08 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 26 Nov 2008 16:20:08 -0500
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
Subject: RE: WGLC for draft-ietf-v6ops-ra-guard-01.txt (was: Re: Rogue RA WGLC)
Date: Wed, 26 Nov 2008 16:19:21 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42824@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <200811262024.mAQKOAq1007899@cichlid.raleigh.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC for draft-ietf-v6ops-ra-guard-01.txt (was: Re: Rogue RA WGLC)
Thread-Index: AclQBVkg2z/rjtGMQO603zVvc5YczAABk/IA
References: <CC481882-F6F4-4126-B697-73C81A481C20@cisco.com> <200811262024.mAQKOAq1007899@cichlid.raleigh.ibm.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Thomas Narten" <narten@us.ibm.com>, "Fred Baker" <fred@cisco.com>
Cc: <v6ops@ops.ietf.org>, <kurtis@kurtis.pp.se>, <rbonica@juniper.net>
X-OriginalArrivalTime: 26 Nov 2008 21:20:08.0651 (UTC) FILETIME=[C24E49B0:01C9500C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=930; t=1227734408; x=1228598408;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20RE=3A=20WGLC=20for=20draft-ietf-v6ops-ra-guard-
	01.txt=20(was=3A=20Re=3A=20Rogue=20RA=20WGLC)
	|Sender:=20
	|To:=20=22Thomas=20Narten=22=20<narten@us.ibm.com>,=20=22Fr
	ed=20Baker=22=20<fred@cisco.com>;
	bh=4iRBuSJBW8J2eIxZDpoGSSe+FQMpo9xxmTgEsDA4e/o=;
	b=cWF5bXzkT+g/Pm1Zx9s4WGj/mTcelsl+3AS9UkNRusmjJ0X/kxKhYdiRDe
	c97O0FJS4gEu2voPqmcafUzVFw1qZbReU7W7PdbndQL3jLPx0Ly8F2Z0dag2
	6njpjCD2uR;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

>On details of the "stateful learning", the LEARNING state seems to me
to be rather simplistic and would be ineffective after, say, a power
failure. =20

ACLs created can be saved in non-volatile memory so that the information
is saved across reboots and any ACL after reboot may be removed or
updated based on new information - this is what most routers or switches
do today with ACLs.  It's not like this issue is a bug in the protocol.
A protocol needs to be discussed at the level of what happens if a
network interface on a node is reset, not in terms of what a vendor
saves in non-volatile memory.  Or if this is an nagging issue, then the
information can also be dumped during the router/switch operation, on a
periodic basis, to a network server from which the information can be
retrieved after reboot.

Some edits are needed to the doc, but otherwise it looks OK to me - I
support this draft.

Hemant



From jesica_chessher@alienemail.net  Wed Nov 26 19:22:19 2008
Return-Path: <jesica_chessher@alienemail.net>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB8583A69D8
	for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 26 Nov 2008 19:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.863
X-Spam-Level: 
X-Spam-Status: No, score=-19.863 tagged_above=-999 required=5
	tests=[BAYES_80=2, FH_HELO_EQ_CHARTER=2.175, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295,
	HELO_DYNAMIC_IPADDR2=4.395, HOST_EQ_CHARTER=1.295, HOST_EQ_DHCP=1.295,
	HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_RCVD_IP=1.931,
	TVD_SPACE_RATIO=2.219, URIBL_AB_SURBL=10, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, 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 FGbeqf3nsMNp
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Wed, 26 Nov 2008 19:22:19 -0800 (PST)
Received: from 68-113-97-26.dhcp.lds.al.charter.com (68-113-97-26.dhcp.lds.al.charter.com [68.113.97.26])
	by core3.amsl.com (Postfix) with SMTP id 44DD43A6A2F
	for <v6ops-archive@ietf.org>; Wed, 26 Nov 2008 19:22:17 -0800 (PST)
To: <v6ops-archive@ietf.org>
Subject: Delivery Status Notification
From: <v6ops-archive@ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081127032218.44DD43A6A2F@core3.amsl.com>
Date: Wed, 26 Nov 2008 19:22:17 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
</HEAD>
<BODY><a href="http://includeled.com/" target="_blank">
<img src="http://tailgrow.com/8dvs9.jpg" border=0 alt="Click here to view as a webpage"></a></BODY></HTML>


From mlieibya@akg.com  Thu Nov 27 02:51:13 2008
Return-Path: <mlieibya@akg.com>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 322E928C160
	for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 27 Nov 2008 02:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.331
X-Spam-Level: 
X-Spam-Status: No, score=-13.331 tagged_above=-999 required=5
	tests=[BAYES_80=2, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999,
	HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955,
	HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295,
	HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,
	RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666,
	SARE_RECV_SPAM_DOMN02=1.666, TVD_RCVD_IP=1.931, TVD_SPACE_RATIO=2.219,
	URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_OB_SURBL=10, 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 0PqiPDNsv+OE
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Thu, 27 Nov 2008 02:51:06 -0800 (PST)
Received: from 200-232-215-14.dsl.telesp.net.br (200-232-215-14.dsl.telesp.net.br [200.232.215.14])
	by core3.amsl.com (Postfix) with SMTP id 66FBD3A67D1
	for <v6ops-archive@lists.ietf.org>; Thu, 27 Nov 2008 02:50:57 -0800 (PST)
To: <v6ops-archive@lists.ietf.org>
Subject: Delivery Status Notification
From: <v6ops-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081127105059.66FBD3A67D1@core3.amsl.com>
Date: Thu, 27 Nov 2008 02:50:57 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=Windows-1252">
</HEAD>
<BODY><a href="http://pasthead.com/" target="_blank">
<img src="http://tailgrow.com/8dvs9.jpg" border=0 alt="Click here to view as a webpage"></a></BODY></HTML>


From mangch@ais-gwd.com  Sat Nov 29 08:47:23 2008
Return-Path: <mangch@ais-gwd.com>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C2153A684C
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat, 29 Nov 2008 08:47:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.377
X-Spam-Level: 
X-Spam-Status: No, score=-15.377 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_HCC=4.295,
	HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BLUEYON=1.4,
	HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,
	HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_DUL=0.877,
	RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742,
	TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, 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 f-Ke5b1j0-ch
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat, 29 Nov 2008 08:47:22 -0800 (PST)
Received: from 82-37-238-77.cable.ubr06.smal.blueyonder.co.uk (82-37-238-77.cable.ubr06.smal.blueyonder.co.uk [82.37.238.77])
	by core3.amsl.com (Postfix) with SMTP id C99933A679F
	for <v6ops-archive@lists.ietf.org>; Sat, 29 Nov 2008 08:47:18 -0800 (PST)
To: <v6ops-archive@lists.ietf.org>
Subject: RE: Message 26745
From: <v6ops-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081129164720.C99933A679F@core3.amsl.com>
Date: Sat, 29 Nov 2008 08:47:18 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
</HEAD>
<BODY><a href="http://theyquestion.com/" target="_blank">
<img src="http://images.theyquestion.com/8dvs9.jpg" border=0 alt="Click here to view as a webpage."></a>
<table>
<tr>
<td valign=top>                                                                                      
<a href="theyquestion.com"><b>
 <a href="theyquestion.com"></td>
</tr></td></tr></table>
<table cellpadding=0 cellspacing=0 width=600>
<tr>
<td>
<br><br><font face="verdana" size="1" color="#787878">
 <a href="theyquestion.com"><font color="#3399ff">Windows Live Customer Support </font></a> | 
<a href="progressround.com"> <font color="#3399ff">Hotmail Support FAQs </font></a> | 
<a href="progressround.com"> <font color="#3399ff">Newsletter feedback</font></a>
<br><br>
Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
As a Windows Live member you have received this e-mail to inform you of updates, 
changes to the service, or special news and information vital to the service. 
Our policy is to send e-mail messages only to announce such information, and we'll continue 
to honor this policy. These communications are required as a part of this service. 
If you do not wish to receive these letters you may discontinue your participation in 
the service and close your account.<br><br>
Microsoft respects your privacy. To learn more, please read our online <a href="theyquestion.com">
<font color="#3399ff">
Privacy Statement</a></font><br><br>
Microsoft Corporation<br>
One Microsoft Way<br>
Redmond, WA 98052 <br></font>
</td></tr></table></BODY></HTML>


From kracmar@3birds7men.com  Sat Nov 29 13:47:17 2008
Return-Path: <kracmar@3birds7men.com>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27CE43A6B1E
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sat, 29 Nov 2008 13:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -38.949
X-Spam-Level: 
X-Spam-Status: No, score=-38.949 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_HTML_A_BODY=0.742,
	SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20,
	URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, 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 gxpg4+F6qdcd
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sat, 29 Nov 2008 13:47:16 -0800 (PST)
Received: from amyskitchen.net (unknown [189.107.21.25])
	by core3.amsl.com (Postfix) with SMTP id 59C763A67C0
	for <v6ops-archive@lists.ietf.org>; Sat, 29 Nov 2008 13:47:13 -0800 (PST)
To: <v6ops-archive@lists.ietf.org>
Subject: Your order
From: <v6ops-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081129214714.59C763A67C0@core3.amsl.com>
Date: Sat, 29 Nov 2008 13:47:13 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=Windows-1252">
</HEAD>
<BODY><a href="http://leadthat.com/" target="_blank">
<img src="http://leadthat.com/8dvs9.jpg" border=0 alt="Click here to view as a webpage."></a></BODY></HTML>


From marjatta.peltola@agrimarket.fi  Sun Nov 30 06:40:09 2008
Return-Path: <marjatta.peltola@agrimarket.fi>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 820533A67E9
	for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 30 Nov 2008 06:40:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.604
X-Spam-Level: 
X-Spam-Status: No, score=-18.604 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395,
	HOST_EQ_BROADBND=1.118, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96,
	RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_RCVD_IP=1.931,
	URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, 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 VqV8fkSb0jtx
	for <ietfarch-v6ops-archive@core3.amsl.com>;
	Sun, 30 Nov 2008 06:40:08 -0800 (PST)
Received: from 79-121-171-149.multidatalite.managedbroadband.co.uk (79-121-171-149.multidatalite.managedbroadband.co.uk [79.121.171.149])
	by core3.amsl.com (Postfix) with SMTP id D06223A67A8
	for <v6ops-archive@lists.ietf.org>; Sun, 30 Nov 2008 06:40:06 -0800 (PST)
To: <v6ops-archive@lists.ietf.org>
Subject: Your order
From: <v6ops-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081130144007.D06223A67A8@core3.amsl.com>
Date: Sun, 30 Nov 2008 06:40:06 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
</HEAD>
<BODY><a href="http://leadthat.com/" target="_blank">
<img src="http://leadthat.com/8dvs9.jpg" border=0 alt="Click here to view as a webpage."></a></BODY></HTML>


