Re: [v6ops] Requirements for IPv6 routers in various locations

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 27 February 2017 15:22 UTC

Return-Path: <prvs=1231b8dbd5=jordi.palet@consulintel.es>
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 CC96612A10A for <v6ops@ietfa.amsl.com>; Mon, 27 Feb 2017 07:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 Y0P_xhXfJe0V for <v6ops@ietfa.amsl.com>; Mon, 27 Feb 2017 07:21:55 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82A3512A0E2 for <v6ops@ietf.org>; Mon, 27 Feb 2017 07:21:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1488208911; x=1488813711; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=MIgC+cBnd4onvqpThMJRm6sZJ KZ7s9hT4ASuvaye4Og=; b=G4VWNFzN9/T3Tmqa764EtWv4WbjEHBdUGzY+n4zI1 YffQfSa7EZi7ftNyln38BM9V3m7fEi9ajVM/Tpda3/Luv+h1IFpcuCE+zrcHPRy/ nfmwd46d9V7qzxYiqcLmOfvdRhYK3Fr826uPYHqY52Kl6tRjwMqgVm9Dur2WepdK Yc=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=V8xy73xhnCp1sJ7aibc8A92aLH5sDyWsW/SngI2vzQaY2gvGFT96uzIvVcLP 4WtT9xeM4VEylkxLUmYj5fTf7AN0n/KkOgWE7mOjwnEWAQdecTUAGkwuj leEb01y2ol2P8Md/40+kVEwHXfUgJ8rqnSKEEnP1pU2WSwfCBHoXFA=;
X-MDAV-Processed: mail.consulintel.es, Mon, 27 Feb 2017 16:21:51 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 27 Feb 2017 16:21:50 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005375098.msg for <v6ops@ietf.org>; Mon, 27 Feb 2017 16:21:49 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170227:md50005375098::iizxU6qP0BTztIp4:00002ah6
X-Return-Path: prvs=1231b8dbd5=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.1f.0.170216
Date: Mon, 27 Feb 2017 16:21:48 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IPv6 Ops WG <v6ops@ietf.org>
Message-ID: <1BE1CAD4-138D-4AE4-8AD0-2334465A2D86@consulintel.es>
Thread-Topic: [v6ops] Requirements for IPv6 routers in various locations
References: <148763027040.25952.5914924936449771028.idtracker@ietfa.amsl.com> <692043A0-04F2-46EA-84D2-D4964E925C6B@consulintel.es> <03B10A5B-ABE3-4515-90B9-D16A41039229@google.com> <2D09D61DDFA73D4C884805CC7865E6114DAC7803@GAALPA1MSGUSRBF.ITServices.sbc.com> <EC9120C1-E135-4BD9-9B8B-AD9443261C13@gmail.com> <a52faa18-6ee5-b683-d1a1-36fdb956e10d@isi.edu> <C5483E13-2155-434D-A2CD-F165577872C0@gmail.com> <65EF9449-6FCC-4666-983F-E33E9812C9F3@consulintel.es> <2D09D61DDFA73D4C884805CC7865E6114DACA276@GAALPA1MSGUSRBF.ITServices.sbc.com> <24EBE27C-C207-4025-AC2F-8D55617A56EB@consulintel.es>
In-Reply-To: <24EBE27C-C207-4025-AC2F-8D55617A56EB@consulintel.es>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0EsDxxu3mPYk7FWdPMuPHO7Ql74>
Subject: Re: [v6ops] Requirements for IPv6 routers in various locations
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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, 27 Feb 2017 15:22:01 -0000

Hi all,

I’ve submitted a new version for this document.

Barbara, after thinking again for several hours on this classification, I’ve the feeling that all those cases have the same requirements as the ones in the original document. Let me explain why. Those 2 cases that need to “export services” (by means of DMZ, virtual host, port/protocol forwarding, etc.), actually will need that only for IPv4 (because the private addresses behind NAT), and this is already supported by all the devices in the market, so we don’t need to have any “new” IPv4 requirements for that.

For IPv6, well, you have GUA, so being all the addresses global, they are always reachable, right? Of course, it will be good that any IPv6 CE has a configurable firewall, and may be enabled by default, but I recall in the original document, there is already text about that, so probably we don’t want to change it.

So according to this, and responding to Fred comments on the decision about one or several documents for different scenarios, I think that leaving out special requirements for data-centers, content-providers, big enterprises, etc., the requirements for a CE “baseline” are the same in all the cases, and the differences are more related to more memory, more interfaces/types/speed, performance, etc.

So, in my opinion, this document is good for most of the residential users, SOHO, SMEs, and probably some degree of medium-to-big organizations, and may be, if we want other scenarios we can either “upgrade” this document to include them, or have other documents that state as “baseline” this document to avoid repeating text. I think the second option is close to what Tim suggested.

So, the new version is:

https://datatracker.ietf.org/doc/draft-palet-v6ops-rfc7084-bis/

Let me try to summarize the main changes:

1) 6rd and DS-Lite are back SHOULD as in the original document.
2) Requirements for 464XLAT, MAP-E/T, lw4o6 and 6in4 are now completed, and all them are SHOULD, same as 6rd and DS-Lite.
3) Added a section “Usage Scenarios” to clarify what I indicated above.
4) Added, as SHOULD, support for HNCP as a LAN requirement.
5) Added requirement for support of DHCPv6 S46 priority option RFC8026.
6) Added requirement for support of DHCPv4-over-DHCPv6 (DHCP4o6) transport RFC7341.

Comments?

Regards,
Jordi
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Responder a: <jordi.palet@consulintel.es>
Fecha: viernes, 24 de febrero de 2017, 14:32
Para: IPv6 Ops WG <v6ops@ietf.org>
Asunto: Re: [v6ops] Requirements for IPv6 routers in various locations

    Hi Barbara,
    
    Then fully agree !
    
    I think the main difference between the “2 groups” that you differentiate is that in the second group the CE needs to support the ability to either being setup as a “bridge” or be able to have a DMZ or to allow ports/protocols forwarding.
    
    Actually, I even think that 5 is part of your “first” group (so together are 1, 2, 4 and 5) and only 3 and 6 are in the second group.
    
    So, according to this, I don’t see the need to have 2 different documents, just un update of the RFC7084 (and as you said, not changing the definition of the terms neither the scope).
    
    Regards,
    Jordi
     
    
    -----Mensaje original-----
    De: "STARK, BARBARA H" <bs7652@att.com>
    Responder a: <bs7652@att.com>
    Fecha: viernes, 24 de febrero de 2017, 14:19
    Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, IPv6 Ops WG <v6ops@ietf.org>
    Asunto: RE: [v6ops] Requirements for IPv6 routers in various locations
    
        > Can we define what is a customer edge?
        
        RFC 7084 already includes a definition of what it means:
        
        IPv6 Customer Edge Router:
        a node intended for home or small-office use that forwards IPv6 packets not explicitly addressed to itself.  The IPv6 CE router connects the end-user network to a service provider network.
        
        I would suggest not trying to change this definition of this term, because I think that would be confusing. If a more encompassing term is needed, I think it would be better to create a new term.
        I would also be strongly opposed to any attempt at a RFC 7084 update that changed the scope of RFC 7084.
        
        > 1) Pure residential
        > 2) Residential with small home office
        > 3) Residential/techie (with or w/o home office) that have exported services
        > (email server, web server, VPN server, etc.).
        > 4) Small home office
        > 5) SMEs with just use Internet for “browsing”, emailing, etc.
        > 6) SMEs as in the previous case that also have exported services (email
        > server, web server, VPN server, etc.).
        
        Clearly, 1, 2, and 4 are included in the RFC 7084 definition. If the needs of 3, 5, and 6 are met by a device designed for 1/2/4, then they are certainly welcome to use it. If such a device does not meet the needs of 3/5/6, then it doesn't meet their needs.
        
        Barbara 
        
    
    
    
    **********************************************
    IPv4 is over
    Are you ready for the new Internet ?
    http://www.consulintel.es
    The IPv6 Company
    
    This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
    
    
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    
    **********************************************
    IPv4 is over
    Are you ready for the new Internet ?
    http://www.consulintel.es
    The IPv6 Company
    
    This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.