
From pierre.levis@orange-ftgroup.com  Thu Jun  4 00:57:01 2009
Return-Path: <pierre.levis@orange-ftgroup.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 89CAA28C1E2 for <softwires@core3.amsl.com>; Thu,  4 Jun 2009 00:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGLuotbUwM4m for <softwires@core3.amsl.com>; Thu,  4 Jun 2009 00:56:54 -0700 (PDT)
Received: from R-MAIL2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 187B63A6904 for <softwires@ietf.org>; Thu,  4 Jun 2009 00:56:53 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Jun 2009 09:56:54 +0200
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
Date: Thu, 4 Jun 2009 09:56:53 +0200
Message-ID: <F1A741D65FFEF6489D607B26ABA0ED573E108D@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: TR: I-D Action:draft-boucadair-dslite-interco-v4v6-01.txt 
Thread-Index: AcnX0hOVUev8rcjuTZK83Itnc/23nANFh28gAAAMqBAAAGM3YA==
From: <pierre.levis@orange-ftgroup.com>
To: <softwires@ietf.org>
X-OriginalArrivalTime: 04 Jun 2009 07:56:54.0598 (UTC) FILETIME=[06E5E660:01C9E4EA]
Cc: mohamed.kassilahlou@orange-ftgroup.com, jeanluc.grimault@orange-ftgroup.com
Subject: [Softwires] TR: I-D Action:draft-boucadair-dslite-interco-v4v6-01.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, 04 Jun 2009 07:57:01 -0000

 Dear all,

We have submitted the following draft

Comments are very welcome


Pierre

-----Message d'origine-----
De : i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org] De la part de =
Internet-Drafts@ietf.org
Envoy=E9 : lundi 18 mai 2009 18:00
=C0 : i-d-announce@ietf.org
Objet : I-D Action:draft-boucadair-dslite-interco-v4v6-01.txt=20

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

	Title           : Stateless IPv4-IPv6 Interconnection in the Context of =
DS-lite Deployment
	Author(s)       : M. Boucadair, et al.
	Filename        : draft-boucadair-dslite-interco-v4v6-01.txt
	Pages           : 15
	Date            : 2009-05-18

This memo describes a proposal to enhance DS-lite solution with an =
additional feature to ease interconnection between IPv4 and IPv6 realms. =
 When deployed, no dual-stack-enabled network is required for the =
delivery of both IPv4 and IPv6 connectivity to customers.  Only
IPv6 is required to be deployed in core and access networks.
Particularly, IPv6 transfer capabilities are used for the transfer of =
IPv4-addressed packets in a completely stateless scheme between the =
interconnection segment and the DS-lite CGN node(s).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-boucadair-dslite-interco-v4v6-0=
1.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.

From rfc-editor@rfc-editor.org  Tue Jun  9 17:00:59 2009
Return-Path: <rfc-editor@rfc-editor.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 4F86328C123; Tue,  9 Jun 2009 17:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.01
X-Spam-Level: 
X-Spam-Status: No, score=-17.01 tagged_above=-999 required=5 tests=[AWL=-0.011, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRqqMpQPfyKv; Tue,  9 Jun 2009 17:00:58 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 83CA528C124; Tue,  9 Jun 2009 17:00:58 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 865A52C791E; Tue,  9 Jun 2009 17:00:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090610000014.865A52C791E@bosco.isi.edu>
Date: Tue,  9 Jun 2009 17:00:14 -0700 (PDT)
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 5565 on Softwire Mesh Framework
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, 10 Jun 2009 00:00:59 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5565

        Title:      Softwire Mesh Framework 
        Author:     J. Wu, Y. Cui,
                    C. Metz, E. Rosen
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    jianping@cernet.edu.cn, 
                    yong@csnet1.cs.tsinghua.edu.cn, 
                    chmetz@cisco.com, erosen@cisco.com
        Pages:      31
        Characters: 75039
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-mesh-framework-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5565.txt

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.  [STANDARDS TRACK]

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor@rfc-editor.org  Tue Jun  9 17:01:11 2009
Return-Path: <rfc-editor@rfc-editor.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 5F56B28C103; Tue,  9 Jun 2009 17:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.01
X-Spam-Level: 
X-Spam-Status: No, score=-17.01 tagged_above=-999 required=5 tests=[AWL=-0.011, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oups7ZqlOoWg; Tue,  9 Jun 2009 17:01:10 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id A520728C153; Tue,  9 Jun 2009 17:01:10 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 595A82C7920; Tue,  9 Jun 2009 17:00:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090610000032.595A82C7920@bosco.isi.edu>
Date: Tue,  9 Jun 2009 17:00:32 -0700 (PDT)
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 5566 on BGP IPsec Tunnel Encapsulation Attribute
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, 10 Jun 2009 00:01:11 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5566

        Title:      BGP IPsec Tunnel Encapsulation Attribute 
        Author:     L. Berger, R. White,
                    E. Rosen
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    lberger@labn.net, 
                    riw@cisco.com, 
                    erosen@cisco.com
        Pages:      8
        Characters: 17416
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-encaps-ipsec-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5566.txt

The BGP Encapsulation Subsequent Address Family Identifier (SAFI)
provides a method for the dynamic exchange of encapsulation
information and for the indication of encapsulation protocol types to be
used for different next hops.  Currently, support for Generic Routing
Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TPv3), and
IP in IP tunnel types are defined.  This document defines support for
IPsec tunnel types.  [STANDARDS TRACK]

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From root@core3.amsl.com  Thu Jun 11 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 8E39E28C150; Thu, 11 Jun 2009 19:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090612021501.8E39E28C150@core3.amsl.com>
Date: Thu, 11 Jun 2009 19:15:01 -0700 (PDT)
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action:draft-ietf-softwire-security-requirements-09.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: Fri, 12 Jun 2009 02: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 Security Analysis and Requirements
	Author(s)       : S. Yamamoto, et al.
	Filename        : draft-ietf-softwire-security-requirements-09.txt
	Pages           : 28
	Date            : 2009-06-11

This document describes the security guidelines for the softwire
"Hubs and Spokes" and "Mesh" solutions.  Together with the discussion
of the softwire deployment scenarios, the vulnerability to the
security attacks is analyzed to provide the security protection
mechanism such as authentication, integrity and confidentiality to
the softwire control and data packets.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-security-requirements-09.txt

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

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

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

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


--NextPart--

From rfc-editor@rfc-editor.org  Fri Jun 12 10:57:08 2009
Return-Path: <rfc-editor@rfc-editor.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 B623E3A6A07; Fri, 12 Jun 2009 10:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.001
X-Spam-Level: 
X-Spam-Status: No, score=-17.001 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBagnSH25-Ot; Fri, 12 Jun 2009 10:57:08 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 006B83A68D8; Fri, 12 Jun 2009 10:57:08 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 3CB022CB059; Fri, 12 Jun 2009 10:56:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090612175618.3CB022CB059@bosco.isi.edu>
Date: Fri, 12 Jun 2009 10:56:18 -0700 (PDT)
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 5571 on Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)
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: Fri, 12 Jun 2009 17:57:08 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5571

        Title:      Softwire Hub and Spoke Deployment 
                    Framework with Layer Two Tunneling Protocol 
                    Version 2 (L2TPv2) 
        Author:     B. Storer, C. Pignataro,
                    Ed., M. Dos Santos,
                    B. Stevant, Ed.,
                    J. Tremblay
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    bstorer@cisco.com, 
                    cpignata@cisco.com, 
                    mariados@cisco.com,
                    bruno.stevant@telecom-bretagne.eu, 
                    jf@jftremblay.com
        Pages:      41
        Characters: 91379
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-hs-framework-l2tpv2-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5571.txt

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

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor@rfc-editor.org  Fri Jun 12 11:10:10 2009
Return-Path: <rfc-editor@rfc-editor.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 174EF3A6B46; Fri, 12 Jun 2009 11:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.001
X-Spam-Level: 
X-Spam-Status: No, score=-17.001 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pU72ioE4L5tL; Fri, 12 Jun 2009 11:10:09 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 39E233A6ACB; Fri, 12 Jun 2009 11:10:09 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 4DDD12CB06B; Fri, 12 Jun 2009 11:09:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090612180920.4DDD12CB06B@bosco.isi.edu>
Date: Fri, 12 Jun 2009 11:09:20 -0700 (PDT)
Cc: softwires@ietf.org, rfc-editor@rfc-editor.org
Subject: [Softwires] [Correction] RFC 5571 on Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)
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: Fri, 12 Jun 2009 18:10:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5571

        Title:      Softwire Hub and Spoke Deployment 
                    Framework with Layer Two Tunneling Protocol 
                    Version 2 (L2TPv2) 
        Author:     B. Storer, C. Pignataro,
                    Ed., M. Dos Santos,
                    B. Stevant, Ed.,
                    L. Toutain, J. Tremblay
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    bstorer@cisco.com, 
                    cpignata@cisco.com, 
                    mariados@cisco.com, 
                    bruno.stevant@telecom-bretagne.eu, 
                    laurent.toutain@telecom-bretagne.eu,  
                    jf@jftremblay.com
        Pages:      41
        Characters: 91379
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-hs-framework-l2tpv2-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5571.txt

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

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From bruno.stevant@telecom-bretagne.eu  Mon Jun 15 00:32:18 2009
Return-Path: <bruno.stevant@telecom-bretagne.eu>
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 436D528C10C for <softwires@core3.amsl.com>; Mon, 15 Jun 2009 00:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0IJyC5IcGQLV for <softwires@core3.amsl.com>; Mon, 15 Jun 2009 00:32:17 -0700 (PDT)
Received: from laposte.rennes.enst-bretagne.fr (laposte.rennes.enst-bretagne.fr [192.44.77.17]) by core3.amsl.com (Postfix) with ESMTP id 2A4AC28C101 for <softwires@ietf.org>; Mon, 15 Jun 2009 00:32:14 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with ESMTP id n5F7WJdT013039 for <softwires@ietf.org>; Mon, 15 Jun 2009 09:32:19 +0200
Received: from l2.rennes.enst-bretagne.fr (l2.rennes.enst-bretagne.fr [192.44.77.4]) by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2008.01.11) with ESMTP id n5F7WCcT013017 for <softwires@ietf.org>; Mon, 15 Jun 2009 09:32:16 +0200
Received: from [IPv6:2001:660:7301:3728:216:cbff:fecf:bc8d] ([IPv6:2001:660:7301:3728:216:cbff:fecf:bc8d]) (authenticated bits=0) by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id n5F7WBZY018969 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <softwires@ietf.org>; Mon, 15 Jun 2009 09:32:12 +0200
Message-Id: <1CDA65DD-780B-4124-AACA-1F9A99F3624B@telecom-bretagne.eu>
From: Bruno STEVANT <bruno.stevant@telecom-bretagne.eu>
To: softwires@ietf.org
In-Reply-To: <20090612180920.4DDD12CB06B@bosco.isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 15 Jun 2009 09:32:10 +0200
References: <20090612180920.4DDD12CB06B@bosco.isi.edu>
X-Mailer: Apple Mail (2.935.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Mailman-Approved-At: Mon, 15 Jun 2009 11:02:59 -0700
Subject: Re: [Softwires] [Correction] RFC 5571 on Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)
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, 15 Jun 2009 07:32:18 -0000

Dear all,

Thanks for everyone who contribute to this document, it was a long way =20=

to push it out of the door :)
May I remind you we say at the very beginning of the document that =20
this is a "Phase 1" protocol ... what about "Phase 2" now ?!

Regards,
--=20
Bruno STEVANT - TELECOM Bretagne

Le 12 juin 09 =E0 20:09, rfc-editor@rfc-editor.org a =E9crit :

>
> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 5571
>
>        Title:      Softwire Hub and Spoke Deployment
>                    Framework with Layer Two Tunneling Protocol
>                    Version 2 (L2TPv2)
>        Author:     B. Storer, C. Pignataro,
>                    Ed., M. Dos Santos,
>                    B. Stevant, Ed.,
>                    L. Toutain, J. Tremblay
>        Status:     Standards Track
>        Date:       June 2009
>        Mailbox:    bstorer@cisco.com,
>                    cpignata@cisco.com,
>                    mariados@cisco.com,
>                    bruno.stevant@telecom-bretagne.eu,
>                    laurent.toutain@telecom-bretagne.eu,
>                    jf@jftremblay.com
>        Pages:      41
>        Characters: 91379
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-ietf-softwire-hs-framework-l2tpv2-13.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc5571.txt
>
> This document describes the framework of the Softwire "Hub and Spoke"
> solution with the Layer Two Tunneling Protocol version 2 (L2TPv2).
> The implementation details specified in this document should be
> followed to achieve interoperability among different vendor
> implementations.  [STANDARDS TRACK]
>
> This document is a product of the Softwires Working Group of the IETF.
>
> This is now a Proposed Standard Protocol.
>
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and =20
> suggestions
> for improvements.  Please refer to the current edition of the Internet
> Official Protocol Standards (STD 1) for the standardization state and
> status of this protocol.  Distribution of this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see =
http://www.rfc-editor.org/rfcsearch.html=20
> .
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  =20
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> USC/Information Sciences Institute
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires






From wwwrun@core3.amsl.com  Fri Jun 19 16:12:29 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 E07493A6A4E; Fri, 19 Jun 2009 16:12:29 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090619231229.E07493A6A4E@core3.amsl.com>
Date: Fri, 19 Jun 2009 16:12:29 -0700 (PDT)
Cc: softwires@ietf.org
Subject: [Softwires] Last Call: draft-ietf-softwire-lb (Load Balancing for Mesh Softwires) 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: Fri, 19 Jun 2009 23:12:30 -0000

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

- 'Load Balancing for Mesh Softwires '
   <draft-ietf-softwire-lb-03.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-07-03. 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-lb-03.txt


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


From alain_durand@cable.comcast.com  Sat Jun 20 06:19:06 2009
Return-Path: <alain_durand@cable.comcast.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 9EAE028C144 for <softwires@core3.amsl.com>; Sat, 20 Jun 2009 06:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level: 
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[AWL=-3.934, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EK0X6p7-5naS for <softwires@core3.amsl.com>; Sat, 20 Jun 2009 06:19:05 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id C304128C13E for <softwires@ietf.org>; Sat, 20 Jun 2009 06:18:39 -0700 (PDT)
Received: from ([10.195.246.152]) by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.63860366; Sat, 20 Jun 2009 09:18:29 -0400
Received: from PACORPEXCMB04.cable.comcast.com ([24.40.15.117]) by NJMDCEXCRLY01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 20 Jun 2009 09:18:29 -0400
Received: from 10.17.2.53 ([10.17.2.53]) by PACORPEXCMB04.cable.comcast.com ([24.40.15.117]) with Microsoft Exchange Server HTTP-DAV ;  Sat, 20 Jun 2009 13:18:19 +0000
User-Agent: Microsoft-Entourage/12.19.0.090515
Date: Sat, 20 Jun 2009 09:18:18 -0400
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: <softwires@ietf.org>
Message-ID: <C66259DA.1F114%Alain_Durand@cable.comcast.com>
Thread-Topic: Softwires at IETF75, call for agenda items
Thread-Index: AcnxqZNPhK0RFtDIt0C0EFpLe3fAyA==
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3328334298_2582764"
X-OriginalArrivalTime: 20 Jun 2009 13:18:29.0094 (UTC) FILETIME=[99EC5860:01C9F1A9]
Subject: [Softwires] Softwires at IETF75, call for agenda items
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: Sat, 20 Jun 2009 13:19:06 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3328334298_2582764
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

The draft agenda of IETF75 is available at: The Draft agenda is now
available at:
http://www.ietf.org/meetings/75/

As of today, we are scheduled on Tuesday pm.

Please send your agenda item request to me and David ASAP.

  - Alain.

--B_3328334298_2582764
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Softwires at IETF75, call for agenda items</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>The draft agenda of IETF75 is available at: The Draft agenda is now availa=
ble at:<BR>
<FONT COLOR=3D"#0000FF"><U><a href=3D"http://www.ietf.org/meetings/75/">http://=
www.ietf.org/meetings/75/</a><BR>
</U></FONT><BR>
As of today, we are scheduled on Tuesday pm. <BR>
<BR>
Please send your agenda item request to me and David ASAP.<BR>
<BR>
&nbsp;&nbsp;- Alain.</SPAN></FONT>
</BODY>
</HTML>


--B_3328334298_2582764--


From pierre.levis@orange-ftgroup.com  Mon Jun 22 06:43:03 2009
Return-Path: <pierre.levis@orange-ftgroup.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 E4C6E3A69CA; Mon, 22 Jun 2009 06:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzbohoJadzIy; Mon, 22 Jun 2009 06:43:03 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 5F53C3A6933; Mon, 22 Jun 2009 06:43:02 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Jun 2009 15:43:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C9F33F.645995C3"
Date: Mon, 22 Jun 2009 15:43:14 +0200
Message-ID: <F1A741D65FFEF6489D607B26ABA0ED575BDA17@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-levis-behave-ipv4-shortage-framework-02.txt 
Thread-Index: AcnzPbcB+4wzZZXCRhqFxwRGprq7DgAAHZXA
From: <pierre.levis@orange-ftgroup.com>
To: <behave@ietf.org>, <shara@ietf.org>, <softwires@ietf.org>
X-OriginalArrivalTime: 22 Jun 2009 13:43:15.0723 (UTC) FILETIME=[64D96DB0:01C9F33F]
Cc: alain.villefranque@orange-ftgroup.com, jeanluc.grimault@orange-ftgroup.com
Subject: [Softwires] TR: I-D Action:draft-levis-behave-ipv4-shortage-framework-02.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, 22 Jun 2009 13:43:04 -0000

This is a multi-part message in MIME format.

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

Dear all,

This new version is significantly richer than the previous one.


Looking forward to reading your comments


Regards


Pierre


-----Message d'origine-----
De : i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org] De la part de =
Internet-Drafts@ietf.org
Envoy=E9 : lundi 22 juin 2009 15:30
=C0 : i-d-announce@ietf.org
Objet : I-D Action:draft-levis-behave-ipv4-shortage-framework-02.txt=20

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

	Title           : IPv4 Address Shortage: Needs and Open Issues
	Author(s)       : P. Levis, et al.
	Filename        : draft-levis-behave-ipv4-shortage-framework-02.txt
	Pages           : 25
	Date            : 2009-06-22

This document analyses the main issues related to IPv4 Internet
access in the context of public IPv4 address exhaustion.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-levis-behave-ipv4-shortage-fram=
ework-02.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_001_01C9F33F.645995C3
Content-Type: application/octet-stream;
	name="draft-levis-behave-ipv4-shortage-framework-02.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-levis-behave-ipv4-shortage-framework-02.URL
Content-Disposition: attachment;
	filename="draft-levis-behave-ipv4-shortage-framework-02.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1sZXZpcy1iZWhhdmUtaXB2NC1zaG9ydGFnZS1mcmFtZXdvcmstMDIudHh0DQo=

------_=_NextPart_001_01C9F33F.645995C3
Content-Type: text/plain;
	name="ATT10715347.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT10715347.txt
Content-Disposition: attachment;
	filename="ATT10715347.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCkludGVybmV0LURyYWZ0IGRpcmVj
dG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sDQpvciBmdHA6Ly9mdHAuaWV0
Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA0K

------_=_NextPart_001_01C9F33F.645995C3--

From shengjiang@huawei.com  Wed Jun 24 18:30:17 2009
Return-Path: <shengjiang@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 C4C2E28C50F for <softwires@core3.amsl.com>; Wed, 24 Jun 2009 18:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.322
X-Spam-Level: 
X-Spam-Status: No, score=-0.322 tagged_above=-999 required=5 tests=[AWL=0.173,  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 JhyIcxaevR0J for <softwires@core3.amsl.com>; Wed, 24 Jun 2009 18:30:17 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 0C4EC3A6D7C for <softwires@ietf.org>; Wed, 24 Jun 2009 18:30:17 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLR002Z1TH0XX@szxga02-in.huawei.com> for softwires@ietf.org; Thu, 25 Jun 2009 09:29:24 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLR0014STH0WN@szxga02-in.huawei.com> for softwires@ietf.org; Thu, 25 Jun 2009 09:29:24 +0800 (CST)
Received: from j66104a ([10.111.12.60]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLR00L60TGZ4H@szxml06-in.huawei.com> for softwires@ietf.org; Thu, 25 Jun 2009 09:29:24 +0800 (CST)
Date: Thu, 25 Jun 2009 09:29:23 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <C66259DA.1F114%Alain_Durand@cable.comcast.com>
To: "'Durand, Alain'" <Alain_Durand@cable.comcast.com>, softwires@ietf.org, dward@cisco.com
Message-id: <001201c9f534$5f293390$3c0c6f0a@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=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcnxqZNPhK0RFtDIt0C0EFpLe3fAyADiiREw
Cc: guoseu@huawei.com
Subject: Re: [Softwires] Softwires at IETF75, call for agenda items
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, 25 Jun 2009 01:30:17 -0000

We would like to apply a time slot to represent  a new draft
draft-guo-softwire-sc-discovery. It proposes a general softwire (tunnel)
concentrator discovery mechanisms. 

http://tools.ietf.org/html/draft-guo-softwire-sc-discovery-00

Many thanks,

Sheng

> -----Original Message-----
> From: softwires-bounces@ietf.org 
> [mailto:softwires-bounces@ietf.org] On Behalf Of Durand, Alain
> Sent: Saturday, June 20, 2009 9:18 PM
> To: softwires@ietf.org
> Subject: [Softwires] Softwires at IETF75, call for agenda items
> 
> The draft agenda of IETF75 is available at: The Draft agenda 
> is now available at:
> http://www.ietf.org/meetings/75/
> 
> As of today, we are scheduled on Tuesday pm. 
> 
> Please send your agenda item request to me and David ASAP.
> 
>   - Alain. 
> 


From shengjiang@huawei.com  Fri Jun 26 19:37:24 2009
Return-Path: <shengjiang@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 6FCAF28C1E1 for <softwires@core3.amsl.com>; Fri, 26 Jun 2009 19:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.328
X-Spam-Level: 
X-Spam-Status: No, score=-0.328 tagged_above=-999 required=5 tests=[AWL=0.167,  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 YlO-9c9-qHye for <softwires@core3.amsl.com>; Fri, 26 Jun 2009 19:37:23 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 9123A28C1DC for <softwires@ietf.org>; Fri, 26 Jun 2009 19:37:23 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLV0044PLYJ6V@szxga02-in.huawei.com> for softwires@ietf.org; Sat, 27 Jun 2009 10:37:32 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLV003P7LYJ66@szxga02-in.huawei.com> for softwires@ietf.org; Sat, 27 Jun 2009 10:37:31 +0800 (CST)
Received: from j66104a ([10.111.12.60]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLV00DQTLYJX2@szxml04-in.huawei.com> for softwires@ietf.org; Sat, 27 Jun 2009 10:37:31 +0800 (CST)
Date: Sat, 27 Jun 2009 10:37:31 +0800
From: Sheng Jiang <shengjiang@huawei.com>
To: softwires@ietf.org
Message-id: <002101c9f6d0$38519170$3c0c6f0a@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=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acn1K+rkLqLDRMQeSC2rhTrZBqAcHQBomoaw
Cc: guoseu@huawei.com
Subject: [Softwires] FW: New Version Notification for draft-guo-softwire-sc-discovery-00
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: Sat, 27 Jun 2009 02:37:24 -0000

Dear all,

A new draft draft-guo-softwire-sc-discovery has been submitted to softwire
WG. It proposes a general softwire (tunnel) concentrator discovery
mechanism. It is generic to server different kinds of tunnel/softwire
concentrator auto dsicover scenarios includes the scenario of
draft-dhankins-softwire-tunnel-option.

Please view and comments. Many thanks.
 
http://tools.ietf.org/html/draft-guo-softwire-sc-discovery-00

Best regards,

Sheng

> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
> Sent: Thursday, June 25, 2009 8:28 AM
> To: shengjiang@huawei.com
> Cc: guoseu@huawei.com
> Subject: New Version Notification for 
> draft-guo-softwire-sc-discovery-00
> 
> 
> A new version of I-D, draft-guo-softwire-sc-discovery-00.txt 
> has been successfuly submitted by Sheng Jiang and posted to 
> the IETF repository.
> 
> Filename:	 draft-guo-softwire-sc-discovery
> Revision:	 00
> Title:		 Softwire Concentrator Discovery Using DHCP
> Creation_date:	 2009-06-23
> WG ID:		 Independent Submission
> Number_of_pages: 10
> 
> Abstract:
> Several types of Carrier-Grade-NATs (CGNs) have been proposed 
> to simplify IPv4/IPv6 transition of the edge network by 
> integrating tunnels and NAT. A very common scenario is that 
> many users set up softwires (i.e. tunnels) to a softwire 
> concentrator for public or private access services. In order 
> to establish softwires successfully, a new mechanism is 
> required to enable users in the edge network to discover the 
> information of the concentrator. This document describes how 
> a host or CPE (Customer Premises Equipment) discovers the 
> remote softwire concentrator or CGN in a hub and spoke 
> network using DHCP. 
> Based on two new Softwire Concentrator or CGN Discovery DHCP 
> Options, proposed in the document, a user can obtain softwire 
> concentrator or CGN information and then set up a tunnel to 
> the softwire concentrator or CGN.
>                                                               
>                     
> 
> 
> The IETF Secretariat.
> 
> 


From thomson@klub.com.pl  Sun Jun 28 16:54:41 2009
Return-Path: <thomson@klub.com.pl>
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 0CCC128C138 for <softwires@core3.amsl.com>; Sun, 28 Jun 2009 16:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.444
X-Spam-Level: ****
X-Spam-Status: No, score=4.444 tagged_above=-999 required=5 tests=[AWL=2.909,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_PL=1.135, HELO_MISMATCH_PL=1.448, 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 sogSPX1vIeki for <softwires@core3.amsl.com>; Sun, 28 Jun 2009 16:54:39 -0700 (PDT)
Received: from v13.klub.com.pl (unknown [88.220.59.34]) by core3.amsl.com (Postfix) with ESMTP id 5868E28C0F9 for <softwires@ietf.org>; Sun, 28 Jun 2009 16:54:39 -0700 (PDT)
Received: from klub.com.pl (klub.com.pl [88.220.59.12]) by v13.klub.com.pl (Postfix) with ESMTP id 92C2047963 for <softwires@ietf.org>; Mon, 29 Jun 2009 01:55:05 +0200 (CEST)
Date: Mon, 29 Jun 2009 01:55:05 +0200 (CEST)
From: Tomasz Mrugalski <thomson@klub.com.pl>
To: softwires@ietf.org
Message-ID: <alpine.DEB.1.10.0906290050050.24543@v13.klub.com.pl>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: [Softwires] A few draft-dhankins-softwire-tunnel-option-03 comments
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Tomasz Mrugalski <tomasz.mrugalski@klub.com.pl>
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, 29 Jun 2009 00:31:50 -0000

Hi,
I've read draft-dhankins-softwire-tunnel-option-03 draft recently and have
several comments and questions:

1. Tunnel type
Can we assume that IPv4-over-IPv6 will be the only tunnel type used?
I think not. Therefore tunnel-type field should be added to the DS_LITE 
option. One octet is enough.

2. SI hints
I think it should be possible (or even recommended) that client will send 
not only OPTION_DS_LITE in ORO, but also MAY provide OPTION_DS_LITE itself 
in SOLICIT, REQUEST, RENEW, etc. messages. It should contain 
address of previously used SC address, provided as a hint to the DHCPv6 
server. Here's scenario, where this approach could be useful:

Network Operator may have more than one SC. It is reasonable to assume 
that client-to-SC assignment will not be fixed, but rather client will be 
assigned to a SC (e.g. due to load-balancing).

Using knowledge about previously used SC, Network Operator may prefer to 
assign this particular client to the same SC as before. There are several 
benefits of such assignment. In particular, if SI was reboot, some 
enc-user sessions may still be active.

3. Preference
In section 3, multihoming is mentioned. Would it be beneficial to provide 
additional field in the option called Tunnel preference? Its meaning would 
be similar to the one in DHCPv6's PREFERENCE option. In case when 
multihoming device has several softwire offers, it would use (or favor) 
the one with highest preference. The best size for this field would be 1 
octet.

4. Renewal
According to Softwire Problem Statement (RFC4925), section 1.1, softwires
are generally dynamic. Shouldn't SC address be periodically renewed? This 
would be useful for graceful failover to a different SC. There are several 
possible solutions:
a) Include current SC address in all RENEW messages, using DS_LITE_OPTION.
    (poor choice, renewal frequency depends on leased address and
    prefix T1 values)
b) use Information Refresh Time Option (RFC4242) to define how often
    DS_LITE option should be renewed.
c) add T1 (and possibly T2) to the DS_LITE option, with meaning similar to 
T1 and T2 used in IA_NA and IA_PD options.

Another issue is related to the following question: Is softwire permanent? 
Can we assume that softwire is permanent in the sense that once 
established, it will be used and is valid until SI crashes or is powered 
off? What about failover scenarios when SC malfunctions or reaches end of 
its lifecycle? Maybe it would be useful to specify lifetime? This counter 
could be reset every time DS_LITE option is renewed, exactly the same as 
addresses in IA_NA option.

Size of those fields (T1,T2, lifetime) would be standard double words and 
values expressed in seconds.

5. Softwire termination
Again, Softwire Problem Statement (RFC4925), Section 1.1 states that 
softwires may be initiated and terminated on demand. How should SI release 
its tunnel? Assuming that softwire tunnel is teared down once SI sends 
Release message is not appropriate. I think the simplest approach is the 
best: SI should include OPTION_DS_LITE in the RELEASE message. Server may 
acknowledge this by sending DS_LITE option with address set to ::. This 
could be used to notify SC that it may free its resources associated with 
tunnel for this particular SI.

6. Stateless autoconfiguration
DS_LITE on its own, without address being delegated, is useless. I think 
clarification should be added that this option may not be used in 
stateless DHCPv6 (i.e. is not allowed in INFORMATION-REQUEST message).

7. Leasequery
There's a mechanism for querying server about provided configuration 
parameters (RFC5007). Would it be useful for a server to report that 
DS_LITE option was provided to the client in question? I'm not sure if 
such details should be put in the draft or not.

I think that's it for now. That's my first post on IETF, so forgive me if 
I was pointing out the obvious or discussing topic already covered (I've 
checked list archives, but I could have missed something).

Regards,
-- 
Tomasz Mrugalski                Dibbler - a portable DHCPv6 implementation
tomasz.mrugalski@klub.com.pl    http://klub.com.pl/dhcpv6/
Gdansk University of Technology

From shengjiang@huawei.com  Mon Jun 29 02:17:53 2009
Return-Path: <shengjiang@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 590F33A6849 for <softwires@core3.amsl.com>; Mon, 29 Jun 2009 02:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.413
X-Spam-Level: 
X-Spam-Status: No, score=-1.413 tagged_above=-999 required=5 tests=[AWL=1.186,  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 DIbk6rB0DYjX for <softwires@core3.amsl.com>; Mon, 29 Jun 2009 02:17:52 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 49F843A683A for <softwires@ietf.org>; Mon, 29 Jun 2009 02:17:51 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLZ002F1TU6BW@szxga04-in.huawei.com> for softwires@ietf.org; Mon, 29 Jun 2009 17:18:06 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLZ00K28TU6UP@szxga04-in.huawei.com> for softwires@ietf.org; Mon, 29 Jun 2009 17:18:06 +0800 (CST)
Received: from j66104a ([10.111.12.60]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLZ00KWOTU32Z@szxml04-in.huawei.com> for softwires@ietf.org; Mon, 29 Jun 2009 17:18:03 +0800 (CST)
Date: Mon, 29 Jun 2009 17:18:03 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <alpine.DEB.1.10.0906290050050.24543@v13.klub.com.pl>
To: 'Tomasz Mrugalski' <tomasz.mrugalski@klub.com.pl>, softwires@ietf.org
Message-id: <002001c9f89a$816a9e30$3c0c6f0a@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=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acn4URG2GnJCBpMXQ8yoEJlLsIjsSwASNZZw
Subject: Re: [Softwires] A few draft-dhankins-softwire-tunnel-option-03 comments
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, 29 Jun 2009 09:17:53 -0000

>From the title of this draft, it only serves the dual-stack lite scenario.
For 
support generic tunnel scenarios, we have recently proposed a new draft
draft-guo-softwire-sc-discovery
http://tools.ietf.org/html/draft-guo-softwire-sc-discovery-00 
to softwire WG. It proposes a general softwire (tunnel) concentrator 
discovery mechanism. It is generic to server different kinds of
tunnel/softwire
concentrator auto discover scenarios includes the scenario of 
draft-dhankins-softwire-tunnel-option.

Regards,

Sheng

> -----Original Message-----
> From: softwires-bounces@ietf.org 
> [mailto:softwires-bounces@ietf.org] On Behalf Of Tomasz Mrugalski
> Sent: Monday, June 29, 2009 7:55 AM
> To: softwires@ietf.org
> Subject: [Softwires] A few 
> draft-dhankins-softwire-tunnel-option-03 comments
> 
> 
> Hi,
> I've read draft-dhankins-softwire-tunnel-option-03 draft 
> recently and have several comments and questions:
> 
> 1. Tunnel type
> Can we assume that IPv4-over-IPv6 will be the only tunnel type used?
> I think not. Therefore tunnel-type field should be added to 
> the DS_LITE option. One octet is enough.
> 
> 2. SI hints
> I think it should be possible (or even recommended) that 
> client will send not only OPTION_DS_LITE in ORO, but also MAY 
> provide OPTION_DS_LITE itself in SOLICIT, REQUEST, RENEW, 
> etc. messages. It should contain address of previously used 
> SC address, provided as a hint to the DHCPv6 server. Here's 
> scenario, where this approach could be useful:
> 
> Network Operator may have more than one SC. It is reasonable 
> to assume that client-to-SC assignment will not be fixed, but 
> rather client will be assigned to a SC (e.g. due to load-balancing).
> 
> Using knowledge about previously used SC, Network Operator 
> may prefer to assign this particular client to the same SC as 
> before. There are several benefits of such assignment. In 
> particular, if SI was reboot, some enc-user sessions may 
> still be active.
> 
> 3. Preference
> In section 3, multihoming is mentioned. Would it be 
> beneficial to provide additional field in the option called 
> Tunnel preference? Its meaning would be similar to the one in 
> DHCPv6's PREFERENCE option. In case when multihoming device 
> has several softwire offers, it would use (or favor) the one 
> with highest preference. The best size for this field would 
> be 1 octet.
> 
> 4. Renewal
> According to Softwire Problem Statement (RFC4925), section 
> 1.1, softwires are generally dynamic. Shouldn't SC address be 
> periodically renewed? This would be useful for graceful 
> failover to a different SC. There are several possible solutions:
> a) Include current SC address in all RENEW messages, using 
> DS_LITE_OPTION.
>     (poor choice, renewal frequency depends on leased address and
>     prefix T1 values)
> b) use Information Refresh Time Option (RFC4242) to define how often
>     DS_LITE option should be renewed.
> c) add T1 (and possibly T2) to the DS_LITE option, with 
> meaning similar to
> T1 and T2 used in IA_NA and IA_PD options.
> 
> Another issue is related to the following question: Is 
> softwire permanent? 
> Can we assume that softwire is permanent in the sense that 
> once established, it will be used and is valid until SI 
> crashes or is powered off? What about failover scenarios when 
> SC malfunctions or reaches end of its lifecycle? Maybe it 
> would be useful to specify lifetime? This counter could be 
> reset every time DS_LITE option is renewed, exactly the same 
> as addresses in IA_NA option.
> 
> Size of those fields (T1,T2, lifetime) would be standard 
> double words and values expressed in seconds.
> 
> 5. Softwire termination
> Again, Softwire Problem Statement (RFC4925), Section 1.1 
> states that softwires may be initiated and terminated on 
> demand. How should SI release its tunnel? Assuming that 
> softwire tunnel is teared down once SI sends Release message 
> is not appropriate. I think the simplest approach is the
> best: SI should include OPTION_DS_LITE in the RELEASE 
> message. Server may acknowledge this by sending DS_LITE 
> option with address set to ::. This could be used to notify 
> SC that it may free its resources associated with tunnel for 
> this particular SI.
> 
> 6. Stateless autoconfiguration
> DS_LITE on its own, without address being delegated, is 
> useless. I think clarification should be added that this 
> option may not be used in stateless DHCPv6 (i.e. is not 
> allowed in INFORMATION-REQUEST message).
> 
> 7. Leasequery
> There's a mechanism for querying server about provided 
> configuration parameters (RFC5007). Would it be useful for a 
> server to report that DS_LITE option was provided to the 
> client in question? I'm not sure if such details should be 
> put in the draft or not.
> 
> I think that's it for now. That's my first post on IETF, so 
> forgive me if I was pointing out the obvious or discussing 
> topic already covered (I've checked list archives, but I 
> could have missed something).
> 
> Regards,
> -- 
> Tomasz Mrugalski                Dibbler - a portable DHCPv6 
> implementation
> tomasz.mrugalski@klub.com.pl    http://klub.com.pl/dhcpv6/
> Gdansk University of Technology
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires


From wwwrun@core3.amsl.com  Mon Jun 29 09:28:41 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 9EF0B28C27B; Mon, 29 Jun 2009 09:28:41 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20090629162841.9EF0B28C27B@core3.amsl.com>
Date: Mon, 29 Jun 2009 09:28:41 -0700 (PDT)
Cc: softwire mailing list <softwires@ietf.org>, Internet Architecture Board <iab@iab.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Softwires] Protocol Action: 'Softwire Security Analysis and Requirements' to Proposed Standard
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, 29 Jun 2009 16:28:41 -0000

The IESG has approved the following document:

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

This document is the product of the Softwires Working Group. 

The IESG contact persons are Ralph Droms and Jari Arkko.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-security-requirements-09.txt

Technical Summary

This document describes the security guidelines for the softwire
"Hubs and Spokes" and "Mesh" solutions. Together with the discussion of
the softwire deployment scenarios, the vulnerability to the security
attacks is analyzed to provide the security protection mechanism such as
authentication, integrity and confidentiality to the softwire
control and data packets.

Working Group Summary

The SOFTWIRE WG supports the development and advancement of this
document.

Protocol Quality

This document was thoroughly reviewed by WG chairs and WG members,
including those with expertise in security, IPv4 to IPv6
transitions and interworking.

