IETF Logo Mail Archive

Re: [homenet] Support for RFC 7084 on shipping devices...

RayH <v6ops@globis.net> Mon, 07 October 2019 15:16 UTC

Return-Path: <v6ops@globis.net>
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 B014A12089B; Mon, 7 Oct 2019 08:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.477
X-Spam-Level:
X-Spam-Status: No, score=0.477 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, MISSING_MIMEOLE=1.899, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 Xpifu5N_vUxa; Mon, 7 Oct 2019 08:16:06 -0700 (PDT)
Received: from globis01.globis.net (92-111-140-212.static.v4.ziggozakelijk.nl [92.111.140.212]) by ietfa.amsl.com (Postfix) with ESMTP id C4574120879; Mon, 7 Oct 2019 08:16:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 9688240109; Mon, 7 Oct 2019 17:16:04 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unOYUi6rudks; Mon, 7 Oct 2019 17:16:02 +0200 (CEST)
Received: from [192.168.1.15] (h9041.upc-h.chello.nl [62.194.9.41]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 3B699400AF; Mon, 7 Oct 2019 17:16:02 +0200 (CEST)
Date: Mon, 07 Oct 2019 17:16:00 +0200
Message-ID: <6ef668e0-d0d2-46ed-afb0-4f0e28be1b6c@email.android.com>
X-Android-Message-ID: <6ef668e0-d0d2-46ed-afb0-4f0e28be1b6c@email.android.com>
In-Reply-To: <66B2B7A2-59B9-4FEB-B75A-4F9EF324BF8C@fugue.com>
From: RayH <v6ops@globis.net>
To: Ted Lemon <mellon@fugue.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Markus Stenberg <homenet@ietf.org>, 6MAN <6man@ietf.org>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/unPzfg2A-qIIbz1ILFdd_B6YM5U>
Subject: Re: [homenet] Support for RFC 7084 on shipping devices...
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Oct 2019 15:16:07 -0000



On 7 Oct 2019 17:03, Ted Lemon <mellon@fugue.com> wrote:
On Oct 7, 2019, at 10:00 AM, RayH <v6ops@globis.net> wrote:
Why does an ISP have to add complexity to their network in order to support Homenet?

If the ISP is on the hook for support, then “their network” includes your home network.

If that's their business model, we've got nothing to say.

IMHO that quite simply isn't Homenet's scope....  and they can deploy whatever proprietary management protocols they like in that situation.

Hopefully, they'll open one port to IA-PD RA etc. for plug and play. But no-one can force them.

Regards,

v2.23.0 | Report a Bug | By Email