Re: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt

"DE CNODDER, STEFAAN (STEFAAN)" <stefaan.de_cnodder@alcatel-lucent.com> Wed, 20 March 2013 09:10 UTC

Return-Path: <stefaan.de_cnodder@alcatel-lucent.com>
X-Original-To: ancp@ietfa.amsl.com
Delivered-To: ancp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2DEB21F8667 for <ancp@ietfa.amsl.com>; Wed, 20 Mar 2013 02:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 N3R4K9JL4r-O for <ancp@ietfa.amsl.com>; Wed, 20 Mar 2013 02:10:56 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id DB69F21F87B6 for <ancp@ietf.org>; Wed, 20 Mar 2013 02:10:55 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r2K9As9G020181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 20 Mar 2013 04:10:55 -0500 (CDT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r2K9Anhi026385 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Mar 2013 05:10:54 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 20 Mar 2013 05:10:50 -0400
Received: from FR711WXCHMBA06.zeu.alcatel-lucent.com ([169.254.2.68]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Wed, 20 Mar 2013 10:10:33 +0100
From: "DE CNODDER, STEFAAN (STEFAAN)" <stefaan.de_cnodder@alcatel-lucent.com>
To: "Markus.Freudenberger@t-systems.com" <Markus.Freudenberger@t-systems.com>
Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt
Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOA=
Date: Wed, 20 Mar 2013 09:10:33 +0000
Message-ID: <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com>
References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <F51C24472ABFED4AA5FE7C5F7EF98E100C1882765E@HE113484.emea1.cds.t-internal.com>
In-Reply-To: <F51C24472ABFED4AA5FE7C5F7EF98E100C1882765E@HE113484.emea1.cds.t-internal.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 09:10:57 -0000

Hi Markus,

Thanks for the feedback.  For issue 1, the trap could be generated because the row is deleted from both tables.  This means that the ancpAnSessionConfigSessionId in the trap has in this case no relevant information, and might point to a wrong or non-existing entry in the table.  So I am not sure if adding this to the trap is good.

For issue 2, the state "down" is actually detailed in the next sentences: it can be down because the session is deleted, or the session is a state other than the estab state.  The estab state you find back in ancpAnCurrentSessionState.

regards,
Stefaan


-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Markus.Freudenberger@t-systems.com
Sent: dinsdag 19 maart 2013 13:23
To: internet-drafts@ietf.org; i-d-announce@ietf.org
Cc: ancp@ietf.org
Subject: Re: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt

Hi all,

Issue 1:
there are two objects for identifying an ancp sessions in the access node.    
1. ancpAnSessionConfigSessionId 
2. ancpAnCurrentSessionAnInstance
The first one identifies rows in the ancpAnSessionConfigTable and in the ancpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjacency Message itself and is an attribute in the ancpAnCurrentSessionTable.

Proposal:
Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSessionUp/ancpSessionDown traps as this is the clear reference to both tables ancpAnSessionConfigTable and ancpAnCurrentSessionTable. 

Issue 2:
The definition of the ancpSessionDown trap says: "This notification is generated whenever an ANCP session goes down." bute the state 'down' is not explicitely defined in the status attribute "ancpAnCurrentSessionState" which triggers the generation of the trap.

Proposal:
Define the state 'down' in the attribute ancpAnCurrentSessionState or make the relation from the different states in the ancpAnCurrentSessionState to the phrase 'down' resp. 'operational down' more clear in the description of the ancpSessionDown trap.

Thanks and regards
Markus


-----Ursprüngliche Nachricht-----
Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von internet-drafts@ietf.org
Gesendet: Dienstag, 29. Januar 2013 09:06
An: i-d-announce@ietf.org
Cc: ancp@ietf.org
Betreff: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Access Node Control Protocol Working Group of the IETF.

	Title           : Access Node Control Protocol (ANCP) MIB module for Access Nodes
	Author(s)       : Stefaan De Cnodder
                          Moti Morgenstern
	Filename        : draft-ietf-ancp-mib-an-10.txt
	Pages           : 39
	Date            : 2013-01-29

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols.  In particular it defines
   objects for managing access nodes that are using the Access Node
   Control Protocol (ANCP).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ancp-mib-an

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-ancp-mib-an-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-ancp-mib-an-10


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp