Re: [OPSAWG] [Errata Verified] RFC7630 (4509)

Benoit Claise <bclaise@cisco.com> Fri, 23 October 2015 09:28 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4877E1B3391 for <opsawg@ietfa.amsl.com>; Fri, 23 Oct 2015 02:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 AIwRhtokiEpn for <opsawg@ietfa.amsl.com>; Fri, 23 Oct 2015 02:28:10 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4DEB1B33D2 for <opsawg@ietf.org>; Fri, 23 Oct 2015 02:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13923; q=dns/txt; s=iport; t=1445592490; x=1446802090; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=2hsGWi3cCqUIstCHm+Qympp8oeL0WxqZ7VtOcpxSX58=; b=CctNKo5f0q/s8BTMckpj2chEwmCP22afdvF4MPSBsF3d6gHQ4QpVPXGo uBSCqfwPxHNez3Kkvhsq16jANA/v+eHJOiNYczuIH9NpY4PRBpEN/LMjd 2CpWDgQCDcXl52Z9l7SY52hYJd/HC3VCzgu7x/bioY5Zv1hT2GeQZoA6S E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwBAAs/SlW/xbLJq1EGoJpgSFvtQeLBhcBC4UwSgKCEQEBAQEBAYELhDIBAQEDAQEBAWsEBgEFBwQLFQELFg8JAwIBAgEVMAYBDAYCAQEFEIgPCA07xHsBAQEBAQEBAQEBAQEBAQEBAQEBAQEYhneEfoE9gy4iB4QuBYdAjmuFGYgFgVhIhniKQ4hLY4IRDRCBVzw0AROGLwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,186,1444694400"; d="scan'208,217";a="605866841"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2015 09:27:44 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t9N9ReUl021552; Fri, 23 Oct 2015 09:27:41 GMT
To: "t.petch" <ietfc@btconnect.com>, Johannes Merkle <johannes.merkle@secunet.com>, manfred.lochter@bsi.bund.de
References: <20151020091258.5C26A182534@rfc-editor.org> <56260809.9040501@cisco.com> <043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <5629FD77.6080107@cisco.com>
Date: Fri, 23 Oct 2015 11:27:19 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net>
Content-Type: multipart/alternative; boundary="------------030602040309070608020901"
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/GwsLkupMhVFT_S5AQqlOiMm0Uks>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] [Errata Verified] RFC7630 (4509)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2015 09:28:14 -0000

Tom,
> ---- Original Message -----
> From: "Benoit Claise" <bclaise@cisco.com>
> To: "RFC Errata System" <rfc-editor@rfc-editor.org>;
> <johannes.merkle@secunet.com>; <manfred.lochter@bsi.bund.de>
> Cc: <opsawg@ietf.org>
> Sent: Tuesday, October 20, 2015 10:23
>
>
>> Dear all,
>>
>> The facts:
>> - The MIB doctors advised not to publish MIB modules under snmpModules
>> any longer. IANA updated the registry information. See
>>
> http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
> s-61
>> - RFC 7360 is published with a mistake. The MIB module should have
> been
>> published under mib-2.235 (as advised by the MIB doctors) but the
>> document mentions: snmpModules.235
> Benoit
>
> Mutter, mutter: it is a shame that the MIB Doctors did not tell us of
> this change!
This discussion was actually triggered by IANA when it tried to figure 
out the registration procedures for SMI SNMPv2 snmpModules Codes 
registry ... in relation to this draft. The MIB doctors and I were involved.

> I carefully checked the I-D when it first appeared and was satisfied
> that the assignment was in exactly the right place, using all the
> information available to me so I think that the I-D was spot on.  And
> that it remained correct thoughout its life.
>
> And of course we are now wasting valuable resources making a 'right'
> 'wrong'!
I share the pain, trust me.
>
> Is there anything else we have not been told, by e-mail, RFC or I-D,
> that might waste our time in future:-(
I don't know what I don't know.
However, when a problem is discovered, it's generally solved. In this 
case, see the update at 
http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number 
s-61, e.g. "[No more registrations accepted ]"

Regards, Benoit
>
> Tom Petch
>
>> - The IANA registry is actually correct. snmpUsmHmacSha2MIB is under
>> mib-2.235
>> See http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml
>> - Solving this issue with an errata doesn't work: indeed MIB modules
> are
>> extracted from RFC, and used within scripts.
>>
>> Discussing with Michelle (IANA) and the IESG, we had no other choices
>> than obsoleting this RFC and re-issuing a new one. Hence this errata
> and
>> draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.
>>
> <http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-n
> ew/>
>> One change to keep in mind for the next version:
>> OLD:
>>
>>          REVISION    "201508130000Z"       -- 13 August 2015, midnight
>>          DESCRIPTION "Initial version, published asRFC 7630
> <https://tools.ietf.org/html/rfc7630>"
>>      ::= { snmpModules 235 }
>>
>> NEW:
>>
>>          REVISION     ... new date
>>          DESCRIPTION "Initial version, published asRFC xxxx
> <https://tools.ietf.org/html/rfc7630>"
>>      ::= { mib-2 235 }
>>
>> The way forward is to publish a new draft ASAP with the above
>> correction, to have a one week IETF LC, and to publish the new RFC. At
>> that point (and not before because we don't have a replacement RFC),
> we
>> will obsolete RFC 7360.
>>
>> Regards, Benoit
>>> The following errata report has been verified for RFC7630,
>>> "HMAC-SHA-2 Authentication Protocols in the User-based Security
> Model (USM) for SNMPv3".
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=7630&eid=4509
>>>
>>> --------------------------------------
>>> Status: Verified
>>> Type: Technical
>>>
>>> Reported by: Johannes Merkle <johannes.merkle@secunet.com>
>>> Date Reported: 2015-10-20
>>> Verified by: Benoit Claise (IESG)
>>>
>>> Section: 8 and 10
>>>
>>> Original Text
>>> -------------
>>> snmpModules 235
>>>
>>> Corrected Text
>>> --------------
>>> mib-2 235
>>>
>>> Notes
>>> -----
>>> IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by
> the MIB doctors), but the document mentions snmpModules.235
>>> --------------------------------------
>>> RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
>>> --------------------------------------
>>> Title               : HMAC-SHA-2 Authentication Protocols in the
> User-based Security Model (USM) for SNMPv3
>>> Publication Date    : October 2015
>>> Author(s)           : J. Merkle, Ed., M. Lochter
>>> Category            : PROPOSED STANDARD
>>> Source              : Operations and Management Area Working Group
>>> Area                : Operations and Management
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>> .
>>>
>>
>
> ------------------------------------------------------------------------
> --------
>
>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>>
> .
>