
From root@core3.amsl.com  Wed Feb  4 19:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id ADCA728C1C0; Wed,  4 Feb 2009 19:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090205031501.ADCA728C1C0@core3.amsl.com>
Date: Wed,  4 Feb 2009 19:15:01 -0800 (PST)
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action:draft-ietf-softwire-encaps-safi-05.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2009 03:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Softwires Working Group of the IETF.


	Title           : BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute
	Author(s)       : P. Mohapatra, E. Rosen
	Filename        : draft-ietf-softwire-encaps-safi-05.txt
	Pages           : 14
	Date            : 2009-02-04

In certain situations, transporting a packet from one Border Gateway
Protocol (BGP) speaker to another, the BGP next hop, requires that
the packet be encapsulated by the first BGP speaker and decapsulated
by the second. To support these situations, there needs to be some
agreement between the two BGP speakers with regard to the
"encapsulation information", i.e., the format of the encapsulation
header as well as the contents of various fields of the header.

The encapsulation information need not be signaled for all
encapsulation types. In the cases where the signaling is required
(such as Layer Two Tunneling Protocol - Version 3 (L2TPv3), Generic
Routing Encapsulation (GRE) with key), this draft specifies a method
by which BGP speakers can signal encapsulation information to each
other. The signaling is done by sending BGP updates using the
"Encapsulation Subsequent Address Family Identifier (SAFI)" and IPv4
or IPv6 Address Family Identifier (AFI). In the cases where no
encapsulation information needs to be signaled (such as GRE without
key), this draft specifies a BGP extended community that can be
attached to BGP UPDATE messages that carry payload prefixes to
indicate the encapsulation protocol type to be used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-encaps-safi-05.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-softwire-encaps-safi-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From wwwrun@core3.amsl.com  Mon Feb  9 06:47:16 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 858C028C11F; Mon,  9 Feb 2009 06:47:16 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090209144716.858C028C11F@core3.amsl.com>
Date: Mon,  9 Feb 2009 06:47:16 -0800 (PST)
Cc: softwires@ietf.org
Subject: [Softwires] Last Call: draft-ietf-softwire-security-requirements (Softwire Security Analysis and Requirements) to Proposed Standard
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2009 14:47:16 -0000

The IESG has received a request from the Softwires WG (softwire) to 
consider the following document:

- 'Softwire Security Analysis and Requirements '
   <draft-ietf-softwire-security-requirements-06.txt> as a Proposed Standard

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

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-softwire-security-requirements-06.txt


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


From root@core3.amsl.com  Mon Feb  9 09:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 49AA33A6A83; Mon,  9 Feb 2009 09:15:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090209171501.49AA33A6A83@core3.amsl.com>
Date: Mon,  9 Feb 2009 09:15:01 -0800 (PST)
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action:draft-ietf-softwire-hs-framework-l2tpv2-11.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2009 17:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Softwires Working Group of the IETF.


	Title           : Softwire Hub & Spoke Deployment Framework with L2TPv2
	Author(s)       : B. Storer, et al.
	Filename        : draft-ietf-softwire-hs-framework-l2tpv2-11.txt
	Pages           : 48
	Date            : 2009-02-09

This document describes the framework of the Softwire "Hub and Spoke"
solution with the Layer 2 Tunneling Protocol version 2 (L2TPv2).  The
implementation details specified in this document should be followed
to achieve interoperability among different vendor implementations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-hs-framework-l2tpv2-11.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-softwire-hs-framework-l2tpv2-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xuxh@huawei.com  Sun Feb 15 18:02:17 2009
Return-Path: <xuxh@huawei.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6085F3A6B15 for <softwires@core3.amsl.com>; Sun, 15 Feb 2009 18:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.148
X-Spam-Level: *
X-Spam-Status: No, score=1.148 tagged_above=-999 required=5 tests=[AWL=-1.146,  BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DgTm9y8w-NAQ for <softwires@core3.amsl.com>; Sun, 15 Feb 2009 18:02:16 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6AD8E3A6B13 for <softwires@ietf.org>; Sun, 15 Feb 2009 18:02:16 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KF4006UPYZRBR@szxga03-in.huawei.com> for softwires@ietf.org; Mon, 16 Feb 2009 10:02:15 +0800 (CST)
Received: from x41208a ([10.111.12.103]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KF400DQCYZRZ8@szxga03-in.huawei.com> for softwires@ietf.org; Mon, 16 Feb 2009 10:02:15 +0800 (CST)
Date: Mon, 16 Feb 2009 10:02:14 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: softwires@ietf.org
Message-id: <000c01c98fda$96bd4a40$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: AcmMN7hO3vK5xUTbTxOdWNf3wvziuwDnhGxA
Subject: [Softwires] Simple Tunnel Endpoint Signalling in BGP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 02:02:17 -0000

Hi all,

Paul and I have just submitted a draft titled "Simple Tunnel Endpoint
Signalling in BGP"[ http://tools.ietf.org/id/draft-xu-tunnel-00.txt ]. =
In
this draft, an IP address specific extended community is used for =
carring
the tunnel endpoint, which is associated with the NLRI.This allows the =
site
networks to be connected via the tunnels over the transit networks.To be
note, the difference from the SAFI draft =
(draft-ietf-softwire-encaps-safi)
is  that the tunnel endpoints are not always identical with the next-hop
fields in the BGP updates. =20

The abstract is : Virtual Aggregation (VA) is a mechanism for shrinking =
the
size of the DFZ FIB in routers [
http://tools.ietf.org/html/draft-francis-intra-va-00].  VA can result in
longer paths and increased load on routers within the ISP that deploys =
VA.
This document describes a mechanism that allows an AS that originates a
route to associate a tunnel endpoint terminating at itself with the =
route.
This allows routers in a remote AS to tunnel packets to the originating =
AS.
If transit ASes between the remote AS and the originating AS install the
prefixes associated with tunnel endpoints in their FIBs, then tunneled
packets that transit through them will take the shortest path.  This =
results
in reduced load for the transit AS, and better performance for the =
customers
at the source and destination.

Any comment appreciated.

Xiaohu=20

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]=20
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA2=D4=C211=C8=D5 18:59
> =CA=D5=BC=FE=C8=CB: francis@mpi-sws.org
> =B3=AD=CB=CD: xuxh@huawei.com
> =D6=F7=CC=E2: New Version Notification for draft-xu-tunnel-00
>=20
>=20
> A new version of I-D, draft-xu-tunnel-00.txt has been=20
> successfuly submitted by Paul Francis and posted to the IETF=20
> repository.
>=20
> Filename:	 draft-xu-tunnel
> Revision:	 00
> Title:		 Simple Tunnel Endpoint Signaling in BGP
> Creation_date:	 2009-02-11
> WG ID:		 Independent Submission
> Number_of_pages: 8
>=20
> Abstract:
> Virtual Aggregation (VA) is a mechanism for shrinking the=20
> size of the DFZ FIB in routers [I-D.francis-intra-va].  VA=20
> can result in longer paths and increased load on routers=20
> within the ISP that deploys VA.
> This document describes a mechanism that allows an AS that=20
> originates a route to associate a tunnel endpoint terminating=20
> at itself with the route.  This allows routers in a remote AS=20
> to tunnel packets to the originating AS.  If transit ASes=20
> between the remote AS and the originating AS install the=20
> prefixes associated with tunnel endpoints in their FIBs, then=20
> tunneled packets that transit through them will take the=20
> shortest path.  This results in reduced load for the transit=20
> AS, and better performance for the customers at the source=20
> and destination.
>                                                              =20
>                    =20
>=20
>=20
> The IETF Secretariat.
>=20
>=20


From root@core3.amsl.com  Mon Feb 16 09:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: softwires@ietf.org
Delivered-To: softwires@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 8886B3A6CDF; Mon, 16 Feb 2009 09:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090216170001.8886B3A6CDF@core3.amsl.com>
Date: Mon, 16 Feb 2009 09:00:01 -0800 (PST)
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action:draft-ietf-softwire-mesh-framework-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 17:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Softwires Working Group of the IETF.


	Title           : Softwire Mesh Framework
	Author(s)       : J. Wu, et al.
	Filename        : draft-ietf-softwire-mesh-framework-06.txt
	Pages           : 32
	Date            : 2009-02-16

The Internet needs to be able to handle both IPv4 and IPv6 packets.
However, it is expected that some constituent networks of the
Internet will be "single protocol" networks.  One kind of single
protocol network can parse only IPv4 packets and can process only
IPv4 routing information; another kind can parse only IPv6 packets
and can process only IPv6 routing information.  It is nevertheless
required that either kind of single protocol network be able to
provide transit service for the "other" protocol.  This is done by
passing the "other kind" of routing information from one edge of the
single protocol network to the other, and by tunneling the "other
kind" of data packet from one edge to the other.  The tunnels are
known as "Softwires".  This framework document explains how the
routing information and the data packets of one protocol are passed
through a single protocol network of the other protocol.  The
document is careful to specify when this can be done with existing
technology, and when it requires the development of new or modified
technology.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-mesh-framework-06.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-softwire-mesh-framework-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From David_Hankins@isc.org  Tue Feb 17 15:00:25 2009
Return-Path: <David_Hankins@isc.org>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E826628C192 for <softwires@core3.amsl.com>; Tue, 17 Feb 2009 15:00:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DgNY0AWjQau for <softwires@core3.amsl.com>; Tue, 17 Feb 2009 15:00:25 -0800 (PST)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 9DB9828C189 for <softwires@ietf.org>; Tue, 17 Feb 2009 15:00:23 -0800 (PST)
Received: from hcf.isc.org (dhcp-186.sql1.isc.org [204.152.187.186]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id n1HN0Yar025160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <softwires@ietf.org>; Tue, 17 Feb 2009 15:00:35 -0800
Received: by hcf.isc.org (Postfix, from userid 10200) id 2C9FC57354; Tue, 17 Feb 2009 15:02:33 -0800 (PST)
Date: Tue, 17 Feb 2009 15:02:33 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: softwires@ietf.org
Message-ID: <20090217230232.GF16400@isc.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="64j1qyTOoGvYcHb1"
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: [Softwires] Softwires configuration via DHCP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 23:00:26 -0000

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

In forming the DHCPv6 option format for Softwires configuration, I
made a few assumptions.  I would like to (hopefully _very_ briefly)
explain my rationale, and invite additional feedback before I revise
the draft.

1) That the only configuration required would be the endpoint - that
   the 'Softwires Protocol' would include as specification a single
   kind of tunnel, for example.  The presumption, for simplicity, is
   that any Softwire client can establish a connection with any
   Softwire service without needing to know "which type."  Put another
   way, all Softwire services will be externally identical.

2) That only a single endpoint is sensible.  That there wouldn't be
   a configuration where a client had multiple Softwire endpoints
   configured at once (migrated from one to another, but never
   straddling two or more at once).

3) That although many current tunneling software implementations might
   accept domain names as configuration parameters,

	a) A recursive domain name lookup after completing DHCP is
	   extra work for no benefit.  DHCP servers can and will
	   perform the lookup on behalf of the client.  These extra
	   packet exchanges are trivial, until every packet you transmit
	   drains your phone's battery.

	b) Tunneling is a "routing kind of service", and so my first
	   inclination is that operators are likely to solve tunnel
	   endpoint reachability problems ("failure modes") by using
	   classic IP routing solutions.  Consequently the
	   configuration of interest is an IPv6 address, whose
	   termination may change through changes in routing policy.

These are essentially the assumptions that went into
draft-dhankins-softwire-tunnel-option-01.

--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--64j1qyTOoGvYcHb1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkmbQggACgkQcXeLeWu2vmp3vwCglPREzSKiDrcmD+2EEnWyYHnp
2BIAninGSzfZ2L7xhdjX9wSi+guCQjjV
=46CR
-----END PGP SIGNATURE-----

--64j1qyTOoGvYcHb1--

From brian.e.carpenter@gmail.com  Tue Feb 17 18:45:38 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51E3C3A6A21 for <softwires@core3.amsl.com>; Tue, 17 Feb 2009 18:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145,  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 gw5E5IscTUa3 for <softwires@core3.amsl.com>; Tue, 17 Feb 2009 18:45:37 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by core3.amsl.com (Postfix) with ESMTP id 78E243A67D7 for <softwires@ietf.org>; Tue, 17 Feb 2009 18:45:37 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so3379292wfd.31 for <softwires@ietf.org>; Tue, 17 Feb 2009 18:45:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KANp8UuSbQqnEciukX4pDxQIvum+J7hPH0dENrYbFkQ=; b=p+JHyxtvOy2jASQ4Nzps1rMSSuUvr8pNgLH5Nk0WSjXBqtigpH34+UjoxTTlZXto9X lPe1UD8f+XgZj7Lf+6up3zJXceN9o6TmmYlP0YrCd1sdGQuPmJUH8m92C6hztUxd7zdD 4aeLnvxOdeLPMGzMe9Csvo1ktEQvH1gC0whiw=
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=ZFWpvgpRFu6ZSwdiYeZP6QhI8GYDHxzIWNzsf5qpnyD+KrxkMiGoH4b0CqqusRiTZa zBU0WhNAKnKpjwOUc7ntmndAiQbHZU+HnooPfLoNSic2h4rQd1Ep9DiFhvn2rmK75kHB xOv1xdjfUc36HNy6fm24LBKpWK8fxljlPGs8w=
Received: by 10.142.136.16 with SMTP id j16mr3327171wfd.27.1234925149243; Tue, 17 Feb 2009 18:45:49 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 30sm17409252wff.47.2009.02.17.18.45.47 (version=SSLv3 cipher=RC4-MD5); Tue, 17 Feb 2009 18:45:48 -0800 (PST)
Message-ID: <499B7659.7080604@gmail.com>
Date: Wed, 18 Feb 2009 15:45:45 +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: "David W. Hankins" <David_Hankins@isc.org>
References: <20090217230232.GF16400@isc.org>
In-Reply-To: <20090217230232.GF16400@isc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org
Subject: Re: [Softwires] Softwires configuration via DHCP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 02:45:38 -0000

David,

On 2009-02-18 12:02, David W. Hankins wrote:
...
> 2) That only a single endpoint is sensible.  That there wouldn't be
>    a configuration where a client had multiple Softwire endpoints
>    configured at once (migrated from one to another, but never
>    straddling two or more at once).

Wouldn't you want a short overlap to allow seamless migration
of application sessions? Break-before-make is not good for
real time streams or for any kind of QOS assurance.

   Brian

From David_Hankins@isc.org  Tue Feb 17 20:20:13 2009
Return-Path: <David_Hankins@isc.org>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 817E13A6A67 for <softwires@core3.amsl.com>; Tue, 17 Feb 2009 20:20:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vll1Ol1-tjBY for <softwires@core3.amsl.com>; Tue, 17 Feb 2009 20:20:12 -0800 (PST)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 884603A6A1A for <softwires@ietf.org>; Tue, 17 Feb 2009 20:20:12 -0800 (PST)
Received: from david.isc.org (c-67-161-51-194.hsd1.ca.comcast.net [67.161.51.194]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id n1I4KLKF002054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <softwires@ietf.org>; Tue, 17 Feb 2009 20:20:23 -0800
Received: by david.isc.org (Postfix, from userid 10200) id 7124616E1B3; Tue, 17 Feb 2009 20:20:19 -0800 (PST)
Date: Tue, 17 Feb 2009 20:20:19 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: softwires@ietf.org
Message-ID: <20090218042016.GA5061@isc.org>
References: <20090217230232.GF16400@isc.org> <499B7659.7080604@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua"
Content-Disposition: inline
In-Reply-To: <499B7659.7080604@gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: Re: [Softwires] Softwires configuration via DHCP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 04:20:13 -0000

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

On Wed, Feb 18, 2009 at 03:45:45PM +1300, Brian E Carpenter wrote:
> Wouldn't you want a short overlap to allow seamless migration
> of application sessions? Break-before-make is not good for
> real time streams or for any kind of QOS assurance.

I think two Softwires endpoints will cover different IPv4 address
ranges on the 'external' side of the CGN.  So even make-before-break
would not provide what you are looking for?

--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFJm4yAcXeLeWu2vmoRAnOrAJ47SpL+2F8hKABEFAi7F5TH86oZ4wCgha1E
oiApqjm1kTCr0FXNHo3kXd0=
=5b6K
-----END PGP SIGNATURE-----

--SUOF0GtieIMvvwua--

From brian.e.carpenter@gmail.com  Wed Feb 18 14:04:49 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A79CE3A67AD for <softwires@core3.amsl.com>; Wed, 18 Feb 2009 14:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D0zzhQEqNd05 for <softwires@core3.amsl.com>; Wed, 18 Feb 2009 14:04:48 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by core3.amsl.com (Postfix) with ESMTP id C46DD3A68D8 for <softwires@ietf.org>; Wed, 18 Feb 2009 14:04:19 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id l9so97446rvb.49 for <softwires@ietf.org>; Wed, 18 Feb 2009 14:04:32 -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=OzQHEOe2TxsZRipAxvNhf+PuRQ9wsyHhYkM4dbY6OcA=; b=AfBPGofH+hns2v/pXfad24rNwQ0tPC8N/isdHm1/t6GdLRpuvWb/GjrZRi7rWlI6Yy oF5O2+bg4BHdPy3FkprkTFkeBbMBGfPxqhbVHn1abUg8hMRWvG+RfwHibxsxAiX5bP7q SHMR3GekZxPMf8Iu7QuIgXW2Ve0w9JeLbTZJU=
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=L5SlAz8DzeLjMxzyXU4/lkA7R0ZP5YLMnJ7kz7+ExkUJzn0lAB2qSbmbdccSqXpfnD 237OGNXl6DPwblNSt61pobAV57tlz/2Np/WVd8b/RDyPBogeiDIPVYiJikjSqkvsXw2V 0YZr5gZfx6xi6FhHlR96N8GytB60ycv3ILLmU=
Received: by 10.141.84.21 with SMTP id m21mr4171164rvl.118.1234994672185; Wed, 18 Feb 2009 14:04:32 -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 l31sm756977rvb.5.2009.02.18.14.04.30 (version=SSLv3 cipher=RC4-MD5); Wed, 18 Feb 2009 14:04:31 -0800 (PST)
Message-ID: <499C85EC.7080809@gmail.com>
Date: Thu, 19 Feb 2009 11:04: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: "David W. Hankins" <David_Hankins@isc.org>
References: <20090217230232.GF16400@isc.org> <499B7659.7080604@gmail.com> <20090218042016.GA5061@isc.org>
In-Reply-To: <20090218042016.GA5061@isc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org
Subject: Re: [Softwires] Softwires configuration via DHCP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 22:04:49 -0000

On 2009-02-18 17:20, David W. Hankins wrote:
> On Wed, Feb 18, 2009 at 03:45:45PM +1300, Brian E Carpenter wrote:
>> Wouldn't you want a short overlap to allow seamless migration
>> of application sessions? Break-before-make is not good for
>> real time streams or for any kind of QOS assurance.
> 
> I think two Softwires endpoints will cover different IPv4 address
> ranges on the 'external' side of the CGN.  So even make-before-break
> would not provide what you are looking for?

Actually, wouldn't it allow a clever NAT to update session state
automatically? In any case, we can't be sure that this is the only
usage scenario for ever.

   Brian

From David_Hankins@isc.org  Wed Feb 18 14:27:48 2009
Return-Path: <David_Hankins@isc.org>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DB743A67F0 for <softwires@core3.amsl.com>; Wed, 18 Feb 2009 14:27:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6gsCnYifIxMS for <softwires@core3.amsl.com>; Wed, 18 Feb 2009 14:27:48 -0800 (PST)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 024F43A676A for <softwires@ietf.org>; Wed, 18 Feb 2009 14:27:47 -0800 (PST)
Received: from david.isc.org (c-67-161-51-194.hsd1.ca.comcast.net [67.161.51.194]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id n1IMRxGQ016771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <softwires@ietf.org>; Wed, 18 Feb 2009 14:27:59 -0800
Received: by david.isc.org (Postfix, from userid 10200) id CF68316E1B3; Wed, 18 Feb 2009 14:27:58 -0800 (PST)
Date: Wed, 18 Feb 2009 14:27:58 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: softwires@ietf.org
Message-ID: <20090218222757.GE4262@isc.org>
References: <20090217230232.GF16400@isc.org> <499B7659.7080604@gmail.com> <20090218042016.GA5061@isc.org> <499C85EC.7080809@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7CZp05NP8/gJM8Cl"
Content-Disposition: inline
In-Reply-To: <499C85EC.7080809@gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: Re: [Softwires] Softwires configuration via DHCP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 22:27:48 -0000

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

First, thank you Brian for responding and thinking about this, I do
appreciate it.  My writing style is sometimes dry.

On Thu, Feb 19, 2009 at 11:04:28AM +1300, Brian E Carpenter wrote:
> Actually, wouldn't it allow a clever NAT to update session state
> automatically?

If you were to have two nodes sharing NAT mapping state, why would you
prefer to wait for DHCP renewal timers rather than to have the
surviving CGN simply take over routing for its peer's /128?  This is
the area of solutions I mean when I say I would expect 'tunnels' to
be handled by routing equipment, and solved with classic routing
solutions.

Surely by the time you are coordinating such NAT tables, the idea of
coordinating the use of /128s (fallbacks, anycasts) is trivial, and
preferrable to placing complications on the softwire-client end?

--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--7CZp05NP8/gJM8Cl
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFJnIttcXeLeWu2vmoRAsGhAKCpX3bzeZ+l52n4AjWJYSeJc8IwbQCdGlZl
SdTH0UTJ5XxJsjGPoLATZ1U=
=sEvh
-----END PGP SIGNATURE-----

--7CZp05NP8/gJM8Cl--

From brian.e.carpenter@gmail.com  Wed Feb 18 16:22:08 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C78AE28C198 for <softwires@core3.amsl.com>; Wed, 18 Feb 2009 16:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 q+pzduDHC7Q2 for <softwires@core3.amsl.com>; Wed, 18 Feb 2009 16:22:08 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by core3.amsl.com (Postfix) with ESMTP id 1C77D3A67EF for <softwires@ietf.org>; Wed, 18 Feb 2009 16:22:08 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id l9so143455rvb.49 for <softwires@ietf.org>; Wed, 18 Feb 2009 16:22:20 -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=yYjKXMgJpZ3wWRJfxLpLg7Crb/sYfS9ZrSPJsKrP8Go=; b=BgK446qiCvlxbWJcFFbwFmp34Df3/JDl1yRL4yIkHAXjYw1enjZ1O5421MM/4DWqCC lJnMLrt/1C6V0WaPAa2q5Q70Kw+V94RWhLaRj4nV3oOFI7B+K9c2C8HObHjZmB4+YC8V MmtZjmn+5ARAS9RgJZFQ+1fXWOqXpQ1esCTMo=
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=E0rqxHSi8lJjJ0XvHU5NjuFYqtiF+OCSZeCPUfLRXK9qgIiZwLyeraB0DhtM9u64RX h/1La6SaTES2cVv/KznsV3aCxyvTm/HGCcI0FxsGZwQKCYU4HSeM5irbIalK4Y8TLWFn w/0OVareZjoqGiBMAUDR35bYNlv4uynJDPuvU=
Received: by 10.141.20.7 with SMTP id x7mr4242681rvi.14.1235002940380; Wed, 18 Feb 2009 16:22:20 -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 k2sm1042792rvb.4.2009.02.18.16.22.18 (version=SSLv3 cipher=RC4-MD5); Wed, 18 Feb 2009 16:22:20 -0800 (PST)
Message-ID: <499CA641.1000402@gmail.com>
Date: Thu, 19 Feb 2009 13:22:25 +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: "David W. Hankins" <David_Hankins@isc.org>
References: <20090217230232.GF16400@isc.org> <499B7659.7080604@gmail.com>	<20090218042016.GA5061@isc.org> <499C85EC.7080809@gmail.com> <20090218222757.GE4262@isc.org>
In-Reply-To: <20090218222757.GE4262@isc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org
Subject: Re: [Softwires] Softwires configuration via DHCP
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2009 00:22:08 -0000

David,


On 2009-02-19 11:27, David W. Hankins wrote:
> First, thank you Brian for responding and thinking about this, I do
> appreciate it.  My writing style is sometimes dry.

This is the IETF, isn't it? ;-) Dry is fine...

> On Thu, Feb 19, 2009 at 11:04:28AM +1300, Brian E Carpenter wrote:
>> Actually, wouldn't it allow a clever NAT to update session state
>> automatically?
> 
> If you were to have two nodes sharing NAT mapping state, why would you
> prefer to wait for DHCP renewal timers rather than to have the
> surviving CGN simply take over routing for its peer's /128?  This is
> the area of solutions I mean when I say I would expect 'tunnels' to
> be handled by routing equipment, and solved with classic routing
> solutions.
> 
> Surely by the time you are coordinating such NAT tables, the idea of
> coordinating the use of /128s (fallbacks, anycasts) is trivial, and
> preferrable to placing complications on the softwire-client end?

I won't argue with you for the currently envisaged scenarios. I've
been looking at things with slightly different eyes while working
on draft-carpenter-renum-needs-work, because there seem to be quite
a lot of existing mechanisms that could be repurposed to support
dynamic renumbering, and there make-before-break has benefits.

    Brian
