[OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement for configuration by SNMP

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Mon, 06 November 2006 20:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhB5b-00051n-HX; Mon, 06 Nov 2006 15:29:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhB5a-00050m-PB; Mon, 06 Nov 2006 15:29:02 -0500
Received: from ihemail3.lucent.com ([135.245.0.37]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhB5Y-0003UG-GB; Mon, 06 Nov 2006 15:29:02 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id kA6KSXOW027823; Mon, 6 Nov 2006 14:28:33 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <R9BLYMSB>; Mon, 6 Nov 2006 21:28:32 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AEB7B30@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, MIB Doctors <mib-doctors@ietf.org>, ops-nm@ietf.org
Date: Mon, 06 Nov 2006 21:28:22 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: Mark Townsley <townsley@cisco.com>
Subject: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement for configuration by SNMP
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

I can live with a a MUST allow for SNMP config, if that is
what the WG consciously decided for (has consensus on).

I saw DBH comment too. I can also live with a SHOULD,
but it does make the potential interoperability less sure.
The reason DBH mentions sounds fine, but they can always
relax (i.e. update the RFC0 if/when in the future we have
a new/other/alternative/better protocol available.

my 2 cents

Bert


> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Sunday, November 05, 2006 09:37
> To: MIB Doctors; ops-nm@ietf.org
> Cc: Mark Townsley
> Subject: [MIB-DOCTORS] Mandatory Requirement for 
> configuration by SNMP 
> 
> 
> 
> 
> I would like to hear the opinion of the MIB Doctors and OPS-NM folks
> concerning the following. The Access Node Control Protocol (ANCP)
> framework document
> http://www.ietf.org/internet-drafts/draft-ietf-ancp-framework-
> 00.txt has
> a management-related requirements section (Section 6) which is quite
> nice. The issue is that the section includes MUST requirements for
> configuration by SNMP. 
> 
> Is this what we want at this stage of evolution of the IETF management
> protocols, or should we advice them to do something different? 
> 
> Dan
> 
> 
>  
> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www1.ietf.org/mailman/listinfo/mib-doctors
> 

_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm