
From wdec@cisco.com  Mon Oct 28 07:05:07 2013
Return-Path: <wdec@cisco.com>
X-Original-To: ancp@ietfa.amsl.com
Delivered-To: ancp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A6511E8143 for <ancp@ietfa.amsl.com>; Mon, 28 Oct 2013 07:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 zJbqdjBqOL5N for <ancp@ietfa.amsl.com>; Mon, 28 Oct 2013 07:05:03 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDFE21F9FA7 for <ancp@ietf.org>; Mon, 28 Oct 2013 07:04:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1801; q=dns/txt; s=iport; t=1382969095; x=1384178695; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=DHLPyrVM7fv5gNjoEswENwIvFlAcM6OKC2dXXxGRlJc=; b=JG4aINxmkmM4hHV3fHWcyGTDHRAmHsseaCkARCMYeApB4BzBBzvFsKGO gk6yJF1pnb43P27rxnOzGxsblrDIAja/FFHN4Nn4ERJLZFIOuJBCSYN8I 6iT68i64C9jFX5HHxpZg0IspcUkq9cM0Ya/H7WYy7TqJBkzoYBUluYFIN c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8GADxublKtJXG+/2dsb2JhbABZgwc4VL5kgSQWbQeCJQEBAQQdHT8SAQgYChQxESUCBA4FCIdtAw8Nrh4NiWuMZYI/MQeDH4ENA5YfgxqLIYU3gyaCKg
X-IronPort-AV: E=Sophos;i="4.93,586,1378857600"; d="scan'208";a="277525968"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 28 Oct 2013 14:04:55 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9SE4tu4016045 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Oct 2013 14:04:55 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.120]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Mon, 28 Oct 2013 09:04:54 -0500
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "draft-ietf-ancp-mib-an@tools.ietf.org" <draft-ietf-ancp-mib-an@tools.ietf.org>
Thread-Topic: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
Thread-Index: AQHOqi9Ht0ftoae/nUOa6N2ejV2p3JnNXPeAgD2AroA=
Date: Mon, 28 Oct 2013 14:04:54 +0000
Message-ID: <19F346EB777BEE4CB77DA1A2C56F20B32003B5EC@xmb-aln-x05.cisco.com>
In-Reply-To: <523AE58F.8050001@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.7.130812
x-originating-ip: [10.61.111.204]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <41CB76B5D1764A4D816DEB4EF1F5A394@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Oct 2013 14:05:08 -0000

Hi MIB-draft authors,

Could you kindly reply to Tom's comments/questions. We can then close the
last call.

Regards,
Wojciech.



On 19/09/2013 13:52, "Tom Taylor" <tom.taylor.stds@gmail.com> wrote:

>On 05/09/2013 7:58 AM, Wojciech Dec (wdec) wrote:
>> Hi All,
>>
>> Starting from today we would like to initiate a week Working Group
>> Last Call for the following draft:
>>
>> Access Node Control Protocol (ANCP) MIB module for Access Nodes
>>
>> http://tools.ietf.org/html/draft-ietf-ancp-mib-an-11
>>
>> Accordingly, please review these documents and bring any remaining
>> issues, or issues whose resolution is not satisfactory, to the
>> attention of the Working Group on this list and/or by using the issue
>> tracker tool.
>>
>> Please note that both of these parts has recently been substantially
>> rewritten by Roy, just as I rewrote p6 a while back. As such, we're
>> treating those changes as a proposal from the editors to the Working
>> Group, to be confirmed. Please review carefully with this in mind.
>>
>> To give people ample time to review, we'll have a 3-week WGLC, ending
>> on September 27.
>>
>> Regards,
>>
>> Wojciech and Matthew.
>>
>
>I have reviewed the latest version of this document. There are a couple
>instances of non-native English syntax, but not enough to worry about.
>In general the document looks good to go.
>
>I have one question regarding the ancpAnSessionUp notification. The
>index to the session tables is ancpAnSessionConfigSessionId. How, then,
>does one retrieve the data associated with the
>ancpAnCurrentSessionAnInstance, which is buried in the
>ancpAnCurrentSessionTabl? Is it necessary to walk the complete
>ancpAnCurrentSessionTable (well, on the average, half the table)
>applying a filter?


From Moti.Morgenstern@ecitele.com  Tue Oct 29 08:16:03 2013
Return-Path: <Moti.Morgenstern@ecitele.com>
X-Original-To: ancp@ietfa.amsl.com
Delivered-To: ancp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F8E11E8291 for <ancp@ietfa.amsl.com>; Tue, 29 Oct 2013 08:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 WRyR-QjSnEci for <ancp@ietfa.amsl.com>; Tue, 29 Oct 2013 08:15:59 -0700 (PDT)
Received: from ilptbmg01-out.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by ietfa.amsl.com (Postfix) with ESMTP id 1589811E82B2 for <ancp@ietf.org>; Tue, 29 Oct 2013 08:15:57 -0700 (PDT)
X-AuditID: 93eaf2e7-b7f798e0000035ac-f4-526fdf4d29d5
Received: from ILPTWPVEXCA02.ecitele.com ( [172.31.244.232]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id CC.4B.13740.D4FDF625; Tue, 29 Oct 2013 18:16:13 +0200 (IST)
Received: from ILPTWPVEXMB01.ecitele.com ([fe80::f152:8eaf:8fb0:a5da]) by ILPTWPVEXCA02.ecitele.com ([fe80::c473:490d:3a7e:e34a%12]) with mapi id 14.03.0123.003; Tue, 29 Oct 2013 17:15:55 +0200
From: Moti Morgenstern <Moti.Morgenstern@ecitele.com>
To: "ancp@ietf.org" <ancp@ietf.org>, Tom Taylor <tom.taylor.stds@gmail.com>
Thread-Topic: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
Thread-Index: AQHOqi9Ht0ftoae/nUOa6N2ejV2p3JnNXPeAgD2AroCAASOj4IAAFC9Q
Date: Tue, 29 Oct 2013 15:15:54 +0000
Message-ID: <8FEE79F3EE86A244B0BDE68E90ED34DC1CD44835@ILPTWPVEXMB01.ecitele.com>
References: <5F657CFC59E51E4B842F0D51C19AC36C278F3A99@FR711WXCHMBA06.zeu.alcatel-lucent.com>
In-Reply-To: <5F657CFC59E51E4B842F0D51C19AC36C278F3A99@FR711WXCHMBA06.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.4.46.21]
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA3VTa0gUURTm7sxu42NiXB97tYhttCIftVsJG6W9yDQJxcrAjBp3b7tTu7Pb ziQqFFZUoP3oSbYG9tAsC7aiRFMDjfJBoNG7cKW2rNwgkEjcULrTpAnR/fXd833nnO9ezqEI 7VdNHMULEnILnJ3VhJKnhoa/p2wYcOYZ+n3Jpt7AMcLU/fIsaerzBsmVRObhwTZ1ZrOnf1pm be2oKpcoKAfLOUFwSpyE9BYkmtPYXDdfzJlLWT1vSWONrN5l58zIgQQpjeVcLiRY2PRQ/T9n OZbxgh4JZqeFF6xpbNbGnBSTKXVpipFNnxtvXLwsdJONF/UoxcHxdr0DiSJnRXoc2XGHsHlP r3P5Z5R8PDlKloO3MRUghILMEljZ2qVWcAzs83k1FSCU0jLtAPpe3lcrl4cA3vWNAVmlYVLh 92GvSsZRTDYMPgtMkzGB8b3zraSMI5ks+OCQD2sorFkPT9UZFZgBq58myQqSmQMPPm9Uy2Ga yYUDbclyWMsUwpaG7t9FQpht8OLrx4SMAbY20nNDpTTSwTcfalSKZQbWtvYSCo6GX/zjf54y CzZ52/8YS4YXWoY1Ck6CVy4GfutpJgJ2n/tAKvpY2H71FXkc6DxTWnimpHumpHumpF8AZAOI 5u0uqchhNRgXIDMvITtaYHY6bgNlVD41gWBNQgdgKMCG05lRzjytmisWSx0dIJZSsdH0z14c ml7ktJTaONG23b3XjsQOACmCjaLPdmKOtnClZcjtnKDW4g88QcSFmZ14KAVp+2KD4f8XVkfX l2/J0TJWPH67EXIh90SdmRTFQprowy0i3MiKSnbydukvraJCZBvh2MY+2SItujiHyFsVvgfM jtPRgzLByIRtrzCZO7EkQ0CHHx1Jh8ktwvEKTWYP4cIqXLiVFOTCeDUmqbhyEBNc42vrJ9aX vfAv8deFLZSqs5sua9fU2/ePdRRmJGQHDT8Su/KnZ7Qzn09snTdwqWpX1PuYpM1nSiqqcnr9 T44y7wriv5lGCjoHdYHUuhnF9Tu33WpoWQb7j+fnRa54tOoJXRkdOJIXG2t8cf1mc9m1+WFv Vl9aZK6iD+wJGS9oFFhStHHGRMItcr8AnlDte/8DAAA=
Subject: Re: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 15:16:03 -0000

Hi all,

The question, if I understand it correctly, assumes that the ancpAnSessionUp=
 notification reports the ancpAnCurrentSessionAnInstance only as a value (wh=
ich means the management system does not know what session ID is involved).
However, in SNMP each object (Variable Binding) in the PDU (no matter if tha=
t is a SET/GET message of a notification message) is actually more than just=
 a value. 

Actually, each Variable Binding consists of 4 pieces of information: 
(1) The length of the Variable Binding instance in bytes [should the destina=
tion wish to jump over that Variable Binding block].
(2) The full OID of the Variable Binding instance (i.e., which means you got=
 the ancpAnSessionConfigSessionId value embedded here) 
(3) The value type 
(4) The value

I hope that this clears the question.

Regards,
Moti
-----Original Message-----
From: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucen=
t.com] 
Sent: Tuesday, October 29, 2013 3:30 PM
To: Moti Morgenstern
Subject: FW: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11

Hi Moti,

Do you have an answer for the question below?  Scanning the whole table does=
 not look a big problem to me because I do not expect that many ANCP session=
s in an AN, but still the question looks relevant for me if there is such a=
 method to directly access the right row.

Regards,
Stefaan


-----Original Message-----
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: maandag 28 oktober 2013 15:05
To: draft-ietf-ancp-mib-an@tools.ietf.org
Cc: ancp@ietf.org; Tom Taylor
Subject: Re: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11

Hi MIB-draft authors,

Could you kindly reply to Tom's comments/questions. We can then close the la=
st call.

Regards,
Wojciech.



On 19/09/2013 13:52, "Tom Taylor" <tom.taylor.stds@gmail.com> wrote:

>On 05/09/2013 7:58 AM, Wojciech Dec (wdec) wrote:
>> Hi All,
>>
>> Starting from today we would like to initiate a week Working Group 
>> Last Call for the following draft:
>>
>> Access Node Control Protocol (ANCP) MIB module for Access Nodes
>>
>> http://tools.ietf.org/html/draft-ietf-ancp-mib-an-11
>>
>> Accordingly, please review these documents and bring any remaining 
>> issues, or issues whose resolution is not satisfactory, to the 
>> attention of the Working Group on this list and/or by using the issue 
>> tracker tool.
>>
>> Please note that both of these parts has recently been substantially 
>> rewritten by Roy, just as I rewrote p6 a while back. As such, we're 
>> treating those changes as a proposal from the editors to the Working 
>> Group, to be confirmed. Please review carefully with this in mind.
>>
>> To give people ample time to review, we'll have a 3-week WGLC, ending 
>> on September 27.
>>
>> Regards,
>>
>> Wojciech and Matthew.
>>
>
>I have reviewed the latest version of this document. There are a couple 
>instances of non-native English syntax, but not enough to worry about.
>In general the document looks good to go.
>
>I have one question regarding the ancpAnSessionUp notification. The 
>index to the session tables is ancpAnSessionConfigSessionId. How, then, 
>does one retrieve the data associated with the 
>ancpAnCurrentSessionAnInstance, which is buried in the 
>ancpAnCurrentSessionTabl? Is it necessary to walk the complete 
>ancpAnCurrentSessionTable (well, on the average, half the table) 
>applying a filter?



This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


From tom.taylor.stds@gmail.com  Tue Oct 29 08:28:18 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ancp@ietfa.amsl.com
Delivered-To: ancp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C186411E82F2 for <ancp@ietfa.amsl.com>; Tue, 29 Oct 2013 08:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
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 J9V2YlXkLuiy for <ancp@ietfa.amsl.com>; Tue, 29 Oct 2013 08:28:18 -0700 (PDT)
Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B0E2E11E82FB for <ancp@ietf.org>; Tue, 29 Oct 2013 08:27:50 -0700 (PDT)
Received: by mail-qa0-f46.google.com with SMTP id j15so2962169qaq.5 for <ancp@ietf.org>; Tue, 29 Oct 2013 08:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=uSwVL4lifNnLdaY60iiIpxQW5qaB78p/q2uSp8JvOCE=; b=S0MDi2r7iw4ZnUqF2WdSgsQ1JZnzRvP1NJfGAYZ1e4bHdZTHbCc9yZ96Xt/3p21uAK 8FuwGoKovc7HANe1YK/DaB4ND9lRYTKwWwWnDe7/0pnXeJVSAwb6GWs2NB0TcCIHSPzI RZBNYz+NoiJ5toYViqCJ3YNdGd/xq6UW6psLjZlGIhQkmi7axko3cXPRYj96NACQzMvx 5s0k/jrbf+SfQbATwbOJb7pErEXCmMPjV7bv/lbWeXylsnZ9ry5c8/VHo8wDITi9itIe TrHeECv4oVa6fQd0kKgL+hWa9huMqyBvLimMLH3o3XtC3pwxYSZJM/31EeO76/mES+av XJRw==
X-Received: by 10.49.6.6 with SMTP id w6mr79457qew.43.1383060470007; Tue, 29 Oct 2013 08:27:50 -0700 (PDT)
Received: from [192.168.1.69] ([64.56.250.4]) by mx.google.com with ESMTPSA id k2sm48481739qan.8.2013.10.29.08.27.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 08:27:49 -0700 (PDT)
Message-ID: <526FD3F3.9080506@gmail.com>
Date: Tue, 29 Oct 2013 11:27:47 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Moti Morgenstern <Moti.Morgenstern@ecitele.com>,  "ancp@ietf.org" <ancp@ietf.org>
References: <5F657CFC59E51E4B842F0D51C19AC36C278F3A99@FR711WXCHMBA06.zeu.alcatel-lucent.com> <8FEE79F3EE86A244B0BDE68E90ED34DC1CD44835@ILPTWPVEXMB01.ecitele.com>
In-Reply-To: <8FEE79F3EE86A244B0BDE68E90ED34DC1CD44835@ILPTWPVEXMB01.ecitele.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 15:28:18 -0000

Stefaan actually answered the question I intended. Essentially, the 
answer is that walking the whole table is no big deal because it won't 
be that large. Thanks, aand consider the matter cleared.

tom

On 29/10/2013 11:15 AM, Moti Morgenstern wrote:
> Hi all,
>
> The question, if I understand it correctly, assumes that the ancpAnSessionUp notification reports the ancpAnCurrentSessionAnInstance only as a value (which means the management system does not know what session ID is involved).
> However, in SNMP each object (Variable Binding) in the PDU (no matter if that is a SET/GET message of a notification message) is actually more than just a value.
>
> Actually, each Variable Binding consists of 4 pieces of information:
> (1) The length of the Variable Binding instance in bytes [should the destination wish to jump over that Variable Binding block].
> (2) The full OID of the Variable Binding instance (i.e., which means you got the ancpAnSessionConfigSessionId value embedded here)
> (3) The value type
> (4) The value
>
> I hope that this clears the question.
>
> Regards,
> Moti
> -----Original Message-----
> From: DE CNODDER, STEFAAN (STEFAAN) [mailto:stefaan.de_cnodder@alcatel-lucent.com]
> Sent: Tuesday, October 29, 2013 3:30 PM
> To: Moti Morgenstern
> Subject: FW: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
>
> Hi Moti,
>
> Do you have an answer for the question below?  Scanning the whole table does not look a big problem to me because I do not expect that many ANCP sessions in an AN, but still the question looks relevant for me if there is such a method to directly access the right row.
>
> Regards,
> Stefaan
>
>
> -----Original Message-----
> From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
> Sent: maandag 28 oktober 2013 15:05
> To: draft-ietf-ancp-mib-an@tools.ietf.org
> Cc: ancp@ietf.org; Tom Taylor
> Subject: Re: [ANCP] Working Group Last Call for draft-ietf-ancp-mib-an-11
>
> Hi MIB-draft authors,
>
> Could you kindly reply to Tom's comments/questions. We can then close the last call.
>
> Regards,
> Wojciech.
>
>
>
> On 19/09/2013 13:52, "Tom Taylor" <tom.taylor.stds@gmail.com> wrote:
>
>> On 05/09/2013 7:58 AM, Wojciech Dec (wdec) wrote:
>>> Hi All,
>>>
>>> Starting from today we would like to initiate a week Working Group
>>> Last Call for the following draft:
>>>
>>> Access Node Control Protocol (ANCP) MIB module for Access Nodes
>>>
>>> http://tools.ietf.org/html/draft-ietf-ancp-mib-an-11
>>>
>>> Accordingly, please review these documents and bring any remaining
>>> issues, or issues whose resolution is not satisfactory, to the
>>> attention of the Working Group on this list and/or by using the issue
>>> tracker tool.
>>>
>>> Please note that both of these parts has recently been substantially
>>> rewritten by Roy, just as I rewrote p6 a while back. As such, we're
>>> treating those changes as a proposal from the editors to the Working
>>> Group, to be confirmed. Please review carefully with this in mind.
>>>
>>> To give people ample time to review, we'll have a 3-week WGLC, ending
>>> on September 27.
>>>
>>> Regards,
>>>
>>> Wojciech and Matthew.
>>>
>>
>> I have reviewed the latest version of this document. There are a couple
>> instances of non-native English syntax, but not enough to worry about.
>> In general the document looks good to go.
>>
>> I have one question regarding the ancpAnSessionUp notification. The
>> index to the session tables is ancpAnSessionConfigSessionId. How, then,
>> does one retrieve the data associated with the
>> ancpAnCurrentSessionAnInstance, which is buried in the
>> ancpAnCurrentSessionTabl? Is it necessary to walk the complete
>> ancpAnCurrentSessionTable (well, on the average, half the table)
>> applying a filter?
>
>
>
> This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.
>
>
