Re: [v6ops] do we need to update RFC7084 ? - Basic Requirements for IPv6 Customer Edge Routers

Yannis Nikolopoulos <yanodd@otenet.gr> Sun, 27 November 2016 17:08 UTC

Return-Path: <yanodd@otenet.gr>
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 066C1129424 for <v6ops@ietfa.amsl.com>; Sun, 27 Nov 2016 09:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] 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 lY5iJwViCo6O for <v6ops@ietfa.amsl.com>; Sun, 27 Nov 2016 09:08:25 -0800 (PST)
Received: from calypso.otenet.gr (calypso.otenet.gr [83.235.67.36]) by ietfa.amsl.com (Postfix) with ESMTP id 98873127071 for <v6ops@ietf.org>; Sun, 27 Nov 2016 09:08:25 -0800 (PST)
Received: from [192.168.1.21] (dusted.otenet.gr [195.167.126.245]) by calypso.otenet.gr (ESMTP) with ESMTPSA id 9155F13804D; Sun, 27 Nov 2016 19:08:19 +0200 (EET)
To: "STARK, BARBARA H" <bs7652@att.com>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "krun.shah@gmail.com" <krun.shah@gmail.com>
References: <BA6017DD-82A0-4094-9DFB-7C1929E1E259@consulintel.es> <2D09D61DDFA73D4C884805CC7865E6114DA341D8@GAALPA1MSGUSRBF.ITServices.sbc.com>
From: Yannis Nikolopoulos <yanodd@otenet.gr>
Message-ID: <54fb4b5d-5cf3-cb0b-34b9-fb2551fa218f@otenet.gr>
Date: Sun, 27 Nov 2016 19:08:13 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DA341D8@GAALPA1MSGUSRBF.ITServices.sbc.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-rMEmJX00IMnIhM_Mdw94iK1jbE>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] do we need to update RFC7084 ? - Basic Requirements for IPv6 Customer Edge Routers
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 27 Nov 2016 17:08:28 -0000

Hello,


RFC 7084 (and 6204 before that) was used by us (ISPs) to push vendors to 
implement IPv6 deployment-related features. Before that, every ISP would 
write down their own specs, with various degrees of success. So, 7084 
was and still is a very good thing!


Now, as an ISP deploying (not thinking about, actually deploying as we 
speak) lw4o6 to potentially 1.5M users, I'd really prefer if 7084 
included lw4o6/MAP etc, not so much for my ISP, but for others that are 
still considering their options. I really see no reason whatsoever, for 
not updating 7084 (and also keeping existing transition technologies in 
place). BTW, lw4o6 support is mandatory in our CPE tenders (and so it is 
for the rest of DT group AFAIK)


cheers,

Yannis


On 11/04/2016 09:09 PM, STARK, BARBARA H wrote:
>>      When this document was published, the IPv4 situation was different that
>> the actual one.
>>
>>      Many ISPs could have deployed IPv6 using dual stack, or 6rd.
>>
>>      Also, lw6over4 was not available, same as other protocols such as MAP, or
>> 464XLAT, or there was no sufficient experience with them.
>>
>>      Now the situation is totally different, and ISPs will need to provide IPv6
>> service-only in the access link, instead of 6in4 based mechanisms, unless they
>> opt for dual-stack with CGN.
>>
>>      So my question is: should this document be updated to reflect the new
>> situation, so to provide a better guidance to both the ISPs and the vendors?
> RFC 7084 was never intended as advice to ISPs. It was intended as advice from ISPs to vendors of retail CE Routers. Along the lines of:
> Given IPv6 access network architectures ISPs have documented in CableLabs and Broadband Forum (BBF), here is a set of common requirements for a retail CE Router that can be used to connect to either of those types of access networks.
>
> If there is more than one ISP who is seriously committed to deploying one of the technologies you list (not just studying or thinking about it), and they want to extend RFC 7084, they should come forward. But I don't think it should be extended for any technology that doesn't have a real deployment commitment from multiple providers. I was very disappointed that some European ISPs pushed really hard to get DS Lite documented in BBF and RFC 7084, and then did nothing with that technology. CE Router vendors should not be asked to expend their scarce resources in support of experimental technologies. Experiments can be done with OpenWRT types of firmware. RFC 7084 extension needs to be done only for widely deployed technologies.
>
> BTW, we also stayed away from 3GPP access architectures, because there was no participation from 3GPP ISPs. The ISPs doing widespread deployment must be involved in providing the advice.
> Barbara
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops