IETF Logo Mail Archive

Re: [mile] What is Version (5070bis, enum, etc.)

"Stoecker, Paul" <Paul.Stoecker@rsa.com> Wed, 13 March 2013 16:19 UTC

Return-Path: <Paul.Stoecker@rsa.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE4521F85FC for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 09:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjLjMHXUY+or for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 09:19:43 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3452121F85EB for <mile@ietf.org>; Wed, 13 Mar 2013 09:19:43 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DGJeMZ016319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Mar 2013 12:19:41 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 13 Mar 2013 12:19:28 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DGJRex012088; Wed, 13 Mar 2013 12:19:27 -0400
Received: from MXHUB104.corp.emc.com (10.253.58.16) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 13 Mar 2013 12:19:27 -0400
Received: from MX103CL01.corp.emc.com ([169.254.5.163]) by MXHUB104.corp.emc.com ([::1]) with mapi id 14.02.0342.003; Wed, 13 Mar 2013 12:19:26 -0400
From: "Stoecker, Paul" <Paul.Stoecker@rsa.com>
To: Eric Burger <eburger-l@standardstrack.com>
Thread-Topic: [mile] What is Version (5070bis, enum, etc.)
Thread-Index: AQHOH/9oWuM9Me0MX0qmOPzlbcI5BZijzREa
Date: Wed, 13 Mar 2013 16:19:27 +0000
Message-ID: <73930A69-4224-4B73-82D5-A23F411F2179@rsa.com>
References: <75782EF7-F21F-44DD-929C-AF4A37BDD860@standardstrack.com>, <384B5B5D-09AE-4A6A-AFCA-93DA799E014E@standardstrack.com>
In-Reply-To: <384B5B5D-09AE-4A6A-AFCA-93DA799E014E@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: MILE IETF <mile@ietf.org>
Subject: Re: [mile] What is Version (5070bis, enum, etc.)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 16:19:44 -0000

Eric,

Thanks.  This is something that I will correct after the IETF meeting as I am sure that I missed other items and there are some other changes that we will be discussing that will need to be incorporated.  This is my rookie year as an editor, so I really appreciate the feedback.

Regards,

Paul

Sent from my iPhone

On Mar 13, 2013, at 11:28 AM, "Eric Burger" <eburger-l@standardstrack.com> wrote:

> 5070, 5070bis, and ENUM all use a 'version' attribute. 
> 
> Section 3.1 of both 5070 and 5070bis define version as:
>     Required.  STRING.  The IODEF specification version number to
>     which this IODEF document conforms.  The value of this attribute
>     MUST be "1.00"
> 
> OK, I will bite. The schema of 5070 and 5070bis are different. How do I know I have a 5070bis schema if it says <IODEF-Document version="1.00">? It is totally non-normative, but I suppose someone who is clueless about protocols would look at the double super secret <documentation> tag that says "Incident Object Description Exchange Format v1.00, see RFC 5070" for a 5070 document and "Incident Object Description Exchange Format v1.10, RFC5070-bis" for a 5070bis document. I say "double super secret" because that string only appears in the schema but has no text describing it. Also, making a programatic decision based on XML Schema documentation is not a very smart idea.
> 
> Let me push this further. What happens if a 5070bis document has <IODEF-Document version="1.10">? 5070 and 5070bis both say… nothing. However, a good protocol writer will see the 'MUST be "1.00"' and thus will reject the document. Is this the desired behavior? If so, say so. I doubt it, but we are begging for interoperability failure if IODEF becomes successful and we enhance it in the future.
> 
> Enum reference format suffers from this as well, but I will address that in a separate email.
> 
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>

v2.23.0 | Report a Bug | By Email