Re: [v6ops] Requirements for IPv6 routers in various locations
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Fri, 24 February 2017 13:32 UTC
Return-Path: <prvs=1228d0687a=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 EACBF129735 for <v6ops@ietfa.amsl.com>; Fri, 24 Feb 2017 05:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 D-7Q_t5w8acB for <v6ops@ietfa.amsl.com>; Fri, 24 Feb 2017 05:32:27 -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 C17E6129712 for <v6ops@ietf.org>; Fri, 24 Feb 2017 05:32:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1487943140; x=1488547940; 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=eRSvNQMTTxTLIKXwZ3APFwOiE D1OttSW7UJaJAP9dII=; b=m/CSJG1ScUfVwPVLkIkEIL9TXiA6YMqBflSup0uiu 0+ByL7+rXp1hgj72sb8heJtjCrzUVBiVoqL/doK+6clWm7CBL3v1VtFexPq5p5+3 pXKqrsHZUvEjqzG9gKuvz4h6uITO9C7AQrBqa+waQOQN5TZhS29PGnBlVF9aA7CE Fc=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=jm6g74HG9e5TX7q9DoSEWV7M2FWNh7fqJJxxSz6hrbQmsdCOqLU2MhlTHU7R 0bjzBkyYHjxX5+9i+bxpO23xtOcVapqt1WmxcuAL4JItyR+e5oANBZAuJ 0lGz3GbjtUrn7k7E+09ozi/uARMtpZ3S3C1hfww73AUWEIZK6pXizU=;
X-MDAV-Processed: mail.consulintel.es, Fri, 24 Feb 2017 14:32:20 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 24 Feb 2017 14:32:17 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005373615.msg for <v6ops@ietf.org>; Fri, 24 Feb 2017 14:32:17 +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:170224:md50005373615::h/IdfD8bBs26qIVi:00000PPi
X-Return-Path: prvs=1228d0687a=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: Fri, 24 Feb 2017 14:32:13 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IPv6 Ops WG <v6ops@ietf.org>
Message-ID: <24EBE27C-C207-4025-AC2F-8D55617A56EB@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>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DACA276@GAALPA1MSGUSRBF.ITServices.sbc.com>
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/Rqxp6_Gb8pmZ2yIK4cELOM_y9KI>
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: Fri, 24 Feb 2017 13:32:29 -0000
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] FW: New Version Notification for draft-pa… JORDI PALET MARTINEZ
- Re: [v6ops] FW: New Version Notification for draf… Nathalie Trenaman
- Re: [v6ops] FW: New Version Notification for draf… Erik Kline
- Re: [v6ops] FW: New Version Notification for draf… JORDI PALET MARTINEZ
- Re: [v6ops] FW: New Version Notification for draf… Nathalie Trenaman
- Re: [v6ops] FW: New Version Notification for draf… Mikael Abrahamsson
- Re: [v6ops] FW: New Version Notification for draf… Rajiv Asati (rajiva)
- Re: [v6ops] FW: New Version Notification for draf… Philip Homburg
- Re: [v6ops] FW: New Version Notification for draf… Mikael Abrahamsson
- Re: [v6ops] New Version Notification for draft-pa… Ian Farrer
- Re: [v6ops] New Version Notification for draft-pa… STARK, BARBARA H
- Re: [v6ops] New Version Notification for draft-pa… james woodyatt
- Re: [v6ops] New Version Notification for draft-pa… STARK, BARBARA H
- [v6ops] Requirements for IPv6 routers in various … Fred Baker
- Re: [v6ops] Requirements for IPv6 routers in vari… Joe Touch
- Re: [v6ops] Requirements for IPv6 routers in vari… Fred Baker
- Re: [v6ops] New Version Notification for draft-pa… JORDI PALET MARTINEZ
- Re: [v6ops] New Version Notification for draft-pa… JORDI PALET MARTINEZ
- Re: [v6ops] Requirements for IPv6 routers in vari… JORDI PALET MARTINEZ
- Re: [v6ops] Requirements for IPv6 routers in vari… JORDI PALET MARTINEZ
- Re: [v6ops] New Version Notification for draft-pa… Fred Baker
- Re: [v6ops] FW: New Version Notification for draf… Tore Anderson
- Re: [v6ops] New Version Notification for draft-pa… Gert Doering
- Re: [v6ops] New Version Notification for draft-pa… JORDI PALET MARTINEZ
- Re: [v6ops] New Version Notification for draft-pa… Tim Chown
- Re: [v6ops] FW: New Version Notification for draf… JORDI PALET MARTINEZ
- Re: [v6ops] New Version Notification for draft-pa… james woodyatt
- Re: [v6ops] Requirements for IPv6 routers in vari… t.petch
- Re: [v6ops] Requirements for IPv6 routers in vari… STARK, BARBARA H
- Re: [v6ops] Requirements for IPv6 routers in vari… JORDI PALET MARTINEZ
- Re: [v6ops] Requirements for IPv6 routers in vari… james woodyatt
- Re: [v6ops] Requirements for IPv6 routers in vari… JORDI PALET MARTINEZ
- Re: [v6ops] FW: New Version Notification for draf… Yannis Nikolopoulos
- Re: [v6ops] FW: New Version Notification for draf… JORDI PALET MARTINEZ
- Re: [v6ops] FW: New Version Notification for draf… Yannis Nikolopoulos
- Re: [v6ops] FW: New Version Notification for draf… JORDI PALET MARTINEZ
- Re: [v6ops] FW: New Version Notification for draf… Yannis Nikolopoulos