IETF Logo Mail Archive

Re: [lmap] WGLC comments for https://datatracker.ietf.org/doc/draft-ietf-lmap-information-model/

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 14 August 2016 07:28 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B170A12B01E for <lmap@ietfa.amsl.com>; Sun, 14 Aug 2016 00:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.147
X-Spam-Level:
X-Spam-Status: No, score=-8.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qe35RqwWV03t for <lmap@ietfa.amsl.com>; Sun, 14 Aug 2016 00:28:42 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A30812B012 for <lmap@ietf.org>; Sun, 14 Aug 2016 00:28:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2GxAQBSHbBX/xUHmMZeGgEBAQGCei1WfAeNJql7gg+BfSSBboQLAoErOBQBAQEBAQEBAQEDWyeCUzk7AQEBAQEBASMCLw8tAQEBAQIBEig/BQcEAgEIDQECAQQBAQsUCQcyFAkIAgQOBQgaiAcIAQ2mKJpcAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYrhEyEQoMqghIdBY4biyMBhh2LMYczhVeMN4N4HjaCRYE1boVzAX4BAQE
X-IPAS-Result: A2GxAQBSHbBX/xUHmMZeGgEBAQGCei1WfAeNJql7gg+BfSSBboQLAoErOBQBAQEBAQEBAQEDWyeCUzk7AQEBAQEBASMCLw8tAQEBAQIBEig/BQcEAgEIDQECAQQBAQsUCQcyFAkIAgQOBQgaiAcIAQ2mKJpcAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYrhEyEQoMqghIdBY4biyMBhh2LMYczhVeMN4N4HjaCRYE1boVzAX4BAQE
X-IronPort-AV: E=Sophos;i="5.28,519,1464667200"; d="scan'208";a="201009978"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 14 Aug 2016 03:28:40 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 14 Aug 2016 03:28:40 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0294.000; Sun, 14 Aug 2016 09:28:38 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [lmap] WGLC comments for https://datatracker.ietf.org/doc/draft-ietf-lmap-information-model/
Thread-Index: AQHR9H2bHKLLQENwxkShun538H1PzqBIEYZw
Date: Sun, 14 Aug 2016 07:28:36 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA7526A93F@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA75254AD4@AZ-FFEXMB04.global.avaya.com> <20160812094035.GB5685@elstar.local>
In-Reply-To: <20160812094035.GB5685@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/LK033QPxFoVkjV_0XufojUWlDL0>
Cc: "lmap@ietf.org" <lmap@ietf.org>
Subject: Re: [lmap] WGLC comments for https://datatracker.ietf.org/doc/draft-ietf-lmap-information-model/
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lmap/>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 07:28:43 -0000

All suggestions are fine. For #3 -  'IP protocol stack implementation' seems most clear to me. 

Thanks for addressing my comments. 

Regards,

Dan


> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> university.de]
> Sent: Friday, August 12, 2016 12:41 PM
> To: Romascanu, Dan (Dan)
> Cc: lmap@ietf.org
> Subject: Re: [lmap] WGLC comments for
> https://datatracker.ietf.org/doc/draft-ietf-lmap-information-model/
>

... 
 
> Thanks Dan. See my response inline.
> 
> > 1.       Section 3, pag. 8: 'It should be clear that the top-level behavior of an
> MA is simply to execute Schedules.' - what does 'top-level behavior' exactly
> mean?
> 
> I have changes this to:
> 
>   The primary function of an MA is to execute Schedules.
> 
> > 2.       Section 3.3.2, pag. 16, definition of ma-suppression-match - s/An
> optional and possibly empty unordered set of match pattern/ An optional
> and possibly empty unordered set of match patterns/
> 
> Added the plural s.
> 
> > 3.       Section 3.8.1, pag 34, definition of ma-channel-interface-name - 'If not
> present, the system will select a suitable interface.' - who is 'the system'
> here?'
> 
> It is usually the IP stack - if you connect() a socket, the IP stack usually
> decides which interface it uses by looking at the routing table. This extra
> parameter only makes sense in very specific corner cases (e.g., you use link-
> local addresses or for whatever reason you want to try to overwrite the
> routing decision). I find 'system' a reasonable term here. Do you want to
> change it to 'operating system'
> or 'IP protocol stack implementation'?
> 
> > 4.       Section 3.9, pag. 36: 'A reporting task might also have a flag
> parameter'- capitalize Reporting Task for consistency
> 
> Capitalized as suggested.
> 
> /js
>

v2.23.0 | Report a Bug | By Email