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

"Haleplidis Evangelos" <ehalep@gmail.com> Wed, 22 October 2014 12:54 UTC

Return-Path: <ehalep@gmail.com>
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 4E9FD1A90F3 for <forces@ietfa.amsl.com>; Wed, 22 Oct 2014 05:54:52 -0700 (PDT)
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 kuQW-b-DRqqT for <forces@ietfa.amsl.com>; Wed, 22 Oct 2014 05:54:50 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 462FB1A8BC4 for <forces@ietf.org>; Wed, 22 Oct 2014 05:54:50 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id y10so3625457wgg.3 for <forces@ietf.org>; Wed, 22 Oct 2014 05:54:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=8soaDj3cU3gdYlGeZIaVtJEPzMrexwxvGGVPreYPtow=; b=r84N0iyHrqkmXQazlblWfxyPuW/pSakh1GiNg8hNuGnPSHGytpyadxZJZp/KQ3InlS Z+LqVUEb97EfZybDIRfIj4NVPyIHGEwi24Tg8DYZPTm2SvTBSUo2/ow+Nbmx2xAedX2j k9GWJgJYHlWCTL3Ol4yj8Ld3zOO6jWYLEAZB+E5kA3J20tJWZ0Dipq6UI0eP1V4l9hGm 9CmdNhmDo90jdSdBNu03PouqDmwnmJYxyi7xdITW82QlDTKdqdFKGw5nmhXTdrDCgPAg hQKcW+Vynzxw9Fo/ZFAh9FJ8o7xdHafjttQcLtBZI16bFhF+NaWw/SZWcvWpDni7VL92 WxNw==
X-Received: by 10.180.210.167 with SMTP id mv7mr5420100wic.15.1413982488959; Wed, 22 Oct 2014 05:54:48 -0700 (PDT)
Received: from EhalepXPS (ppp079166008118.access.hol.gr. [79.166.8.118]) by mx.google.com with ESMTPSA id lp8sm1839167wic.17.2014.10.22.05.54.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 22 Oct 2014 05:54:48 -0700 (PDT)
From: Haleplidis Evangelos <ehalep@gmail.com>
To: 'Julian Reschke' <julian.reschke@gmx.de>, draft-ietf-forces-model-extension@tools.ietf.org, forces@ietf.org
References: <54475790.7000609@gmx.de> <54475DC7.4040402@gmx.de>
In-Reply-To: <54475DC7.4040402@gmx.de>
Date: Wed, 22 Oct 2014 15:54:46 +0300
Message-ID: <00e301cfedf7$5d323430$17969c90$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/t1nsIJ4ebQda2Scy67x3Hx1QbdAAHmXUw
Content-Language: el
Archived-At: http://mailarchive.ietf.org/arch/msg/forces/CUvq2hcV6NGXX8s77Bt1aIcGhZ4
Cc: 'Amanda Baber' <amanda.baber@icann.org>, 'Graham Klyne' <GK@ninebynine.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: Wed, 22 Oct 2014 12:54:52 -0000

Greetings Julian,

I'm a little confused on why you think there is no backwards compatibility.

LFB definitions that use the 1.0 namespace are valid in the 1.1 namespace.
LFB definitions that use the 1.1 namespace are not always valid with the 1.0
namespace.

That means that a software that understands LFBs in the 1.1 namespace can,
without any change, understand older LFBs. That was the end goal.
Software that understand the 1.0 namespace (even if we didn't change the
namespace) will, of course, have trouble parsing the new xml if the
extensions are used.

This document did not change any LFB definitions developed with the 1.0
namespace. As there was no reason for that as 1.1 is backwards compatible
with 1.0
The namespace is a way to distinguish the different versions and notify that
in the 1.1 namespace these extensions apply.

Thus, I don't understand why old software will be needed to change in order
to understand the old format. 
For the new format, of course you'll have to change it. But for the new
format you'd definitely had to update the software if you want to be
compatible with the 1.1 namespace, so I don't see the issue.

Is something I miss?

Regards,
Evangelos Haleplidis.

> -----Original Message-----
> From: forces [mailto:forces-bounces@ietf.org] On Behalf Of Julian
> Reschke
> Sent: Wednesday, October 22, 2014 10:33 AM
> To: draft-ietf-forces-model-extension@tools.ietf.org; forces@ietf.org
> Cc: Amanda Baber; Graham Klyne
> Subject: Re: [forces] draft-ietf-forces-model-extension
> 
> On 2014-10-22 09:06, Julian Reschke wrote:
> > Hi there.
> >
> > I was reviewing the namespace registration and have one question.
> >
> > The draft says
> >
> > "The changes introduced in this memo do not alter the protocol and
> > retain backward compatibility with older LFB models."
> >
> > If this is the case, why is a new XML namespace even desirable?
> >
> > (Other than that, I'm sort of ok with the registration, but it
> strikes
> > me that assigning a new namespace is a very bad idea).
> >
> > Best regards, Julian
> 
> Thinking about that some more: if a new XML namespace is used, the
> format definitively is *not* backwards compatible anymore (every piece
> of software that understood the old format will have to be rewritten).
> 
> Best regards, Julian
> 
> _______________________________________________
> forces mailing list
> forces@ietf.org
> https://www.ietf.org/mailman/listinfo/forces