Re: [homenet] support for HNCP in IPv6 CE routers

Timothy Winters <twinters@iol.unh.edu> Mon, 23 October 2017 18:34 UTC

Return-Path: <twinters@iol.unh.edu>
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 2B919139A22 for <homenet@ietfa.amsl.com>; Mon, 23 Oct 2017 11:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 7eN1t_AQhWsP for <homenet@ietfa.amsl.com>; Mon, 23 Oct 2017 11:34:24 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABDF5138351 for <homenet@ietf.org>; Mon, 23 Oct 2017 11:34:24 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id w5so12907278ywg.11 for <homenet@ietf.org>; Mon, 23 Oct 2017 11:34:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u8wkmWZpJAwQSTXchHfmjR6Dc397Uo2lccoHUiztkb0=; b=bDVaMqknhuA3nm3hhgOnyk/9YnveOa+DVHi+t58IXWe+lgH+i57QxABAx0jlPh/VpV 5sk12NrzTj4ZuRWTrMA3We5UeqJUwdiifwyu00jetimoxP5rJXNgF4R6hRscYx5m+jxy 54chihG0L6ZROW2TMn353bwSO08jbJ1vB7sFQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u8wkmWZpJAwQSTXchHfmjR6Dc397Uo2lccoHUiztkb0=; b=X/+9oXiVDnv8neyyclOJ6kAtyQJPP8nE4XIMqOO8tyJ1oVq35hjdlfAw9bul0GPntF yIXw4MmFfcsm5RicLoEkl7OdHj+k4kwvq5KfYOdUoBIj436+ES84Bd8Lvjoer1gQ8aJR CZ8eSxBPIJhMntu3+5b3csOxtp6Udv8PWfFuGUxUauHI4F4TfkRNFpIQc/YZrNFczrRJ xpwMHmeOk41c/eCH0aHPqgNEnXCl7k8QTk57R1Y+xHMAHH90as4wJhOAWOL9CK5ZldMQ EIqjCKEOl8JX9mXsi/05TYymXtqATA5MMYHQbM7k0GNS8s98FOqLjhrHttyvs4hlRCQ4 uLqQ==
X-Gm-Message-State: AMCzsaWXcnUOoWNmn6Dj+1iU9rR9CpNgop/29vcSaDKax90K/DAL9YTS Dv0+n03EbkJ73xuOy45BBefuigXHB/KBaFFNHSrMwQ==
X-Google-Smtp-Source: ABhQp+TxgGForO+WQeLbiCJay6Nhno+uWDfbVHS8DGN4kcsHfVOGz5R3B5y1Y7n0udFL2vpGEo5lcjzw+IZVcMrOe6U=
X-Received: by 10.37.20.6 with SMTP id 6mr9216855ybu.339.1508783663777; Mon, 23 Oct 2017 11:34:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.248.134 with HTTP; Mon, 23 Oct 2017 11:34:02 -0700 (PDT)
In-Reply-To: <FFB4541F-0BDB-4D5F-B6BB-647EFD0FE27E@google.com>
References: <80D10C70-9411-48EE-8189-87E9401D7F22@consulintel.es> <FFB4541F-0BDB-4D5F-B6BB-647EFD0FE27E@google.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Mon, 23 Oct 2017 14:34:02 -0400
Message-ID: <CAOSSMjUGJ_LJt=QFYpdG3x1St9ckZL_Tt=c9aO5M3OuKLTkdOw@mail.gmail.com>
To: james woodyatt <jhw@google.com>
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d2b9452ab0d055c3b1262"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/-P849oSErGHYzxNTENK6uOYAMyc>
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: Mon, 23 Oct 2017 18:34:27 -0000

On Mon, Oct 23, 2017 at 2:12 PM, james woodyatt <jhw@google.com> wrote:

> On Oct 23, 2017, at 00:48, JORDI PALET MARTINEZ <
> jordi.palet@consulintel.es> wrote:
>
>
> Now, in this version I’ve NOT included the HNCP support as a requirement,
> however I still mention it as:
>
> The end-user network is a stub network, in the sense that is not
>   providing transit to other external networks.  However, HNCP
>   ([RFC7788]) allows support for automatic provisioning of downstream
>   routers.  Figure 1 illustrates the model topology for the end-user
>   network.
>
> 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 it would be better if you leave aside all mention of HOMENET
> protocols from the RFC 7084-bis draft. That document is mainly intended for
> first-mile internet service providers, and I think the less the have to say
> about how residential networks operate behind the demarcation point at the
> edge of their networks, the better for everyone. This would give HOMENET
> optimal freedom to write standards for interoperability of devices intended
> for home networks without having to get mired in the tar pit of dealing
> with first-mile internet service provider stuff.
>

It would also be my preference to have this separate from 7084.


>
>
> --james woodyatt <jhw@google.com>
>
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>


-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR