Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-6204bis-12

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    v6ops mailing list <v6ops@ietf.org>,
    v6ops chair <v6ops-chairs@tools.ietf.org>
Subject: Document Action: 'Basic Requirements for IPv6 Customer Edge Routers' to Informational RFC (draft-ietf-v6ops-6204bis-12.txt)

The IESG has approved the following document:
- 'Basic Requirements for IPv6 Customer Edge Routers'
  (draft-ietf-v6ops-6204bis-12.txt) as Informational RFC

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-v6ops-6204bis/


Technical Summary

This document specifies requirements for an IPv6 Customer Edge (CE) router.  Specifically, the current version of this document focuses on the basic provisioning of an IPv6 CE router and the provisioning of IPv6 hosts attached to it.

Working Group Summary

The Bis document follows quickly on the heals of the original RFC 6204 (published April 2011). This speaks both to the rapid ferment associated with transition technologies and their deployment in CPE devices as well as the impact that operational experience is now having on recommendations. Clearly in this case, perfection is the enemy of the good, and timely publication will likely result in issues that need to be revisited or resolved in future documents. The input of the design team was thoroughly discussed on the mailing list resulting in Draft 08 which passed working group last call, with draft 09 addressing issues with 6rd requirements found during and immediately after WGLC. A subsequent and shorter last call was confirmed on tuesday 5/22/2012.

There is ongoing discussion around requirements related to setting MSS MTU requirements for transition technologies. Consensus in this area to the extent that it exists is still evolving. Additional work in the form of a draft or drafts may be required and several have already been proposed.

Document Quality

The document shepherd believes that the document is generally well written. Significant experience with RFC 6204 by implementers and operators resulted in the document that we see here. The Advice provided here is by no-means comprehensive, but with implementers using these guidelines a common expectation for CPE functionality inclusive of transition technologies is seems plausible.

Personnel

The document shepherd is Joel Jaeggli v6ops co-chair. The responsible area-director is Ron Bonica.


RFC Editor Note

Please remove unused references to RFCs 2030 and 3704