IETF Logo Mail Archive

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

<philip.eardley@bt.com> Thu, 25 July 2013 13:28 UTC

Return-Path: <philip.eardley@bt.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 937F421F933B for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 06:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.333
X-Spam-Level:
X-Spam-Status: No, score=-103.333 tagged_above=-999 required=5 tests=[AWL=0.266, 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 5ghFAXPPwh7L for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 06:28:12 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.com [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id 90B7E21F8436 for <lmap@ietf.org>; Thu, 25 Jul 2013 06:27:38 -0700 (PDT)
Received: from EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.298.1; Thu, 25 Jul 2013 14:27:37 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.1.253]) by EVMHT67-UKRD.domain1.systemhost.net ([10.36.3.104]) with mapi; Thu, 25 Jul 2013 14:27:37 +0100
From: philip.eardley@bt.com
To: dromasca@avaya.com, j.schoenwaelder@jacobs-university.de
Date: Thu, 25 Jul 2013 14:27:35 +0100
Thread-Topic: [lmap] Feedback on draft-eardley-lmap-terminology
Thread-Index: AQHOhvZB9LoTtC34Rxe0kMCmPNNKaZlz1UIwgABgPoCAAOq3wIAATE4A//+9HKCAADynEA==
Message-ID: <9510D26531EF184D9017DF24659BB87F35B80337B0@EMV65-UKRD.domain1.systemhost.net>
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> <9904FB1B0159DA42B0B887B7FA8119CA12880DA0@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA12880DA0@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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 13:28:16 -0000

Dan, Juergen - Thanks, good catch and the re-phrasing seems good to me.

Also Dan said
<< But then in the diagram in Figure 1 the arrow points from the Controller to the MA, and later the examples of possible protocols in Section 5.3 include such 'push' protocols as SNMP and NETCONF>>

I'll clarify that the arrow is about the Instruction. The control protocol may need some back and forth (to request or 'pull' the Instruction)

> -----Original Message-----
> From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of
> Romascanu, Dan (Dan)
> Sent: 25 July 2013 10:47
> To: Juergen Schoenwaelder
> Cc: lmap@ietf.org
> Subject: Re: [lmap] Feedback on draft-eardley-lmap-terminology
> 
> 
> 
> 
> 
> > -----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
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap

v2.23.0 | Report a Bug | By Email