IETF Logo Mail Archive

Re: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt

"STARK, BARBARA H" <bs7652@att.com> Mon, 19 June 2017 14:59 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 81BC113151A for <v6ops@ietfa.amsl.com>; Mon, 19 Jun 2017 07:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level:
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=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 i2mXAZojWlLV for <v6ops@ietfa.amsl.com>; Mon, 19 Jun 2017 07:59:34 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 39FBB131516 for <v6ops@ietf.org>; Mon, 19 Jun 2017 07:59:31 -0700 (PDT)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v5JDjUNx005510; Mon, 19 Jun 2017 09:47:44 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049287.ppops.net-00191d01. with ESMTP id 2b6bf9sst2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Jun 2017 09:47:44 -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 v5JDlg7i026723; Mon, 19 Jun 2017 09:47:42 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v5JDlXGl026475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Jun 2017 09:47:36 -0400
Received: from GAALPA1MSGHUBAF.ITServices.sbc.com (GAALPA1MSGHUBAF.itservices.sbc.com [130.8.218.155]) by alpi131.aldc.att.com (RSA Interceptor); Mon, 19 Jun 2017 13:47:27 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.134]) by GAALPA1MSGHUBAF.ITServices.sbc.com ([130.8.218.155]) with mapi id 14.03.0319.002; Mon, 19 Jun 2017 09:47:27 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt
Thread-Index: AQHS56+w6G39dmryMUGu+j6PZAaxUKIsJ3eQ
Date: Mon, 19 Jun 2017 13:47:26 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DB9A42D@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <149773408722.14141.1243099989313191246.idtracker@ietfa.amsl.com> <334ACBB6-C438-410B-81D7-49269AC51004@gmail.com>
In-Reply-To: <334ACBB6-C438-410B-81D7-49269AC51004@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.235.224]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-19_08:, , 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 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706190232
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5Pajq0coBI6BkFgEsj80eVG2JMU>
Subject: Re: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt
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: Mon, 19 Jun 2017 14:59:38 -0000

> Your thoughts?

Here are a number of my thoughts.

BBF described automated IPv6 configuration for telco-procured CE routers in TR-124 (https://www.broadband-forum.org/technical/download/TR-124_Issue-5.pdf) in Annex A. A.1 is for PPPoE and A.2 is for native IPv6. I don't see a need for this draft wrt CE routers my company procures, because auto-config advice already exists.

The BBF flow has simultaneous RS and DHCPv6 solicitation. This is at odds with what you suggest. Simultaneous and sequential are both allowed by RFC 7084. I realize many cable providers have expressed a preference for sequential RS and DHCPv6 solicit, but many telcos have expressed a preference for simultaneous. But both models work in cable and telco environments.

The BBF flow mandates requesting IA_PD, while you propose it as a very weak MAY. Note that RFC 7084 mandates support for IA_PD. If you really want auto config of a CE router, this is the only way I know of to do it. I don't see that a MAY IA_PD requirement would ever result in auto configuration. Only a MUST will.

BBF also supports auto-configuration via the unnumbered model where the RA does not include an Autonomous prefix and there is no offered IA_NA. RFC 7084 allows for the unnumbered model. You make no mention of the unnumbered model. I don't know how prevalent the unnumbered model is, though.

Sub-delegating into a home network with many subnets (which means the topology is likely to be unpredictable and arbitrary) really needs HNCP and not IA_PD. In the absence of HNCP, any algorithm to try to calculate the correct number of needed prefixes doesn't make sense to me. In other words, I wouldn't trust a calculation that resulted in a need for 17 prefixes, in the absence of HNCP.

As a final note, I have a pet peeve wrt "CPE". CPE = *all* Customer Premises Equipment, including set-top boxes, home automation gateways, VoIP ATAs, etc. Unless this doc is for auto-config of STBs and the rest, could I convince you to use "CE Router"? "CER" can be used as an abbreviated form.
Barbara

v2.23.0 | Report a Bug | By Email