RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt

"David Levi" <dlevi@nortelnetworks.com> Thu, 06 January 2005 16:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18729; Thu, 6 Jan 2005 11:04:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmaKB-0000Lz-9U; Thu, 06 Jan 2005 11:17:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cma0A-00011z-CU; Thu, 06 Jan 2005 10:56:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmZwe-0008Jl-Dv for bridge-mib@megatron.ietf.org; Thu, 06 Jan 2005 10:53:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17663 for <bridge-mib@ietf.org>; Thu, 6 Jan 2005 10:53:02 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cma9R-0001pN-FA for bridge-mib@ietf.org; Thu, 06 Jan 2005 11:06:18 -0500
Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j06FqKW25767; Thu, 6 Jan 2005 10:52:20 -0500 (EST)
Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19) id <WKMBF8RZ>; Thu, 6 Jan 2005 07:52:20 -0800
Message-ID: <0A11633F61BD9F40B43ABCC694004F93043BD0BA@zsc3c026.us.nortel.com>
From: David Levi <dlevi@nortelnetworks.com>
To: 'John Flick' <john.flick@hp.com>
Subject: RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
Date: Thu, 06 Jan 2005 07:52:19 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0870727311=="
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168

John,

>> 2. References to RFC 1493 should refer to the updated version
>>     in draft-ietf-bridge-bridgemib-smiv2-07.txt.
>> DBL> I don't think it makes sense to change this, since these 
>> DBL> references will just need to be updated to the new RFC number for 
>> DBL> draft-ietf-bridge-bridgemib-smiv2-07.txt when it is published as 
>> DBL> an RFC.
>
>Making this change would help the RFC editor find the places that need to
be updated to refer
>to the new RFC when published, as well as alerting the RFC editor to the
dependency between
>these two drafts in case one gets approved by the IESG before the other.

I still don't like the idea of changing references to an RFC into references
to an ID.
How about if we just change 1493 to XXXX throughout the doc, and add a note
to the
RFC editor somewhere that these XXXX's need to be changed to the appropriate
RFC #
after the -smiv2- draft is published as an RFC?

-Dave
_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib