IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 26 October 2017 14:53 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 8331213F5AA for <homenet@ietfa.amsl.com>; Thu, 26 Oct 2017 07:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 u7Kwq6xksxTY for <homenet@ietfa.amsl.com>; Thu, 26 Oct 2017 07:53:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E67C313F5A2 for <homenet@ietf.org>; Thu, 26 Oct 2017 07:53:12 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 72E7320246; Thu, 26 Oct 2017 10:53:44 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7944381DB3; Thu, 26 Oct 2017 10:53:11 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: james woodyatt <jhw@google.com>
cc: HOMENET <homenet@ietf.org>
In-Reply-To: <a1ec0d30-ef09-d51d-91a2-8ce1d9f8b9dd@google.com>
References: <80D10C70-9411-48EE-8189-87E9401D7F22@consulintel.es> <FFB4541F-0BDB-4D5F-B6BB-647EFD0FE27E@google.com> <BA6C5D18-7EB4-4571-99CF-E09AFE8DE834@consulintel.es> <C6847ADB-E163-4738-B334-5B16DD655C86@att.com> <a1ec0d30-ef09-d51d-91a2-8ce1d9f8b9dd@google.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 26 Oct 2017 10:53:11 -0400
Message-ID: <394.1509029591@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/gjcRLkB8Py1eLTORkbo7wKhgaXM>
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: Thu, 26 Oct 2017 14:53:14 -0000

james woodyatt <jhw@google.com> wrote:
    >>
    >> [...] and also what may or may not be good to include in requirements
    >> specifically targeting routers at the customer's edge (CE).

    > I think it's a waste of time for HOMENET to propose requirements for
    > routers in service provider networks, event those at the edge that
    > connects to subscribers. Those requirements will be neither welcome nor
    > observed by the industry.

I think it's appropriate for HOMENET to review and comment on a document in
v6ops that doing that.  Do you agree?

I'd like a 7084bis document to focus less on requirements for the CE
*router*, and more on what shapes of bits we need to pass between CE and ISP.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email