[v6ops] transition-ipv4aas: positioning the draft

"STARK, BARBARA H" <bs7652@att.com> Wed, 25 April 2018 18:58 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 F0371127698 for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 11:58:50 -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 f_wHrJrn4B7b for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 11:58:49 -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 54914129C56 for <v6ops@ietf.org>; Wed, 25 Apr 2018 11:58:49 -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 w3PItVnc038459 for <v6ops@ietf.org>; Wed, 25 Apr 2018 14:58:48 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 2hjy7f0bnj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <v6ops@ietf.org>; Wed, 25 Apr 2018 14:58:48 -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 w3PIwlrH018396 for <v6ops@ietf.org>; Wed, 25 Apr 2018 14:58:47 -0400
Received: from zlp30487.vci.att.com (zlp30487.vci.att.com [135.47.91.176]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w3PIwhhY018310 for <v6ops@ietf.org>; Wed, 25 Apr 2018 14:58:44 -0400
Received: from zlp30487.vci.att.com (zlp30487.vci.att.com [127.0.0.1]) by zlp30487.vci.att.com (Service) with ESMTP id 3A64B4014049 for <v6ops@ietf.org>; Wed, 25 Apr 2018 18:58:43 +0000 (GMT)
Received: from GAALPA1MSGHUBAG.ITServices.sbc.com (unknown [130.8.218.156]) by zlp30487.vci.att.com (Service) with ESMTPS id 27F424014040 for <v6ops@ietf.org>; Wed, 25 Apr 2018 18:58:43 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.170]) by GAALPA1MSGHUBAG.ITServices.sbc.com ([130.8.218.156]) with mapi id 14.03.0361.001; Wed, 25 Apr 2018 14:58:42 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: V6 Ops List <v6ops@ietf.org>
Thread-Topic: transition-ipv4aas: positioning the draft
Thread-Index: AdPcwCSa7f9yrmemQveljKwJ4hWWjQ==
Date: Wed, 25 Apr 2018 18:58:42 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DD80DE8@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=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 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/0PNniQy5qGjWkMeTqnwGq0gdOOk>
Subject: [v6ops] transition-ipv4aas: positioning the draft
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 18:58:51 -0000

I have a number of comments for draft-palet-v6ops-transition-ipv4aas. I'm grouping comments under different email subject headers so it's easier to track the topic of any resulting discussion.

The first area of comments I have is on how to position this draft relative to RFC 7084 and in a way that will maximize its impact and likelihood of achieving its goal (which I think is to drive availability of CE routers that support *all* of the included transition technologies).

I notice the draft introduces the term "IPv6 transition CE". Sometimes this is "IPv6 transition CE router". I like this idea, but would suggest capitalizing and using the longer "IPv6 Transition CE Router". I think if this is a more formal term and this draft is positioned as defining requirements for an IPv6 Transition CE Router (rather than simply specifying "the transition requirements for an IPv6 Customer Edge (CE) router") then it becomes ok to make most of the SHOULD requirements into a MUST. That is, the draft is not an extension of a CE Router (RFC 7084). It's something new that is specified and defined here. And should be the title of the draft.

Saying "MUST" is stronger than "SHOULD" and will increase likelihood of success. It will also increase likelihood that *all* of the included technologies are implemented (as currently written it would be possible to do one or 2 of the technologies and still claim compliance). And it will make it easier to create a subsequent certification program, if there is demand for one. If the MUST statements apply only to the IPv6 Transition CE Router this draft defines, then there is no problem with saying "MUST". The requirements have no scope outside this draft.

----------

If taking this approach, requirements for DS-Lite would need to be included. Those can be copied from RFC 7084.

----------

RFC 7084 can still be a basis for this new thing (MUST comply with RFC 7084).

The current requirement for RFC 7084 compliance is "The IPv6 Transition CE router must comply with all the requirements stated in [RFC7084]." 
I suggest staying away from "all the requirements", since the RFC 7084 SHOULD and MAY requirements are also requirements, and I don't think it's intended to mandate those. I recommend simply saying:
The IPv6 Transition CE router MUST comply with [RFC7084].

---------

If done this way, I don't think it's necessary to make mention of 6rd in any way. It's omission from this draft will make it clear that it's not a component of an IPv6 Transition CE Router.


Barbara