IETF Logo Mail Archive

Re: [homenet] homenet: what now? ... next?

Michael Thomas <mike@mtcc.com> Sat, 02 March 2019 18:17 UTC

Return-Path: <mike@mtcc.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 D5555130E09 for <homenet@ietfa.amsl.com>; Sat, 2 Mar 2019 10:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ezd_Q5NjT3Ag for <homenet@ietfa.amsl.com>; Sat, 2 Mar 2019 10:17:15 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB55F130DC0 for <homenet@ietf.org>; Sat, 2 Mar 2019 10:17:15 -0800 (PST)
Received: from Michaels-MacBook.local (170-75-133-42.volcanocom.com [170.75.133.42] (may be forged)) (authenticated bits=0) by mtcc.com (8.15.2/8.15.2/Debian-3) with ESMTPSA id x22IHDiI012811 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 2 Mar 2019 10:17:14 -0800
To: Juliusz Chroboczek <jch@irif.fr>
Cc: "homenet@ietf.org" <homenet@ietf.org>
References: <894b4181-c4ca-5cf1-adba-1c5fcab0d355@cs.tcd.ie> <90A48EC1-C13D-4B9B-9F04-252C0CC87084@fugue.com> <dbe6e19f-84c2-f2eb-b9ab-d085de7c299c@mtcc.com> <2D09D61DDFA73D4C884805CC7865E6114E0C50C4@GAALPA1MSGUSRBF.ITServices.sbc.com> <ed1e6a2c-b830-07fb-df0d-df6dae96cdd9@mtcc.com> <87fts55jdi.wl-jch@irif.fr>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <27e70874-7de9-5220-0631-7271f0bfd4ce@mtcc.com>
Date: Sat, 02 Mar 2019 10:17:08 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <87fts55jdi.wl-jch@irif.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/oIAC7Ld6frPrjTEyTx4yGWT_OVg>
Subject: Re: [homenet] homenet: what now? ... next?
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: Sat, 02 Mar 2019 18:17:18 -0000

On 3/2/19 8:30 AM, Juliusz Chroboczek wrote:
>> What I meant is that homenet router protocols are v6 only.
> No, they're not.
>
> Both HNCP and Babel carry their control traffic over link-local IPv6, but
> they support both IPv4 and IPv6 with almost equal functionality.
>
> (The only significant difference is the treatment of border routers, which
> are assumed to be doing NAT in IPv4 and stateless routing in IPv6.)

Oh, I thought the charter was for v6 only. Did that change, or am I 
misremembering?

Mike

v2.23.0 | Report a Bug | By Email