IETF Logo Mail Archive

Re: [lmap] Feedback on draft-eardley-lmap-terminology

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 25 July 2013 09:46 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 D855621F9AAB for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 02:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.413
X-Spam-Level:
X-Spam-Status: No, score=-103.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 UhVWtw-hDMdb for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 02:46:52 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 1F67721F9A15 for <lmap@ietf.org>; Thu, 25 Jul 2013 02:46:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4NACPz8FHGmAcV/2dsb2JhbABagmUhNVCpUpQIAwGBGBZ0giQBAQEBAxIoPwwEAgEIDQECAQQBAQEKFAkHMhQJCAIEDgUIGoduAZ14nA2PETsxBwaDDG4DmQiFHYsHgxSCKg
X-IronPort-AV: E=Sophos;i="4.89,742,1367985600"; d="scan'208";a="17745875"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Jul 2013 05:46:48 -0400
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jul 2013 05:44:13 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0328.009; Thu, 25 Jul 2013 05:46:46 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [lmap] Feedback on draft-eardley-lmap-terminology
Thread-Index: AQHOhvZB9LoTtC34Rxe0kMCmPNNKaZlz1UIwgABgPoCAAOq3wIAATE4A//+9HKA=
Date: Thu, 25 Jul 2013 09:46:46 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA12880DA0@AZ-FFEXMB04.global.avaya.com>
References: <51ED59B3.3040701@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA1287FC5D@AZ-FFEXMB04.global.avaya.com> <20130724151217.GA39515@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA12880D39@AZ-FFEXMB04.global.avaya.com> <20130725094528.GA41769@elstar.local>
In-Reply-To: <20130725094528.GA41769@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "lmap@ietf.org" <lmap@ietf.org>
Subject: Re: [lmap] Feedback on draft-eardley-lmap-terminology
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 25 Jul 2013 09:46:58 -0000

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> university.de]
> Sent: Thursday, July 25, 2013 12:45 PM
> To: Romascanu, Dan (Dan)
> Cc: lmap@ietf.org
> Subject: Re: [lmap] Feedback on draft-eardley-lmap-terminology
> 
> On Thu, Jul 25, 2013 at 09:17:22AM +0000, Romascanu, Dan (Dan) wrote:
> >
> > [[DR]] The phrase I am refering to is not from draft-eardley-lmap-
> terminology-02 but from draft-eardley-lmap-framework-02, section 2. In
> my reading this sentence does not talk about who initiates the session,
> but about the way the configuration itself is to reach the MAs:
> >
> > >  To avoid problems with NAT and firewalls, it is likely that the MA
> >    'pulls' the configuration from its Controller, as identified by the
> >    Initialiser.
> >
> 
> OK. I guess this should then be reworded to read like this (or something
> similar):
> 
>   To avoid problems with NAT and firewalls, it is likely that the MA
>   is required to establish the transport layer connection over which
>   it receives its configuration from its Controller, as identified by
>   the Initialiser.
> 
> /js
> 

[[DR]] yes - this makes sense. 

Dan

v2.23.0 | Report a Bug | By Email