[v6ops] transition-ipv4aas: Usage Scenarios and End-User Network Architecture

"STARK, BARBARA H" <bs7652@att.com> Wed, 25 April 2018 19:00 UTC

Return-Path: <bs7652@att.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4CE12E042 for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 12:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 T0Nf3Rwl7Z5E for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 12:00:05 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3EA12AAB6 for <v6ops@ietf.org>; Wed, 25 Apr 2018 12:00:04 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id w3PItW5N038506 for <v6ops@ietf.org>; Wed, 25 Apr 2018 15:00:04 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 2hjy7f0cm4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <v6ops@ietf.org>; Wed, 25 Apr 2018 15:00:04 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w3PJ03Uk022583 for <v6ops@ietf.org>; Wed, 25 Apr 2018 15:00:03 -0400
Received: from zlp30485.vci.att.com (zlp30485.vci.att.com [135.47.91.178]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w3PIxwf0020091 for <v6ops@ietf.org>; Wed, 25 Apr 2018 14:59:58 -0400
Received: from zlp30485.vci.att.com (zlp30485.vci.att.com [127.0.0.1]) by zlp30485.vci.att.com (Service) with ESMTP id 394CC40002CB for <v6ops@ietf.org>; Wed, 25 Apr 2018 18:59:58 +0000 (GMT)
Received: from GAALPA1MSGHUBAC.ITServices.sbc.com (unknown [130.8.218.152]) by zlp30485.vci.att.com (Service) with ESMTPS id 280AC40006C3 for <v6ops@ietf.org>; Wed, 25 Apr 2018 18:59:58 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.170]) by GAALPA1MSGHUBAC.ITServices.sbc.com ([130.8.218.152]) with mapi id 14.03.0361.001; Wed, 25 Apr 2018 14:59:57 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: V6 Ops List <v6ops@ietf.org>
Thread-Topic: transition-ipv4aas: Usage Scenarios and End-User Network Architecture
Thread-Index: AdPcwTiQrayDwDMmSFaI+HlFJzRQDw==
Date: Wed, 25 Apr 2018 18:59:56 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DD80E20@GAALPA1MSGUSRBF.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.61.166.63]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-04-25_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=1 spamscore=0 clxscore=1015 lowpriorityscore=1 mlxscore=0 impostorscore=0 mlxlogscore=916 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1804250172
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Rzynr_06zgYfCjlwOc5BMLskJkM>
Subject: [v6ops] transition-ipv4aas: Usage Scenarios and End-User Network Architecture
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2018 19:00:07 -0000

My next set of comments for the transition-ipv4aas draft is on the Usage Scenarios and End-User Network Architecture sections.

I admit to having a low tolerance for what I consider unnecessary introductory material. If the goal is to get CE router vendors to implement the requirements in Section 5, and make this easy for operators to use this draft to request these features, then don't make readers have to go through 5 pages of largely unnecessary introductory material to get to the really important stuff. Also, the more introductory material that is included, the more comments there will be against the introductory material (and the more time gets spent in discussion of those comments -- to the detriment of discussion of requirements and making it take longer to get to publication). 

The more this draft is focused on the requirements, the more likely it is those requirements will be read and implemented, and the faster it will be to review and publish.

If you really want to include the usage scenarios, I would suggest putting them at the end. My preference would be not to include, at all (because there is no need to discuss and fix what isn't there). Same for the end-user network architecture.

I would suggest replacing these two sections with a really short section maybe titled Scope. Something like:

Scope

This document specifies the requirements for an IPv6 Transition CE Router. The IPv6 Transition CE Router builds upon the IPv6 CE Router defined and specified in [RFC7084] by including mandatory support for several transition technologies. The IPv6 Transition CE Router is intended to be used in the same manner (same types of customers and end-user network architecture) as the IPv6 CE Router. 

The IPv6 Transition CE Router will implement the specified transition mechanisms and related provisioning and configuration mechanisms specified in this document in addition to complying with [RFC7084].

Barbara