[lmap] comments on https://www.ietf.org/id/draft-ietf-lmap-restconf-03.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 31 July 2016 15:21 UTC

X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES256-SHA; 31 Jul 2016 11:21:37 -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.03.0294.000; Sun, 31 Jul 2016 17:21:35 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "lmap@ietf.org" <lmap@ietf.org>
Thread-Topic: comments on https://www.ietf.org/id/draft-ietf-lmap-restconf-03.txt
Thread-Index: AdHrPza1VMJeXcQ/QIqm937s6Q6dJQ==
Date: Sun, 31 Jul 2016 15:21:34 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA752572F2@AZ-FFEXMB04.global.avaya.com>
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: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA752572F2AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/VumwL3rk8m6jhYbK4y41f48joXA>
Subject: [lmap] comments on https://www.ietf.org/id/draft-ietf-lmap-restconf-03.txt
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, 31 Jul 2016 15:21:44 -0000

The WGLC for https://www.ietf.org/id/draft-ietf-lmap-restconf-03.txt expires today. Obviously, the document is not yet ready for submission to the IESG. Let me try to recap shortly what was discussed in the meeting at IETF 96 and how we can progress this document from here.


-          The consensus in the room at IETF 96 was that this document is basically an application statement, that describes how RESTONF and call-home are being used to meet the required functionality of the LMAP configuration protocol and LMAP reporting protocol.

-          The introduction paragraph should mention the fact that the WG protocol selection process gave preference to a solution that reuses existing IETF protocols rather than inventing new ones

-          The current text is pretty much trimmed down - but there was at least one comment (from Tim) that asked to document more in detail how call-home is being used and the fact that the MA initiates the communication - i.e. the MA needs to implement both a server (for the configuration protocol) and a client (for the reporting protocol)

-          Rework and clarify the example

-          Add Security Considerations - guidance for when information is communicated, reference to the RESTCONF security considerations

-          Make draft-ietf-netconf-call-home a normative reference; one cannot implement the LMAP reporting protocol without it

-          Obviously RESTCONF and call-home are dependencies. The plan is to edit and post a revised version after the LC expires and park the document until RESTCONF and call-home will be approved

Regards,

Dan

[lmap] comments on https://www.ietf.org/id/draft-… Romascanu, Dan (Dan)