IETF Logo Mail Archive

Re: [homenet] standard way of configuring homenets

"STARK, BARBARA H" <bs7652@att.com> Wed, 25 July 2018 18:00 UTC

Return-Path: <bs7652@att.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 C6966131038 for <homenet@ietfa.amsl.com>; Wed, 25 Jul 2018 11:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 paiuNOJoB26E for <homenet@ietfa.amsl.com>; Wed, 25 Jul 2018 11:00:44 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 E60AD131008 for <homenet@ietf.org>; Wed, 25 Jul 2018 11:00:43 -0700 (PDT)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w6PHu27Z006471; Wed, 25 Jul 2018 14:00:42 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049458.ppops.net-00191d01. with ESMTP id 2kew7tsbtw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 25 Jul 2018 14:00:41 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w6PI0dKt014377; Wed, 25 Jul 2018 14:00:41 -0400
Received: from zlp30487.vci.att.com (zlp30487.vci.att.com [135.47.91.176]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w6PI0Wau013914; Wed, 25 Jul 2018 14:00:32 -0400
Received: from zlp30487.vci.att.com (zlp30487.vci.att.com [127.0.0.1]) by zlp30487.vci.att.com (Service) with ESMTP id 383284014041; Wed, 25 Jul 2018 18:00:32 +0000 (GMT)
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (unknown [130.8.218.154]) by zlp30487.vci.att.com (Service) with ESMTPS id 25A4E4014040; Wed, 25 Jul 2018 18:00:32 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.81]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0408.000; Wed, 25 Jul 2018 14:00:31 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, 'Ted Lemon' <mellon@fugue.com>, homenet <homenet@ietf.org>
Thread-Topic: [homenet] standard way of configuring homenets
Thread-Index: AQHUI5gcP53omUcFxUqCducdRw8FHKSfLkiAgAAQ+ICAATuOAP//vS8A
Date: Wed, 25 Jul 2018 18:00:30 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DE52A2D@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <27765.1532468911@localhost> <CAPt1N1mO8KFH+M-bq7LKqQcjtyigUPwdchMA11U_vPXYTzcNSw@mail.gmail.com> <2D09D61DDFA73D4C884805CC7865E6114DE51281@GAALPA1MSGUSRBF.ITServices.sbc.com> <16718.1532540812@localhost>
In-Reply-To: <16718.1532540812@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.61.166.63]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-25_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=680 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1807250190
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/5gvx-pP6QpPpqQfb8Z4m9-bTTCQ>
Subject: Re: [homenet] standard way of configuring homenets
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 25 Jul 2018 18:00:54 -0000

> STARK, BARBARA H <bs7652@att.com> wrote:
>     > <individual hat> Since homenet is supposed to be about an unmanaged
>     > network, and configuration via a management protocol requires
> somebody
>     > who knows what they’re doing, it doesn’t fall within my interpretation
>     > of the charter.
> 
> I don't think that management requires somebody who knows what they
> they are doing...  :-)
> 
> I'm thinking along the lines of being able to *backup* the configuration and
> restore it.   You may be right that it's out of charter regardless.
> 
> I think that the developers of homenet products need to be able to get
> telemetry about what went wrong: so at the least, *we* need to be able to
> debug what went wrong.

I think we could do something for config backup (and restoration) and supplying logs and statistics in a way that would not give me the heebie-jeebies (by enabling a fully-functional management interface). 
I still really like NetJSON (netjson.org) as a mechanism for supplying read-only statistics, logs, and config info. I think if we creating some custom NetJSON modules and getting a DNS-SD service name would be really simple and pretty flexible.
For backup, I think a device could create, name, and encrypt its own backup file, and would just need some place to put it. That backup store wouldn't need to be able to log into the device, otherwise configure the device, or be responsible for pulling these backups. 
Barbara

v2.23.0 | Report a Bug | By Email