Re: [forces] draft-ietf-forces-model-extension

Julian Reschke <julian.reschke@gmx.de> Mon, 27 October 2014 20:05 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52A3F1AD3D7 for <forces@ietfa.amsl.com>; Mon, 27 Oct 2014 13:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 2_hyq8Q6qCM5 for <forces@ietfa.amsl.com>; Mon, 27 Oct 2014 13:05:49 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76C531AD3F2 for <forces@ietf.org>; Mon, 27 Oct 2014 13:05:49 -0700 (PDT)
Received: from [192.168.2.160] ([93.217.112.240]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Lpspj-1YKweS2dvz-00fhGA; Mon, 27 Oct 2014 21:05:23 +0100
Message-ID: <544EA57F.3020906@gmx.de>
Date: Mon, 27 Oct 2014 21:05:19 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Haleplidis Evangelos <ehalep@gmail.com>, 'Joel' <joel@stevecrocker.com>, 'Jamal Hadi Salim' <hadi@mojatatu.com>
References: <54475790.7000609@gmx.de> <54475DC7.4040402@gmx.de> <00e301cfedf7$5d323430$17969c90$@com> <5447ACC0.80904@gmx.de> <CAAFAkD8Qn95Msmnw9VqqRDHdG51bWuEc4g1a2fYwM+K61r3-Mw@mail.gmail.com> <5448F7BA.7010607@gmx.de> <54490B04.2000701@stevecrocker.com> <016101cff220$87c93720$975ba560$@com>
In-Reply-To: <016101cff220$87c93720$975ba560$@com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:itnRH3P1fJYEiMrR+mNHjx0zaRbbUD594wHjHbe9cVITU14XryW YDt2YeL1qYodHUPpWqhPTgKHWnWbZEDIskqXvwBSy/+TOkV0pZCcz/EheFfP7Po1t6o1Iq5 dplAP7mYySB5pfHti3x3AaXJMEcVczvTnn4KIB1Hwq1N8fDo0wzfnUH6IMDVOR6lylyty80 syOBB4fEPVONQFeCx6Gqw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/forces/QTx5r-n4QesxORxhEJ0idqi5OQA
Cc: 'Amanda Baber' <amanda.baber@icann.org>, forces@ietf.org, 'Graham Klyne' <GK@ninebynine.org>, draft-ietf-forces-model-extension@tools.ietf.org
Subject: Re: [forces] draft-ietf-forces-model-extension
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces/>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 2014 20:05:52 -0000

On 2014-10-27 20:59, Haleplidis Evangelos wrote:
> Greetings Julian,
>
> Apologies for the late reply.
>
> As Jamal and Joel both noted, the model does not affect the protocol at all.
>
> The change of the namespace was suggested by Adrian during his AD review
> (https://www.ietf.org/mail-archive/web/forces/current/msg04837.html) which I
> agreed to. I am more comfortable with keeping the new namespace as that will
> clearly specify that extensions are expected.
>
> Now, how about if we added the following text in the document. Would that
> address your concerns?
> 	
> "The extensions described in this document, are backwards compatible in
> terms of the operation of the ForCES protocol.  In terms of the XML, any
> definitions that were valid under the old name space are valid under the new
> namespace.  It is to be noted that any auxiliary tools that are processing
> xml definitions written under both namespaces will need to be able to
> understand both."
>
> Regards,
> Evangelos Haleplidis.

Hi,

that's indeed an improvement. Go ahead!

Best regards, Julian