IETF Logo Mail Archive

Re: draft-jennings-app-dns-update-00

Patrik Fältström <patrik@frobbit.se> Fri, 11 July 2008 07:01 UTC

Return-Path: <apps-discuss-bounces@ietf.org>
X-Original-To: apps-discuss-archive@ietf.org
Delivered-To: ietfarch-apps-discuss-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F378A28C145; Fri, 11 Jul 2008 00:01:47 -0700 (PDT)
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA1E128C137 for <apps-discuss@core3.amsl.com>; Fri, 11 Jul 2008 00:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+Z1PaCeMa69 for <apps-discuss@core3.amsl.com>; Fri, 11 Jul 2008 00:01:46 -0700 (PDT)
Received: from frobbit.se (klara.frobbit.se [85.30.129.37]) by core3.amsl.com (Postfix) with ESMTP id C8BA328C14B for <apps-discuss@ietf.org>; Fri, 11 Jul 2008 00:01:14 -0700 (PDT)
Received: from [85.30.128.225] (account paf HELO [192.168.1.194]) by frobbit.se (CommuniGate Pro SMTP 5.0.10) with ESMTPA id 6960875; Fri, 11 Jul 2008 09:01:30 +0200
Message-Id: <3426B6B5-6C93-45FD-B5F9-4C193263EDED@frobbit.se>
From: Patrik Fältström <patrik@frobbit.se>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <26C42831-8209-4CF0-9101-F4DB97428EFA@cisco.com>
Mime-Version: 1.0 (Apple Message framework v928)
Subject: Re: draft-jennings-app-dns-update-00
Date: Fri, 11 Jul 2008 09:01:30 +0200
References: <20080707024501.AE0A33A6947@core3.amsl.com> <89A47DA0-8E2F-4247-A21F-E9B1777A0856@cisco.com> <20080708055828.GA6547@x27.adm.denic.de> <26C42831-8209-4CF0-9101-F4DB97428EFA@cisco.com>
X-Mailer: Apple Mail (2.928)
Cc: Peter Koch <pk@DENIC.DE>, apps-discuss@ietf.org
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: apps-discuss-bounces@ietf.org
Errors-To: apps-discuss-bounces@ietf.org

On 9 jul 2008, at 03.30, Cullen Jennings wrote:

>> 1) We do have Dynamic Updates and EPP as "provisioning" protocols.
>>   Which deficiencies is this approach trying to address in  
>> particular?
>
> Clearly this is the fundamental question in trying to decide what to  
> do with this draft. This approach is very simplistic with less  
> features than other but approaches. However, an simple HTTP approach  
> seems to be one that an is gaining a fair amount of adoption in  
> actual deployments.

I would like to know more what you imply with "simple", and urge you  
to add that research in the draft.

I.e. "why not use DNS dynamic update" section would make sense.

    Patrik

_______________________________________________
Apps-Discuss mailing list
Apps-Discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email