Re: [homenet] Kathleen Moriarty's Discuss on draft-ietf-homenet-hncp-09: (with DISCUSS)

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 19 November 2015 06:49 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C53B1A8A12 for <homenet@ietfa.amsl.com>; Wed, 18 Nov 2015 22:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 h0G4B-ETqCjI for <homenet@ietfa.amsl.com>; Wed, 18 Nov 2015 22:49:06 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (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 4B8D71A8A3F for <homenet@ietf.org>; Wed, 18 Nov 2015 22:49:06 -0800 (PST)
Received: by pacej9 with SMTP id ej9so71271998pac.2 for <homenet@ietf.org>; Wed, 18 Nov 2015 22:49:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=PdPCURRMX6/BfezsiEIP6hS/8aTZSmyrTIXCAE0Zi04=; b=Ns0cA8Qift3fVar9y0Bo9asuHm/Qdj+hMdX4eiueahdmAjCIw3ycuA72HDh4xRIxP+ jkms7Nt/DNwl/AGu9sA4TV41WHj3gTv/XSJUi4D/g1SxHeO+YoWIfOxOw84nll/q1zHh G+tSN/wo6blFWwwjB4Fuj4SqYQsS3/6l4jZYJ2QXM9MdivMPfOFHicSjNN41MjAUzyZs QuM/Xk0Y84gc3VVd0kPWZW1BQRomONQi7+4qBmrs48o8LbdhgZdHnB1/UbdWO1b4HC2F KOxuR+A4ke16AYq2J7bqddV05q3IE2jWlMIhWNYwxPoScYJ+4eULdHaHqQke7S80+VVS YIWA==
X-Received: by 10.68.182.197 with SMTP id eg5mr8170060pbc.114.1447915745958; Wed, 18 Nov 2015 22:49:05 -0800 (PST)
Received: from [10.0.3.190] ([97.65.203.35]) by smtp.gmail.com with ESMTPSA id kl10sm8114808pbd.31.2015.11.18.22.49.00 for <homenet@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Nov 2015 22:49:04 -0800 (PST)
To: homenet@ietf.org
References: <20151117235034.24927.22561.idtracker@ietfa.amsl.com> <87poz7qw2k.wl-jch@pps.univ-paris-diderot.fr> <1447858576159-79d51c78-b96c8c38-55ec1307@fugue.com> <8737w3qozs.wl-jch@pps.univ-paris-diderot.fr> <1447863094928-7e8a26f0-271186df-921ed76e@fugue.com> <87vb8zp903.wl-jch@pps.univ-paris-diderot.fr> <1447884395403-59f7ba69-4ce68f01-0794a090@fugue.com> <87egfmq35o.wl-jch@pps.univ-paris-diderot.fr> <1447906468890-334068f2-9e166c9c-ff8d872f@fugue.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <564D70DC.7050701@gmail.com>
Date: Thu, 19 Nov 2015 19:49:00 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <1447906468890-334068f2-9e166c9c-ff8d872f@fugue.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/iMrLzS8xWp-gzf2ttYtBV_bQRVs>
Subject: Re: [homenet] Kathleen Moriarty's Discuss on draft-ietf-homenet-hncp-09: (with DISCUSS)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Nov 2015 06:49:09 -0000

On 19/11/2015 17:14, Ted Lemon wrote:
> Wednesday, Nov 18, 2015 6:49 PM Juliusz Chroboczek wrote:
>> It's not a simple matter of sending a few mailing list messages -- it's
>> a long-term effort that consists of writing portable, open source,
>> lightweight implementations (hnetd, shncpd), of deploying HNCP ourselves
>> (Paris network, Henning's network somewhere in Germany), of getting HNCP
>> implementations into Linux and Unix distributions (OpenWRT by Steven,
>> Debian/Ubuntu soon, I'm not telling), of speaking to people at community
>> meetings (Battlemesh, IETF, CCC, FOSDEM), in short, making HNCP familiar
>> and easily available.
> 
> Sure, that's fair enough.
> 
>> (And as we're trying to communicate our message in a clear and accurate
>> manner, how helpful it is to be able to say that a feature is "mandatory
>> to implement, optional to use, but you're not allowed to #ifdef it away".)
> 
> Just to clarify, mandatory to implement doesn't mean you have to write the code.   It means the functionality has to be present in the deployed implementation so that two communicating partners can be configured to use it.   

Um, where is that defined? Is there a BCP that says that?

I don't think a protocol spec can say that feature X cannot be ifdeffed.
It can say that a protocol must be capable of X and that implementations
must therefore be capable of X. But if you tell implementors that they can't
ifdef unused stuff when building images for highly constrained nodes, I
don't think they will take you seriously.

   Brian


Mandatory to use means that the functionality has to be used at all times.
> 
> 
> --
> Sent from Whiteout Mail - https://whiteout.io
> 
> My PGP key: https://keys.whiteout.io/mellon@fugue.com
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>