New Non-WG Mailing List: openv6

IETF Secretariat <> Thu, 16 January 2014 20:50 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 1DEB81ACCF5 for <>; Thu, 16 Jan 2014 12:50:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XhkVGDXVZme6; Thu, 16 Jan 2014 12:50:57 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id B167A1A16F0; Thu, 16 Jan 2014 12:50:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <>
To: IETF Announcement List <>
Subject: New Non-WG Mailing List: openv6
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 16 Jan 2014 12:50:57 -0800
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 Jan 2014 20:50:59 -0000

A new IETF non-working group email list has been created.

List address:
To subscribe:


This list is to discuss a open interface and a programmable platform to support various IPv6 applications, which may include IPv6 transition technologies, SAVI (Source Address Validation and Traceback), security, data center and etc. This discussion will focus on the problem space, use case and possible protocol extensions. The following questions are listed to be solved via this discussion:
(1) What are the problems and use cases existing in various IPv6 applications, 
e.g., multiple IPv6 transition technologies co-exist?
(2) How to enable the applications to program the equipment to tunnel IPv6 
traffic across an IPv4 data plane? 

(3) How this work can be done through a general interface, e.g., to incorporate 
the transition policies, simplifying the different stages through the transition 
and guaranteeing that current decisions do not imply a complicated legacy in 
the future? 

(4) How to make the end-to-end configuration of devices: concentrator/CGN, 
CPE and the provisioning system? 

(5) How to extend the existing IETF protocols, e.g., netconf, to support this 
open interface?

For additional information, please contact the list administrators.