IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 07 October 2019 13:47 UTC

Return-Path: <mcr@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 3DF72120096; Mon, 7 Oct 2019 06:47:00 -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, SPF_HELO_NONE=0.001, SPF_PASS=-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 1IDnaOw-p6YD; Mon, 7 Oct 2019 06:46:58 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12495120020; Mon, 7 Oct 2019 06:46:58 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [80.233.32.253]) by relay.sandelman.ca (Postfix) with ESMTPS id 874621F456; Mon, 7 Oct 2019 13:46:56 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 10CB0773; Mon, 7 Oct 2019 15:47:40 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Markus Stenberg <homenet@ietf.org>, 6MAN <6man@ietf.org>
In-reply-to: <alpine.DEB.2.20.1910071203140.968@uplift.swm.pp.se>
References: <56255ECF-9002-4440-BA0D-665EFC4BA9C6@fugue.com> <F638F635-9A1C-409E-BDB8-C00DF00A64C8@employees.org> <alpine.DEB.2.20.1910040752050.968@uplift.swm.pp.se> <A52F076F-817D-4807-8CD6-280C2040AEBF@employees.org> <5F0D2E3D-BE20-4421-8A37-E81E6B93B3A5@fugue.com> <E50D25C7-8EF1-4685-9442-021F019F7F62@employees.org> <60B2C15B-E126-4F86-AA9A-9EB9A6C0EB2D@fugue.com> <FBCD2C32-9CBE-4499-A3E9-0FF4991E34DF@employees.org> <A5D12082-3D6A-4540-9AFB-2530D4FA6A32@fugue.com> <FF34E138-469F-40F6-BA8F-7AE02F878B29@employees.org> <alpine.DEB.2.20.1910071203140.968@uplift.swm.pp.se>
Comments: In-reply-to Mikael Abrahamsson <swmike@swm.pp.se> message dated "Mon, 07 Oct 2019 12:07:25 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 07 Oct 2019 15:47:40 +0200
Message-ID: <5987.1570456060@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/UBuO21u6TSLn_mw3h1M-8VehYDk>
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 13:47:00 -0000

Mikael Abrahamsson <swmike@swm.pp.se> wrote:
    >> The deployment challenge of that is that every router must support HNCP and
    >> must support SADR.

    > Yes, there is indeed a problem here with incremental deployment.

    > That's why I think there might be upside in "homenet lite" which drops the
    > arbitrary topology requirement and keeps the "routed home" requirement, but
    > also brings with it the service discovery part. Perhaps it's an easier chunk
    > of code to deploy if vendors do not need to implement full homenet but
    > instead implement RFC7084 plus a few other things?

So, 7084++ or HomeNet-Lite.  

    > High level would be to use DHCPv6-PD, turning sub-router WAN firewall off and
    > enabling service discovery proxies, as I outlined in previous email.

I agree. 7084bis should suggest downstream DHCPv6-PD be supported, and we
need to explicitely signal there when HNCP is available so that we don't wind
up double allocating things, etc.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email