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 22:40 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 CAB181294F4 for <v6ops@ietfa.amsl.com>; Mon, 19 Jun 2017 15:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level:
X-Spam-Status: No, score=-5.401 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] 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 Rid6ndUuXRja for <v6ops@ietfa.amsl.com>; Mon, 19 Jun 2017 15:40:19 -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 246A4129526 for <v6ops@ietf.org>; Mon, 19 Jun 2017 15:40:19 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v5JMa7d8014907; Mon, 19 Jun 2017 18:40:16 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049295.ppops.net-00191d01. with ESMTP id 2b6pm29efu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Jun 2017 18:40:16 -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 v5JMeEpd016536; Mon, 19 Jun 2017 18:40:15 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v5JMe8Fb016399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Jun 2017 18:40:10 -0400
Received: from GAALPA1MSGHUBAD.ITServices.sbc.com (GAALPA1MSGHUBAD.itservices.sbc.com [130.8.218.153]) by alpi132.aldc.att.com (RSA Interceptor); Mon, 19 Jun 2017 22:39:53 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.134]) by GAALPA1MSGHUBAD.ITServices.sbc.com ([130.8.218.153]) with mapi id 14.03.0319.002; Mon, 19 Jun 2017 18:39:53 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt
Thread-Index: AQHS56+w6G39dmryMUGu+j6PZAaxUKIsJ3eQgADF6YD//9hWsA==
Date: Mon, 19 Jun 2017 22:39:52 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DB9AFD6@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <149773408722.14141.1243099989313191246.idtracker@ietfa.amsl.com> <334ACBB6-C438-410B-81D7-49269AC51004@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114DB9A42D@GAALPA1MSGUSRBF.ITServices.sbc.com> <0A5C360E-0038-4CA0-AC3E-E8B75FD770FE@gmail.com>
In-Reply-To: <0A5C360E-0038-4CA0-AC3E-E8B75FD770FE@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.253.150]
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_12:, , 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-1706190374
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lr2HDxmSQKWDajy2PWatZgufDP4>
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 22:40:21 -0000

> Thanks. TR-124, of course, applies to DSL routers procured by companies and
> used in managed router services. It doesn't apply to Cable Modem routers,
> nor to routers used in open source networks such as Jordi discusses in his
> 7084-bis.
> 
> Are you objecting to the draft, or simply stating that it covers material already
> covered for DSL routers used in ISP managed service?

TR-124 is used by telco ISPs for a variety of procured CE routers, including those with and without a DSL modem or G.fast or PON ONT interface. Some just have Ethernet WAN. It is not limited to DSL WAN interface. Note that the Annex A procedures assume nothing more than Ethernet MAC to the WAN.

I would object to anything that suggested the auto-configuration processes that may be used by cable providers are somehow superior, better, preferred, or recommended over auto-config procedures used by non-cable providers.

There are numerous "correct" ways to do IPv6 auto-config. Describing just one, and then making it normative in a 7084-bis would not be something I would favor. If cable providers want to get together and say "FYI, here is a way some cable operators like to do auto-config", I would not object. Or if v6ops wanted to do a draft of "here are several possible and valid ways to do auto-config that would be RFC7084-compliant -- pick any one of them because the only requirement for interoperability is RFC7084", I would be happy to participate.
Barbara

v2.23.0 | Report a Bug | By Email