From iesg-secretary@ietf.org Thu Mar 7 08:31:30 2013 Return-Path: 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 A6D0A21F8BFD; Thu, 7 Mar 2013 08:31:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.542 X-Spam-Level: X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] 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 P6sCgfabOPXW; Thu, 7 Mar 2013 08:31:30 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 65EDF21F8CD8; Thu, 7 Mar 2013 08:31:29 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.42 Message-ID: <20130307163129.11314.36606.idtracker@ietfa.amsl.com> Date: Thu, 07 Mar 2013 08:31:29 -0800 Cc: ancp mailing list , ancp chair , RFC Editor Subject: [ANCP] Document Action: 'Applicability of Access Node Control Mechanism to PON based Broadband Networks' to Informational RFC (draft-ietf-ancp-pon-05.txt) X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Mar 2013 16:31:30 -0000 The IESG has approved the following document: - 'Applicability of Access Node Control Mechanism to PON based Broadband Networks' (draft-ietf-ancp-pon-05.txt) as Informational RFC This document is the product of the Access Node Control Protocol Working Group. The IESG contact persons are Ralph Droms and Brian Haberman. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/ Technical Summary The purpose of this document is to provide applicability of the Access Node Control mechanism to PON-based broadband access. The need for an Access Node Control mechanism between a Network Access Server (NAS) and an Access Node Complex (a combination of Optical Line Termination (OLT) and Optical Network Termination (ONT) elements) is described in a multi-service reference architecture in order to perform QoS-related, service-related and Subscriber-related operations. The Access Node Control mechanism is also extended for interaction between components of the Access Node Complex (OLT and ONT). Working Group Summary The ANCP working group was originally chartered only to cover DSL access technologies. It's application to PON was only added as a result of this draft being introduced. However, there were no issues with reaching consensus for this change and, indeed, there was significant support within the working group. The document received two working group last calls. The second was after an initial IESG review and as a result of late IPR declaration 1734. No issues were raised about the IPR declaration. Document Quality The document describes the application of an existing technology (ANCP) to a new access technology type (PON). ANCP is deployed for DSL access networks today, but is sufficiently generic and extensible to be applicable to other access technologies. I do not know of deployments of ANCP for PON. I have no other concerns about the quality of the document. The document does not specify any MIB changes or additions which would need review. Personnel Matthew Bocci is the document shepherd. Ralph Droms is the responsible AD. From iesg-secretary@ietf.org Thu Mar 7 08:31:30 2013 Return-Path: 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 D02D021F8C06 for ; Thu, 7 Mar 2013 08:31:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.543 X-Spam-Level: X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] 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 yZejqFfXi+uZ; Thu, 7 Mar 2013 08:31:30 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EAD021F8D01; Thu, 7 Mar 2013 08:31:29 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IANA X-Test-IDTracker: no X-IETF-IDTracker: 4.42 X-IETF-Draft-string: draft-ietf-ancp-pon X-IETF-Draft-revision: 05 Message-ID: <20130307163129.11314.53407.idtracker@ietfa.amsl.com> Date: Thu, 07 Mar 2013 08:31:29 -0800 Cc: ancp mailing list , ancp chair , RFC Editor Subject: [ANCP] Document Action: 'Applicability of Access Node Control Mechanism to PON based Broadband Networks' to Informational RFC (draft-ietf-ancp-pon-05.txt) X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: noreply@ietf.org List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Mar 2013 16:31:31 -0000 The IESG has approved the following document: - 'Applicability of Access Node Control Mechanism to PON based Broadband Networks' (draft-ietf-ancp-pon-05.txt) as Informational RFC This document is the product of the Access Node Control Protocol Working Group. The IESG contact persons are Ralph Droms and Brian Haberman. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/ Technical Summary The purpose of this document is to provide applicability of the Access Node Control mechanism to PON-based broadband access. The need for an Access Node Control mechanism between a Network Access Server (NAS) and an Access Node Complex (a combination of Optical Line Termination (OLT) and Optical Network Termination (ONT) elements) is described in a multi-service reference architecture in order to perform QoS-related, service-related and Subscriber-related operations. The Access Node Control mechanism is also extended for interaction between components of the Access Node Complex (OLT and ONT). Working Group Summary The ANCP working group was originally chartered only to cover DSL access technologies. It's application to PON was only added as a result of this draft being introduced. However, there were no issues with reaching consensus for this change and, indeed, there was significant support within the working group. The document received two working group last calls. The second was after an initial IESG review and as a result of late IPR declaration 1734. No issues were raised about the IPR declaration. Document Quality The document describes the application of an existing technology (ANCP) to a new access technology type (PON). ANCP is deployed for DSL access networks today, but is sufficiently generic and extensible to be applicable to other access technologies. I do not know of deployments of ANCP for PON. I have no other concerns about the quality of the document. The document does not specify any MIB changes or additions which would need review. Personnel Matthew Bocci is the document shepherd. Ralph Droms is the responsible AD. From Markus.Freudenberger@t-systems.com Tue Mar 19 05:22:47 2013 Return-Path: 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 7229821F8901; Tue, 19 Mar 2013 05:22:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 52z203n7cquX; Tue, 19 Mar 2013 05:22:46 -0700 (PDT) Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id D308221F88F7; Tue, 19 Mar 2013 05:22:44 -0700 (PDT) From: Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 19 Mar 2013 13:22:42 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 19 Mar 2013 13:22:41 +0100 To: , Date: Tue, 19 Mar 2013 13:22:39 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbg Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> In-Reply-To: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Mar 2013 12:22:47 -0000 Hi all, Issue 1: there are two objects for identifying an ancp sessions in the access node. = =20 1. ancpAnSessionConfigSessionId=20 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From stefaan.de_cnodder@alcatel-lucent.com Wed Mar 20 02:10:56 2013 Return-Path: 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 ; 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 ; 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 ; 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)" To: "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> In-Reply-To: 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" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 ancpAnSessionConf= igSessionId 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: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId=20 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From Markus.Freudenberger@t-systems.com Wed Mar 20 03:34:09 2013 Return-Path: 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 ACF1721F8488 for ; Wed, 20 Mar 2013 03:34:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 PGF710nIlhDf for ; Wed, 20 Mar 2013 03:34:09 -0700 (PDT) Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 7C64821F8481 for ; Wed, 20 Mar 2013 03:34:08 -0700 (PDT) From: Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 11:33:53 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 11:33:52 +0100 To: Date: Wed, 20 Mar 2013 11:33:52 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEA== Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2013 10:34:09 -0000 Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From stefaan.de_cnodder@alcatel-lucent.com Wed Mar 20 07:58:23 2013 Return-Path: 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 2702011E80A3 for ; Wed, 20 Mar 2013 07:58:23 -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 wGY6ZuZNDfBe for ; Wed, 20 Mar 2013 07:58:22 -0700 (PDT) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 52A1B11E80A2 for ; Wed, 20 Mar 2013 07:58:22 -0700 (PDT) Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r2KEwH07001042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 20 Mar 2013 09:58:18 -0500 (CDT) Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r2KEwErY018481 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Mar 2013 10:58:17 -0400 Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) by US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 20 Mar 2013 10:58:07 -0400 Received: from FR711WXCHMBA06.zeu.alcatel-lucent.com ([169.254.2.68]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Wed, 20 Mar 2013 15:57:47 +0100 From: "DE CNODDER, STEFAAN (STEFAAN)" To: "Markus.Freudenberger@t-systems.com" Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfww Date: Wed, 20 Mar 2013 14:57:46 +0000 Message-ID: <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: 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.35 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2013 14:58:23 -0000 Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com]=20 Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From Markus.Freudenberger@t-systems.com Wed Mar 20 08:44:56 2013 Return-Path: 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 AA9BD21F8FCF for ; Wed, 20 Mar 2013 08:44:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 RGXucuxA-Ejy for ; Wed, 20 Mar 2013 08:44:55 -0700 (PDT) Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id 26D9A21F8FB2 for ; Wed, 20 Mar 2013 08:44:54 -0700 (PDT) From: Received: from he113470.emea1.cds.t-internal.com ([10.134.93.128]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 16:44:51 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113470.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 16:44:51 +0100 To: Date: Wed, 20 Mar 2013 16:44:49 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlA= Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2013 15:44:56 -0000 Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From Markus.Freudenberger@t-systems.com Thu Mar 21 00:48:21 2013 Return-Path: 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 E245721F8526 for ; Thu, 21 Mar 2013 00:48:21 -0700 (PDT) X-Quarantine-ID: <1xAFkIXP2YpM> X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...28377@FR711WXCHMBA06.zeu.alcatel-lucent.com>\n X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 1xAFkIXP2YpM for ; Thu, 21 Mar 2013 00:48:17 -0700 (PDT) Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id 2410D21F9046 for ; Thu, 21 Mar 2013 00:48:16 -0700 (PDT) From: Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 21 Mar 2013 08:47:50 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by he110890 ([10.134.92.131]) with mapi; Thu, 21 Mar 2013 08:47:50 +0100 To: Date: Thu, 21 Mar 2013 08:47:49 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIA== Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Mar 2013 07:48:22 -0000 Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus=20 Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From stefaan.de_cnodder@alcatel-lucent.com Thu Mar 21 02:48:51 2013 Return-Path: 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 9E43421F8574 for ; Thu, 21 Mar 2013 02:48:51 -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 VXhCnjUkIIDM for ; Thu, 21 Mar 2013 02:48:47 -0700 (PDT) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id B72A621F8556 for ; Thu, 21 Mar 2013 02:48:47 -0700 (PDT) Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r2L9mjHK027673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 21 Mar 2013 04:48:46 -0500 (CDT) Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id r2L9mgF5018552 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Mar 2013 05:48:45 -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; Thu, 21 Mar 2013 05:48:43 -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; Thu, 21 Mar 2013 10:48:41 +0100 From: "DE CNODDER, STEFAAN (STEFAAN)" To: "Markus.Freudenberger@t-systems.com" Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIAAEMolw Date: Thu, 21 Mar 2013 09:48:41 +0000 Message-ID: <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: Accept-Language: nl-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.38] 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.35 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Mar 2013 09:48:51 -0000 Hi Markus, Is your question on when the object ancpAnCurrentSessionState has value "ot= her(1)"? It is when the conditions on the other 3 values (synsent, synrcvd= , estab) are not true (as described in the description of the object). Exa= mple: suppose the AN sends a syn (state is synsent), then TCP connection go= es down. Some implementations might keep the synsent state, others might r= e-initialise and go to other state. Listing all these cases in dedicated s= tates would probably never be complete, that's why it is "other". regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com]=20 Sent: donderdag 21 maart 2013 8:48 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus=20 Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From Markus.Freudenberger@t-systems.com Thu Mar 21 09:08:36 2013 Return-Path: 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 ACEF321F90F5 for ; Thu, 21 Mar 2013 09:08:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 XSy912ARDAjE for ; Thu, 21 Mar 2013 09:08:35 -0700 (PDT) Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 28A6321F90E2 for ; Thu, 21 Mar 2013 09:08:31 -0700 (PDT) From: Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 21 Mar 2013 17:08:30 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 21 Mar 2013 17:08:30 +0100 To: Date: Thu, 21 Mar 2013 17:08:29 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIAAEMolwAA0AuuA= Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Mar 2013 16:08:36 -0000 Hi Stefaan, even the state change from estab to synsent resp. synrcvd as a trigger for = the SessionDown trap seems for me to be wrong.=20 One summarized status like e. g. down in the MIB, following the definition = in RFC 6320 chapter 3.5.2.7, may be more appropriate. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Donnerstag, 21. M=E4rz 2013 10:49 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Is your question on when the object ancpAnCurrentSessionState has value "ot= her(1)"? It is when the conditions on the other 3 values (synsent, synrcvd= , estab) are not true (as described in the description of the object). Exa= mple: suppose the AN sends a syn (state is synsent), then TCP connection go= es down. Some implementations might keep the synsent state, others might r= e-initialise and go to other state. Listing all these cases in dedicated s= tates would probably never be complete, that's why it is "other". regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 8:48 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From stefaan.de_cnodder@alcatel-lucent.com Fri Mar 22 02:42:54 2013 Return-Path: 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 B9B3921F8D35 for ; Fri, 22 Mar 2013 02:42:54 -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 iv37cOjPJp-J for ; Fri, 22 Mar 2013 02:42:53 -0700 (PDT) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 591E621F8D62 for ; Fri, 22 Mar 2013 02:42:52 -0700 (PDT) Received: from us70uusmtp3.zam.alcatel-lucent.com (h135-5-2-65.lucent.com [135.5.2.65]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r2M9god7005510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 22 Mar 2013 04:42:50 -0500 (CDT) Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id r2M9gnlq008110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Mar 2013 05:42:49 -0400 Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 22 Mar 2013 05:42:49 -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; Fri, 22 Mar 2013 10:42:34 +0100 From: "DE CNODDER, STEFAAN (STEFAAN)" To: "Markus.Freudenberger@t-systems.com" Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIAAEMolwAA0AuuAAJSCgAA== Date: Fri, 22 Mar 2013 09:42:33 +0000 Message-ID: <5F657CFC59E51E4B842F0D51C19AC36C028D2A@FR711WXCHMBA06.zeu.alcatel-lucent.com> References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: Accept-Language: nl-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.40] 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.39 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2013 09:42:55 -0000 Hi Markus, Do you propose to have an extra value for ancpAnCurrentSessionState to indi= cate when there is loss of synchronization? So we could have following scenario: 1) ancpAnCurrentSessionState =3D estab 2) one of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 4) rest of adjacency negotiation The loss sync state will be a short transient state, but it makes sense to = me, if at least this is what you propose. Also the above scenario will gen= erate the ancpAnSessionDown. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com]=20 Sent: donderdag 21 maart 2013 17:08 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, even the state change from estab to synsent resp. synrcvd as a trigger for = the SessionDown trap seems for me to be wrong.=20 One summarized status like e. g. down in the MIB, following the definition = in RFC 6320 chapter 3.5.2.7, may be more appropriate. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Donnerstag, 21. M=E4rz 2013 10:49 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Is your question on when the object ancpAnCurrentSessionState has value "ot= her(1)"? It is when the conditions on the other 3 values (synsent, synrcvd= , estab) are not true (as described in the description of the object). Exa= mple: suppose the AN sends a syn (state is synsent), then TCP connection go= es down. Some implementations might keep the synsent state, others might r= e-initialise and go to other state. Listing all these cases in dedicated s= tates would probably never be complete, that's why it is "other". regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 8:48 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From Markus.Freudenberger@t-systems.com Fri Mar 22 03:47:11 2013 Return-Path: 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 7091421F8727 for ; Fri, 22 Mar 2013 03:47:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 bBgtfEZt5io1 for ; Fri, 22 Mar 2013 03:47:09 -0700 (PDT) Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id C291921F90DD for ; Fri, 22 Mar 2013 03:47:04 -0700 (PDT) From: Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 22 Mar 2013 11:47:02 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 22 Mar 2013 11:47:02 +0100 To: Date: Fri, 22 Mar 2013 11:47:01 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIAAEMolwAA0AuuAAJSCgAAACS1pA Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028D2A@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: <5F657CFC59E51E4B842F0D51C19AC36C028D2A@FR711WXCHMBA06.zeu.alcatel-lucent.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2013 10:47:11 -0000 Hi Stefaan, this might be one scenario. Antoher one might be: =20 1) ancpAnCurrentSessionState =3D estab 2) One of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message not received because at the peer because the phyical connect= ion betweeen both peers is broken for one hour =3D> ancpAnCurrentSessionSta= te =3D los sync for one hour. 4) Connection is back again after one hour 5) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 6) rest of adjacency negotiation=20 7) ancpAnCurrentSessionState =3D estab Here, the loss of sync state is not a short transient state, right? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Freitag, 22. M=E4rz 2013 10:43 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Do you propose to have an extra value for ancpAnCurrentSessionState to indi= cate when there is loss of synchronization? So we could have following scenario: 1) ancpAnCurrentSessionState =3D estab 2) one of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 4) rest of adjacency negotiation The loss sync state will be a short transient state, but it makes sense to = me, if at least this is what you propose. Also the above scenario will gen= erate the ancpAnSessionDown. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 17:08 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, even the state change from estab to synsent resp. synrcvd as a trigger for = the SessionDown trap seems for me to be wrong.=20 One summarized status like e. g. down in the MIB, following the definition = in RFC 6320 chapter 3.5.2.7, may be more appropriate. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Donnerstag, 21. M=E4rz 2013 10:49 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Is your question on when the object ancpAnCurrentSessionState has value "ot= her(1)"? It is when the conditions on the other 3 values (synsent, synrcvd= , estab) are not true (as described in the description of the object). Exa= mple: suppose the AN sends a syn (state is synsent), then TCP connection go= es down. Some implementations might keep the synsent state, others might r= e-initialise and go to other state. Listing all these cases in dedicated s= tates would probably never be complete, that's why it is "other". regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 8:48 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From stefaan.de_cnodder@alcatel-lucent.com Fri Mar 22 07:45:13 2013 Return-Path: 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 ACA7121F8BA1 for ; Fri, 22 Mar 2013 07:45:13 -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 Q24LiUvjzFTX for ; Fri, 22 Mar 2013 07:45:12 -0700 (PDT) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED8F21F8B9C for ; Fri, 22 Mar 2013 07:45:12 -0700 (PDT) Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r2MEj9hj015355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 22 Mar 2013 09:45:10 -0500 (CDT) Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id r2MEixou030011 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Mar 2013 10:45:09 -0400 Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 22 Mar 2013 10:45:06 -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; Fri, 22 Mar 2013 15:44:45 +0100 From: "DE CNODDER, STEFAAN (STEFAAN)" To: "Markus.Freudenberger@t-systems.com" Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIAAEMolwAA0AuuAAJSCgAAACS1pAAAhi9vA= Date: Fri, 22 Mar 2013 14:44:45 +0000 Message-ID: <5F657CFC59E51E4B842F0D51C19AC36C02903F@FR711WXCHMBA06.zeu.alcatel-lucent.com> References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028D2A@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: Accept-Language: nl-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.40] 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" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2013 14:45:13 -0000 Hi Markus, Yes, it looks we are in agreement. So this object: ancpAnCurrentSessionState OBJECT-TYPE SYNTAX INTEGER { other(1), synsent(2), synrcvd(3), estab(4) } becomes ancpAnCurrentSessionState OBJECT-TYPE SYNTAX INTEGER { other(1), synsent(2), synrcvd(3), estab(4), loss_sync(5) } regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com]=20 Sent: vrijdag 22 maart 2013 11:47 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, this might be one scenario. Antoher one might be: =20 1) ancpAnCurrentSessionState =3D estab 2) One of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message not received because at the peer because the phyical connect= ion betweeen both peers is broken for one hour =3D> ancpAnCurrentSessionSta= te =3D los sync for one hour. 4) Connection is back again after one hour 5) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 6) rest of adjacency negotiation=20 7) ancpAnCurrentSessionState =3D estab Here, the loss of sync state is not a short transient state, right? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Freitag, 22. M=E4rz 2013 10:43 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Do you propose to have an extra value for ancpAnCurrentSessionState to indi= cate when there is loss of synchronization? So we could have following scenario: 1) ancpAnCurrentSessionState =3D estab 2) one of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 4) rest of adjacency negotiation The loss sync state will be a short transient state, but it makes sense to = me, if at least this is what you propose. Also the above scenario will gen= erate the ancpAnSessionDown. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 17:08 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, even the state change from estab to synsent resp. synrcvd as a trigger for = the SessionDown trap seems for me to be wrong.=20 One summarized status like e. g. down in the MIB, following the definition = in RFC 6320 chapter 3.5.2.7, may be more appropriate. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Donnerstag, 21. M=E4rz 2013 10:49 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Is your question on when the object ancpAnCurrentSessionState has value "ot= her(1)"? It is when the conditions on the other 3 values (synsent, synrcvd= , estab) are not true (as described in the description of the object). Exa= mple: suppose the AN sends a syn (state is synsent), then TCP connection go= es down. Some implementations might keep the synsent state, others might r= e-initialise and go to other state. Listing all these cases in dedicated s= tates would probably never be complete, that's why it is "other". regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 8:48 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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 From Markus.Freudenberger@t-systems.com Tue Mar 26 04:16:19 2013 Return-Path: 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 4151021F8A38 for ; Tue, 26 Mar 2013 04:16:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] 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 dH4rxXLO1cSf for ; Tue, 26 Mar 2013 04:16:18 -0700 (PDT) Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) by ietfa.amsl.com (Postfix) with ESMTP id 4505721F8A27 for ; Tue, 26 Mar 2013 04:16:03 -0700 (PDT) From: Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 26 Mar 2013 12:16:01 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 26 Mar 2013 12:16:01 +0100 To: Date: Tue, 26 Mar 2013 12:15:58 +0100 Thread-Topic: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Thread-Index: Ac3994ALXxPI3j1iRlCXYKeYEtRCTQmoGIbgACxpGOAAALGXEAALgfwwAAFZLlAAIdldIAAEMolwAA0AuuAAJSCgAAACS1pAAAhi9vAAwZ3sQA== Message-ID: References: <20130129080601.7204.88535.idtracker@ietfa.amsl.com> <5F657CFC59E51E4B842F0D51C19AC36C028045@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028377@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C0286F9@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C028D2A@FR711WXCHMBA06.zeu.alcatel-lucent.com> <5F657CFC59E51E4B842F0D51C19AC36C02903F@FR711WXCHMBA06.zeu.alcatel-lucent.com> In-Reply-To: <5F657CFC59E51E4B842F0D51C19AC36C02903F@FR711WXCHMBA06.zeu.alcatel-lucent.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Mar 2013 11:16:19 -0000 Hi Stefan, ok and I assume you add a reference to RFC 6320 in the object description t= o set the conditions for this state. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com]=20 Gesendet: Freitag, 22. M=E4rz 2013 15:45 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Yes, it looks we are in agreement. So this object: ancpAnCurrentSessionState OBJECT-TYPE SYNTAX INTEGER { other(1), synsent(2), synrcvd(3), estab(4) } becomes ancpAnCurrentSessionState OBJECT-TYPE SYNTAX INTEGER { other(1), synsent(2), synrcvd(3), estab(4), loss_sync(5) } regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: vrijdag 22 maart 2013 11:47 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, this might be one scenario. Antoher one might be: =20 1) ancpAnCurrentSessionState =3D estab 2) One of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message not received because at the peer because the phyical connect= ion betweeen both peers is broken for one hour =3D> ancpAnCurrentSessionSta= te =3D los sync for one hour. 4) Connection is back again after one hour 5) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 6) rest of adjacency negotiation 7) ancpAnCurrentSessionState =3D estab Here, the loss of sync state is not a short transient state, right? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Freitag, 22. M=E4rz 2013 10:43 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Do you propose to have an extra value for ancpAnCurrentSessionState to indi= cate when there is loss of synchronization? So we could have following scenario: 1) ancpAnCurrentSessionState =3D estab 2) one of the conditions in 3.5.2.7 happens =3D> ancpAnCurrentSessionState = =3D loss sync (+send RSTACK) 3) SYN message received =3D> ancpAnCurrentSessionState =3D synrcvd 4) rest of adjacency negotiation The loss sync state will be a short transient state, but it makes sense to = me, if at least this is what you propose. Also the above scenario will gen= erate the ancpAnSessionDown. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 17:08 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, even the state change from estab to synsent resp. synrcvd as a trigger for = the SessionDown trap seems for me to be wrong.=20 One summarized status like e. g. down in the MIB, following the definition = in RFC 6320 chapter 3.5.2.7, may be more appropriate. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Donnerstag, 21. M=E4rz 2013 10:49 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, Is your question on when the object ancpAnCurrentSessionState has value "ot= her(1)"? It is when the conditions on the other 3 values (synsent, synrcvd= , estab) are not true (as described in the description of the object). Exa= mple: suppose the AN sends a syn (state is synsent), then TCP connection go= es down. Some implementations might keep the synsent state, others might r= e-initialise and go to other state. Listing all these cases in dedicated s= tates would probably never be complete, that's why it is "other". regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: donderdag 21 maart 2013 8:48 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, regarding issue 1: I just recognized that ancpAnSessionConfigSessionId is already implicitely = contained in the trap as all objects in the trap are indexed by it. So, the= re was no need to defend the draft :o) Regards Markus -----Urspr=FCngliche Nachricht----- Von: Freudenberger, Markus Gesendet: Mittwoch, 20. M=E4rz 2013 16:45 An: 'DE CNODDER, STEFAAN (STEFAAN)' Cc: ancp@ietf.org Betreff: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, thanks for your comments. 1.=20 My prososal is still to add ancpAnSessionConfigSessionId into the trap as t= his as this is the clear reference to both tables ancpAnSessionConfigTable = and ancpAnCurrentSessionTable. The most practical situation in operation is= a loss of adjacency and not a deletion of the ancp session. 2.=20 I am not confused about your wording. The point ist that the conditions for= the state "other" is not clear to me. What does it mean? Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 15:58 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Markus, The reason why the SessionDown trap has so many objects in it, is because t= he row might be deleted, and then all information about the session should = be in the trap. The value of ancpAnSessionConfigSessionId only makes sense= if the row is still present in the table. The value of the other objects = in trap still have a meaning even if the row is deleted. I think you are confused by a bad wording I used below. One of the conditi= ons of a session being down is that the session is in another state than es= tab. The state estab as in ancpAnCurrentSessionState. This means that whe= n ancpAnCurrentSessionState is equal to other(1), synsent(2), or synrcvd(3)= , then the session is down. regards, Stefaan -----Original Message----- From: Markus.Freudenberger@t-systems.com [mailto:Markus.Freudenberger@t-sys= tems.com] Sent: woensdag 20 maart 2013 11:34 To: DE CNODDER, STEFAAN (STEFAAN) Cc: ancp@ietf.org Subject: AW: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt Hi Stefaan, see inline. Regards Markus -----Urspr=FCngliche Nachricht----- Von: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen= t.com] Gesendet: Mittwoch, 20. M=E4rz 2013 10:11 An: Freudenberger, Markus Cc: ancp@ietf.org Betreff: RE: [ANCP] I-D Action: draft-ietf-ancp-mib-an-10.txt 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 ancpAnSessionConf= igSessionId 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. MF: Ok but the same would then also happen with the other objects in the tr= ap as they are referenced then also by an non-exisiting table entry. Howeve= r, the agent implementation in the AN must ensure the information to be del= ivered in the trap. For issue 2, the state "down" is actually detailed in the next sentences: i= t can be down because the session is deleted, or the session is a state oth= er than the estab state. The estab state you find back in ancpAnCurrentSes= sionState. MF: Ok but the status "other(1)" can mean anything. It is not defined that = this necessarily only mean that the session is down. regards, Stefaan -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Mar= kus.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. = =20 1. ancpAnSessionConfigSessionId 2. ancpAnCurrentSessionAnInstance The first one identifies rows in the ancpAnSessionConfigTable and in the an= cpAnCurrentSessionTable wehreas the second one is a number from ANCP Adjace= ncy Message itself and is an attribute in the ancpAnCurrentSessionTable. Proposal: Add the attribute ancpAnSessionConfigSessionId as a varbind in the ancpSess= ionUp/ancpSessionDown traps as this is the clear reference to both tables a= ncpAnSessionConfigTable and ancpAnCurrentSessionTable.=20 Issue 2: The definition of the ancpSessionDown trap says: "This notification is gene= rated whenever an ANCP session goes down." bute the state 'down' is not exp= licitely 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=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von in= ternet-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 director= ies. This draft is a work item of the Access Node Control Protocol Working Grou= p of the IETF. Title : Access Node Control Protocol (ANCP) MIB module for Acces= s 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=3Ddraft-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