IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Mon, 07 October 2019 15:31 UTC

Return-Path: <mellon@fugue.com>
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 3BB7C1200E6 for <homenet@ietfa.amsl.com>; Mon, 7 Oct 2019 08:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 EnStebU_SEfM for <homenet@ietfa.amsl.com>; Mon, 7 Oct 2019 08:31:37 -0700 (PDT)
Received: from mail-oi1-x243.google.com (mail-oi1-x243.google.com [IPv6:2607:f8b0:4864:20::243]) (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 93B7B1200EC for <homenet@ietf.org>; Mon, 7 Oct 2019 08:31:37 -0700 (PDT)
Received: by mail-oi1-x243.google.com with SMTP id m16so12037486oic.5 for <homenet@ietf.org>; Mon, 07 Oct 2019 08:31:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=ap1niMlda9oEEcd9iJTGINb5t8zqh8Mq6YiHc16LxSE=; b=r2w6D02yG0BfjG67NdvZ+PqnVXBYM9gp7tIgkQt1R2yWGmJM4hIHOgQ0NWjAyoTxkg 6c5PW3QIu9urh9dEoDqhZunSrOueDk+bnzSk6gi6gVswmLlAiR/dhTu+hUn0SMh8yx6d vxriJnzU0qomIWeidvNrkriknBBXHW21tNM1AmcgdGDRtbfvD9mip8If7xHz5y7OFM3r qgVhI6hKEdyfz5EnSRy7Yzj+7JxG0UpFNij377VrgDLCOSpXKfHqjM8yULYACEcVBHFC jvXE2DfWWV5DyUfboNt772a/iijxpJqVo2euOiQhCPBtgFS7PDB8cXWXYvix3jaaZ5uq vjPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=ap1niMlda9oEEcd9iJTGINb5t8zqh8Mq6YiHc16LxSE=; b=WtCQF0VNn9zKMwqGtxN41OIgMrjw8dvX2TBYjaNJH8Nlk1LDOmkpWpswvxR8muYrXT TXzteFcjH1EEMZXwcyb5fJc79C30Gzt3xq9HZSvjjNDBQNXu/9zITUdwKpvelKHscLuY JBtNMEJ8Tt1u5t+APA5+Q2nN2qLWnwwaRD9/ic9T0+EW9z7AP8U8U6vU8bdvt9fzhhBh okE6Up683Fi1GSiw5fJOW8aS79aojs6TT1LSa71NSU84AeY2PVhfr0dh6bYb2VtmPZbG 2324QuZWuPaRnnWRpCT04oS7Dq54q+otmQp9L1NdSuPyg54HSZ4/Q/KKracbIdSLMReQ DCQw==
X-Gm-Message-State: APjAAAXahOOff5re+SQhWUZ2OxGgDW6ueqqbJRQFC9he5iRlviIkkk0P 1/+eUIoyFnBx+jrSq/ZhT3/Qdw==
X-Google-Smtp-Source: APXvYqwkEUaLah77RkoP43kLIE1Yat8pNzhXKHJMXHvjieecN215dxIZaByyJPIkTUyGnTomV7bFMg==
X-Received: by 2002:aca:1003:: with SMTP id 3mr18828475oiq.13.1570462296924; Mon, 07 Oct 2019 08:31:36 -0700 (PDT)
Received: from [10.10.9.60] (cpe-24-243-152-218.rgv.res.rr.com. [24.243.152.218]) by smtp.gmail.com with ESMTPSA id f12sm4218848oij.1.2019.10.07.08.31.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Oct 2019 08:31:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_AD22492B-1D9B-42D5-92E4-469F957C47E6"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3600\))
From: Ted Lemon <mellon@fugue.com>
X-Priority: 3
In-Reply-To: <6ef668e0-d0d2-46ed-afb0-4f0e28be1b6c@email.android.com>
Date: Mon, 07 Oct 2019 10:31:34 -0500
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Markus Stenberg <homenet@ietf.org>, 6MAN <6man@ietf.org>
Message-Id: <06802631-340F-4C9F-A0D6-E92A9786FD81@fugue.com>
References: <6ef668e0-d0d2-46ed-afb0-4f0e28be1b6c@email.android.com>
To: RayH <v6ops@globis.net>
X-Mailer: Apple Mail (2.3600)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/8SHm0AeoXbyb9189HLNxnhfn0Zg>
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:31:39 -0000

On Oct 7, 2019, at 10:16 AM, RayH <v6ops@globis.net> wrote:
> If the ISP is on the hook for support, then “their network” includes your home network.
> 

What I mean is that the ISP gets phone calls from customers whether it’s their fault the network is broken or not.  So they aren’t going out of their way to make the home network more complicated.  Although we have seen ISP participation in Homenet, I do not expect them to be the drivers for this functionality.   I’d love to be proven wrong, but I don’t think it’s realistic to assume otherwise.

v2.23.0 | Report a Bug | By Email