Re: [homenet] support for HNCP in IPv6 CE routers
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 24 October 2017 14:56 UTC
Return-Path: <prvs=1470615b63=jordi.palet@consulintel.es>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6307913DC3B for <homenet@ietfa.amsl.com>; Tue, 24 Oct 2017 07:56:56 -0700 (PDT)
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 pZoiXh4iPLD8 for <homenet@ietfa.amsl.com>; Tue, 24 Oct 2017 07:56:54 -0700 (PDT)
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 458CA13F6C7 for <homenet@ietf.org>; Tue, 24 Oct 2017 07:56:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1508857012; x=1509461812; 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=eoMjfN7mepj9PO54ZtFRQOa9S 1kPl82G+T+Sy14RgTQ=; b=Fn2xmqwBTsAK3yFG+KPh7OVEkvT7lr2MqMZV5CxQQ qJudjhBglrvqX23+Nxw8uW5bdbW0kS85B6gGW0xveZ7dwa8Pklg09iffyAVroPUp Tbw7KvDPXcAf5RFqOORtTpLUU37ZdmzDY/VhuPtHSAt+Mfa3pQwC/KEQQUEsjhHF Qc=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=lt3C6guc+Km4ScEz+YiwgXku4GrfnDh+/9a5toxkHYRAVGkH+Sjj2KOTcPR3 /M6PvYI26InVDAxGsoctiQGsZWAppaMXPsw5r/VicOsAudQo46zj1xUSJ CDAYnW2MVRLXYfHfcww+qx7fpDn+8nLoifV805vV+RXdcoaM8eeRMw=;
X-MDAV-Processed: mail.consulintel.es, Tue, 24 Oct 2017 16:56:52 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 24 Oct 2017 16:56:51 +0200
Received: from [172.20.11.239] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005604307.msg for <homenet@ietf.org>; Tue, 24 Oct 2017 16:56:51 +0200
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:171024:md50005604307::RSXYq+DlGIsPbkF3:00000chp
X-Return-Path: prvs=1470615b63=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: homenet@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Tue, 24 Oct 2017 18:56:43 +0400
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: HOMENET <homenet@ietf.org>
Message-ID: <26244C6F-928E-45A2-8183-939DC64A41EC@consulintel.es>
Thread-Topic: [homenet] support for HNCP in IPv6 CE routers
References: <80D10C70-9411-48EE-8189-87E9401D7F22@consulintel.es> <FFB4541F-0BDB-4D5F-B6BB-647EFD0FE27E@google.com> <BA6C5D18-7EB4-4571-99CF-E09AFE8DE834@consulintel.es> <9954.1508856244@obiwan.sandelman.ca>
In-Reply-To: <9954.1508856244@obiwan.sandelman.ca>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/qNkEodVaQD3U7i7N9S95s96Sihk>
Subject: Re: [homenet] support for HNCP in IPv6 CE routers
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2017 14:56:56 -0000
Hi Michael, Let me try to explain it …, just for clarity, because that belongs to v6ops. I started to work in an update of the original RFC7084 (https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc7084-bis/), in order to include support for the newer transition mechanism. In the last Chicago meeting, it was adopted as a WG item. Then I got the suggestion to include also HNCP support, and I did, and worked out a couple of versions of that document. However, in Prague, there was a push-back, and the WG basically decided that I should not continue that way, and instead I should have a new document “only” for the transition mechanism and not include explicit support for HNCP and run that thru homenet. So, I worked out https://datatracker.ietf.org/doc/draft-palet-v6ops-rfc7084-bis-transition/. I personally believe it is a missing opportunity to get the “default” IPv6 CPE that is typically provided by the ISP having HNCP support. So, what I’m suggesting to Homenet is to have an explicit document for ISPs that still want to have RFC7084+transition+HNCP, to be able to reference in the RFQs to those 3 documents. Regards, Jordi -----Mensaje original----- De: homenet <homenet-bounces@ietf.org> en nombre de Michael Richardson <mcr+ietf@sandelman.ca> Responder a: <mcr+ietf@sandelman.ca> Fecha: martes, 24 de octubre de 2017, 18:44 Para: <jordi.palet@consulintel.es> CC: HOMENET <homenet@ietf.org> Asunto: Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote: > Hi James, > I included HNCP in RFC7084-bis following your request :-( Where is the document being revised? RFC7084 turns out to be a document which is both requirements on CE routers, but also implicitely requirements on ISPs to provide things to compliant CE routers. I would like to have either both explicitely in an RFC7084bis, or have two documents. I'd sure like to get some of our (HOMENET) DNS forward/reverse requirements into the RFC7084bis-ISP-requirements. > So, concentrating in homenet. > Do, repeating my 2nd questions, do we believe we need a specific > document HOMENET document to suggest to include in CE, or to say how to > do it, or whatever? I'm just not parsing this question, btw. > Now, the questions I’ve for this WG is: > 1) Do you think I should mention other homenet documents ? 2) Do > you think we should have a specific homenet document requiring the > support of homenet for IPv6 CE routers, so for example this becomes an > integral part of testing by ISPs, IPv6 Ready Logo, or even RFQs, etc.? > I will be happy to work in a homenet document if we believe that 2 > above is needed. Anyone else interested? I think that we need some additional text in 7084bis that permits a 7084bis-only device to not screw up a HOMENET network. I don't have specific examples at the moment, but I recall we had various discussions in the past about how things might work or fail to work. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet ********************************************** 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 exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Timothy Winters
- Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers Gert Doering
- Re: [homenet] support for HNCP in IPv6 CE routers STARK, BARBARA H
- Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers Michael Richardson
- Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Michael Richardson
- Re: [homenet] support for HNCP in IPv6 CE routers Juliusz Chroboczek
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Gert Doering
- Re: [homenet] support for HNCP in IPv6 CE routers David Oran
- Re: [homenet] support for HNCP in IPv6 CE routers Ted Lemon
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Michael Richardson
- Re: [homenet] support for HNCP in IPv6 CE routers Gert Doering
- Re: [homenet] support for HNCP in IPv6 CE routers Juliusz Chroboczek
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Juliusz Chroboczek
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt