Re: [v6ops] LISP support for draft-ietf-v6ops-rfc7084-bis-00

"STARK, BARBARA H" <bs7652@att.com> Wed, 12 April 2017 15:26 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 047EC129C5D for <v6ops@ietfa.amsl.com>; Wed, 12 Apr 2017 08:26:15 -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 ORX0JAnx3c-3 for <v6ops@ietfa.amsl.com>; Wed, 12 Apr 2017 08:26:13 -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 6C93A129516 for <v6ops@ietf.org>; Wed, 12 Apr 2017 08:26:12 -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 v3CEOuih030351; Wed, 12 Apr 2017 10:32:53 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049287.ppops.net-00191d01. with ESMTP id 29sneha2g3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Apr 2017 10:32:53 -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 v3CEWpHL014204; Wed, 12 Apr 2017 10:32:52 -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 v3CEWhdW014010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 12 Apr 2017 10:32:44 -0400
Received: from GAALPA1MSGHUBAF.ITServices.sbc.com (GAALPA1MSGHUBAF.itservices.sbc.com [130.8.218.155]) by alpi131.aldc.att.com (RSA Interceptor); Wed, 12 Apr 2017 14:32:34 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.165]) by GAALPA1MSGHUBAF.ITServices.sbc.com ([130.8.218.155]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 10:32:33 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] LISP support for draft-ietf-v6ops-rfc7084-bis-00
Thread-Index: AQHSstX9/aA+q42Pz0u3Y/nN6XijSKHBvWsAgAACzQCAABQWgIAAMIOAgAAEPYD//76fsA==
Date: Wed, 12 Apr 2017 14:32:33 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DB19757@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <D8F5C737-B01A-4EC8-9175-C4921C0CD69F@consulintel.es> <392D675B-73C4-40D3-81A8-A06907F5581D@employees.org> <3BBFC922-85BD-49B5-B39E-227F191BD48C@consulintel.es> <729244A1-E7AB-4BA0-8B39-A6122D2C32DB@employees.org> <CAD6AjGQyatWEOxCpnOn8H+SxG=BWM=cBPaXoON6vA7dj7TNqOQ@mail.gmail.com> <72F5C80C-DDB5-422E-8FEC-7D4157722780@consulintel.es>
In-Reply-To: <72F5C80C-DDB5-422E-8FEC-7D4157722780@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.164.19]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-12_11:, , 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-1702020001 definitions=main-1704120120
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/WFlKD6MisxxRGgxn1l8I2su2c-M>
Subject: Re: [v6ops] LISP support for draft-ietf-v6ops-rfc7084-bis-00
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, 12 Apr 2017 15:26:15 -0000

> Fully agree with Cameron view, and furthermore … if we need to choose one
> mechanism because how many millions of devices already use it, and this
> demonstrates the success, clearly 464XLAT has more TENS OF MILLIONS of
> users than DS-LITE + 6RD + MAP E + MAP T, altogether, and of course it
> means a single ISP having both wired and cellular networks, can have a single
> way to deploy IPv6 instead of two.

RFC 7084 has nothing to do with cellular (3GPP) networks. 3GPP deployments are not relevant to this discussion. 3GPP and wireline deployments are not currently converged, with the 3GPP RAN and IP core networks being distinct from the wireline IP access networks (wireline is used as backhaul for the 3GPP networks at layers 1 and 2, but not for IP). What makes sense for a 3GPP deployment may or may not make sense for a wireline deployment -- especially considering the lack of extensive IA_PD support in deployed 3GPP networks.

If some ISP with wireline and wireless has interest in converging their wireline IPv6 deployment with their wireless, in the very near future (using network elements that are already being trialed or have been deployed), it would indeed be nice for them to speak up. Personally, I have no internal requests from my company to drive such IPv6 convergence.

So please don't use statistics related to 3GPP deployments in an argument for wireline CE routers. And please don't try to bloat the CE router with everything needed to support attachment to a 3GPP network.

In the wireline deployments I'm aware of, the only ones reaching into the millions have used dual stack, 6rd, or (possibly) DS-Lite. And of these 3, the only one that I believe should ever be considered mandatory for all CE routers is dual stack.
Barbara