changes to the network management section in node requirements
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Fri, 20 August 2010 14:48 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D38D63A6A77 for <ipv6@core3.amsl.com>; Fri, 20 Aug 2010 07:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.821
X-Spam-Level:
X-Spam-Status: No, score=-101.821 tagged_above=-999 required=5 tests=[AWL=0.428, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQmi2rUrUfzz for <ipv6@core3.amsl.com>; Fri, 20 Aug 2010 07:48:55 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id AFF7D3A6950 for <ipv6@ietf.org>; Fri, 20 Aug 2010 07:48:55 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id F240BC0002 for <ipv6@ietf.org>; Fri, 20 Aug 2010 16:49:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id bXHrvuBp8JGW; Fri, 20 Aug 2010 16:49:28 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 29FEDC0008; Fri, 20 Aug 2010 16:49:28 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 28EE51453960; Fri, 20 Aug 2010 16:49:12 +0200 (CEST)
Date: Fri, 20 Aug 2010 16:49:11 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: ipv6@ietf.org
Subject: changes to the network management section in node requirements
Message-ID: <20100820144910.GA8526@elstar.local>
Mail-Followup-To: ipv6@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Aug 2010 14:48:57 -0000
Hi, I like to suggest some changes to section 12 "Network Management" of <http://tools.ietf.org/html/draft-ietf-6man-node-req-bis-05>. --- OLD Network Management MAY be supported by IPv6 nodes. However, for IPv6 nodes that are embedded devices, network management may be the only possible way of controlling these nodes. NEW IPv6 nodes may support network management via the Simple Network Management Protocol version 3 (SNMPv3) [RFC3411]. For IPv6 nodes that are embedded devices, network management via SNMPv3 may be the only possible way of controlling these nodes. Rationale: I think it is important to provide a explicit references to SNMPv3 to make it clear that SNMPv3 is the SNMP version to be implemented. --- OLD IP Forwarding Table MIB [RFC4292] SHOULD be supported by nodes that support an SNMP agent. NEW The IP-FORWARD-MIB module [RFC4292] SHOULD be supported by nodes that support an SNMP agent. Rationale I believe it is clearer to list the MIB module name instead of a paraphrase of the respective RFC title. --- OLD IP MIB [RFC4293] SHOULD be supported by nodes that support an SNMP agent. NEW The IP-MIB module [RFC4293] SHOULD be supported by nodes that support an SNMP agent. Implementation of the IPv6-MIB module [RFC2465] is only recommended for backward compatibility reasons since [RFC2465] has been obsoleted by [RFC4293]. Rationale: I believe it is clearer to list the MIB module name instead of a paraphrase of the respective RFC title. The second sentence should take care of ongoing confusion where people think they should implement the IPV6-MIB module for IPv6 nodes. --- /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Ed Jankiewicz
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Thomas Narten
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Basavaraj.Patil
- changes to the network management section in node… Juergen Schoenwaelder
- Comments on Section 9.0 (Mobility) - draft-ietf-6… Sri Gundavelli
- RE: Comments on Section 9.0 (Mobility) -draft-iet… Templin, Fred L
- RE: Comments on Section 9.0 (Mobility)-draft-ietf… Templin, Fred L
- Re: Comments on Section 9.0 (Mobility) -draft-iet… Basavaraj.Patil
- RE: Comments on Section 9.0 (Mobility) -draft-iet… Templin, Fred L
- Re: changes to the network management section in … Thomas Narten
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Behcet Sarikaya
- Re: changes to the network management section in … Juergen Schoenwaelder
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Sri Gundavelli
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Thomas Narten
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Randy Bush
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Alexandru Petrescu
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Alexandru Petrescu
- Re: Comments on Section 9.0 (Mobility) - draft-ie… Vijay Devarapalli