Protocol Action: 'DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients' to Proposed Standard (draft-ietf-softwire-map-dhcp-12.txt)
The IESG <iesg-secretary@ietf.org> Mon, 09 March 2015 17:25 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEDD21A90C6; Mon, 9 Mar 2015 10:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level:
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ioZhiei6B44V; Mon, 9 Mar 2015 10:25:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1051A90D5; Mon, 9 Mar 2015 10:25:07 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients' to Proposed Standard (draft-ietf-softwire-map-dhcp-12.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150309172507.8146.57500.idtracker@ietfa.amsl.com>
Date: Mon, 09 Mar 2015 10:25:07 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/68Fw9jBzGjAFuP1RjRDbVvlrzT4>
Cc: softwire mailing list <softwires@ietf.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2015 17:25:15 -0000
The IESG has approved the following document: - 'DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients' (draft-ietf-softwire-map-dhcp-12.txt) as Proposed Standard This document is the product of the Softwires Working Group. The IESG contact persons are Brian Haberman and Ted Lemon. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-softwire-map-dhcp/ Technical Summary This document specifies DHCPv6 options, termed Softwire46 options, for the provisioning of Softwire46 Customer Edge (CE) devices. Softwire46 is a collective term used to refer to architectures based on the notion of IPv4 Address+Port (A+P) for providing IPv4 connectivity across an IPv6 network. Working Group Summary The working group had active discussion on the draft and the current text of the draft is representative of the consensus of the working group. This document was a result of merging DHCPv6 options required for several softwire solutions into a single document and rationalizing them after consolidating similar options and removing duplicates. Document Quality There is an open source implementation of these options in the recently released OpenWRT software (the BARRIER BREAKER release). There are also available implementations of the mechanism specific options that got merged into this draft. Personnel Suresh Krishnan is the document shepherd. Ted Lemon is the responsible AD. RFC Editor Note This document makes frequent use of the term "sub-option", which is incorrect according to RFC 7227, section 9. The correct term is "encapsulated option." Please double-check that all such uses are corrected. Thanks! This document is one of a set of five softwire documents that should be published with sequential RFC numbers. The numbering should be in the following order: draft-ietf-softwire-lw4over6 draft-ietf-softwire-map draft-ietf-softwire-map-dhcp draft-ietf-softwire-map-t draft-ietf-softwire-4rd