Re: [homenet] Working Group draft adoptions

<normen.kowalewski@telekom.de> Tue, 16 September 2014 12:12 UTC

Return-Path: <normen.kowalewski@telekom.de>
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 137721A0693 for <homenet@ietfa.amsl.com>; Tue, 16 Sep 2014 05:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.5
X-Spam-Level:
X-Spam-Status: No, score=-5.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_FONT_SIZE_LARGE=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652] 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 1ybbZVezPdcb for <homenet@ietfa.amsl.com>; Tue, 16 Sep 2014 05:12:10 -0700 (PDT)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E0D91A0695 for <homenet@ietf.org>; Tue, 16 Sep 2014 05:12:09 -0700 (PDT)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail91.telekom.de with ESMTP; 16 Sep 2014 14:12:07 +0200
X-IronPort-AV: E=Sophos;i="5.04,534,1406584800"; d="scan'208,217";a="531788576"
Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 16 Sep 2014 14:12:06 +0200
Received: from HE113456.emea1.cds.t-internal.com ([10.134.93.97]) by HE110889.emea1.cds.t-internal.com ([fe80::841f:f92c:15ca:8526%16]) with mapi; Tue, 16 Sep 2014 14:12:06 +0200
From: normen.kowalewski@telekom.de
To: Ray.Bellis@nominet.org.uk, homenet@ietf.org
Date: Tue, 16 Sep 2014 14:12:05 +0200
Thread-Topic: [homenet] Working Group draft adoptions
Thread-Index: Ac/Q/a8RbDzqQCXgSrqRVyQyJOf8xwAp+wDw
Message-ID: <62AA760926A38745AAF06AD7319065FD5A23946E7F@HE113456.emea1.cds.t-internal.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: multipart/alternative; boundary="_000_62AA760926A38745AAF06AD7319065FD5A23946E7FHE113456emea1_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/lxAd2mJTG5pzrJfC8bEiszx2NeI
Subject: Re: [homenet] Working Group draft adoptions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 16 Sep 2014 12:12:14 -0000

Hi,

Regarding

* draft-mglt-homenet-front-end-naming-delegation
* draft-mglt-homenet-naming-architecture-dhc-options

I think this is useful work and support its adoption.

However, I'd like to see these drafts generalized so that mechanisms to provide authorization credentials towards the DNS are not limited to only being provided via DHCP, so that the architecture could also be used within other configuration management approaches as well, e.g. via Netconf/Yang.

Thanks,

Normen Kowalewski


Deutsche Telekom AG
Group Headquarters

P.S. My apologies to the email reviewer(s), since I have needlessly clobbered your review queue with a copy of this content instead of subscribing to this list before sending it.

Re: [homenet] Working Group draft adoptions
[X]
*

From: Ray Bellis <Ray.Bellis at nominet.org.uk<mailto:Ray.Bellis@DOMAIN.HIDDEN>>
*       To: "homenet at ietf.org<mailto:homenet@DOMAIN.HIDDEN> Group" <homenet at ietf.org<mailto:homenet@DOMAIN.HIDDEN>>
*       Date: Wed, 3 Sep 2014 13:38:16 +0000
*       List-id: <homenet.ietf.org>
[X]
This email commences a two week period for comments relating to the adoption of the following drafts by the HOMENET Working Group, as promised during our WG session in Toronto:

  draft-pfister-homenet-prefix-assignment<http://datatracker.ietf.org/doc/draft-pfister-homenet-prefix-assignment/>
  draft-mglt-homenet-front-end-naming-delegation<http://datatracker.ietf.org/doc/draft-mglt-homenet-front-end-naming-delegation/>
  draft-mglt-homenet-naming-architecture-dhc-options<http://datatracker.ietf.org/doc/draft-mglt-homenet-naming-architecture-dhc-options/>

If you have any comments please reply to this message, but please do not mix up comments on the PA draft and the two Naming drafts in a single reply.

thanks,

Ray and Mark