
From nobody Sat May  4 14:52:33 2019
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20F2E12023B for <opsawg@ietfa.amsl.com>; Sat,  4 May 2019 14:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 f5BihO2Q5Waz for <opsawg@ietfa.amsl.com>; Sat,  4 May 2019 14:52:30 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D9DC120225 for <opsawg@ietf.org>; Sat,  4 May 2019 14:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=450; q=dns/txt; s=iport; t=1557006750; x=1558216350; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=/Sw5BLxlvGr+XBInLhrV7fx90LDrWZula2QBCFNoJFI=; b=cPvL/IH707kP1tG/STdNORU+/nkw/qbnwOZeOlkLnaCCVintqvmePAs4 Icc4zlm9JR2HkKK75VINGCr03a6NSV4St3NOpQT9SXjMaOmTnWzUEgQTs heIpFZoMtguEeCZ6qLhBqSTKPzLcoAR8bPn5C3MhVAyfwAxTk/Hh8kDkG Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A+AAARCc5c/5RdJa1lGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBVAMBAQELAYIQaYEEMpcagWiacg4BASWGUCM3Bg4BAwEBBAEBAgE?= =?us-ascii?q?CbRwBC4YLUQE+QicEgzUBggoPrCuEMgEDAgKBDYRdBoEyAYtNF4FAP4E4DBO?= =?us-ascii?q?BN4Q0AgOFGoImBJI9h2KNEwkCggkChhaMLRuBfgEPhj+LOYFCi2Y1hkyOHQI?= =?us-ascii?q?RFYEwNSKBVnAVZQGCQoIaF4hghT9BgieOKIEhAQE?=
X-IronPort-AV: E=Sophos;i="5.60,431,1549929600"; d="scan'208";a="266863569"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 May 2019 21:52:29 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x44LqT2O014513 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <opsawg@ietf.org>; Sat, 4 May 2019 21:52:29 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 4 May 2019 16:52:28 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1473.003; Sat, 4 May 2019 16:52:28 -0500
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Minutes for 104
Thread-Index: AQHVAsOq7LR4S1eZ802KyMKxrGhc0w==
Date: Sat, 4 May 2019 21:52:27 +0000
Message-ID: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.88.20]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5C3068E55064CE40A1E29BC740E91852@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.23, xch-rcd-013.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/pocrLJTbvDyqxFuZS5o_zpBqRYg>
Subject: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2019 21:52:32 -0000

After a long delay I have posted the draft minutes from the IETF 104 opsawg=
/Ops Area session.  I took these from notes I did in Etherpad as well as th=
e video recording on YouTube.  I missed one Huawei name at the mic with the=
 NTF draft, but I think I captured most everything else.

Please review and Tianran or I know what we need to change.

Thanks.

https://datatracker.ietf.org/meeting/104/materials/minutes-104-opsawg-00

Joe=


From nobody Sat May  4 14:55:50 2019
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6891912025D for <opsawg@ietfa.amsl.com>; Sat,  4 May 2019 14:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 rqzI4HkJBtVo for <opsawg@ietfa.amsl.com>; Sat,  4 May 2019 14:55:46 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD372120252 for <opsawg@ietf.org>; Sat,  4 May 2019 14:55:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7814; q=dns/txt; s=iport; t=1557006946; x=1558216546; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=XzfvH3P5b75vpiAOEBI6sLu97Qii7bJMHFg24gvgwMg=; b=JfgMFWAa/TqqOUI1fdGJOkODLuitVUEW7q4/mGTRmohzR+QDyrGzo9kX M8VdYGBeY/Zb/Er3reHAULatEuTWolnowmzZZ7fdniLyCNfmiTU/IqgHD Z5JZFZK3k+PlCIDd9i7aJyyX7rlE7dLZh5Jybs2tMWLIbQISTo0BxD2XU o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AKAAARCc5c/4gNJK1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUwMBAQEBCwGBYQUqaYEEKAqEBpUhmFKBew4BARgLhARGAhe?= =?us-ascii?q?BbyM2Bw4BAwEBBAEBAgECbRwMhUoBAQEBAgEBASEROQELBQcEAgEIEQQBAQE?= =?us-ascii?q?CAiMDAgICJQsUAQgIAgQOBYJXSwGBew8PqnyBL4VHhGOBCycBi00XgUA/gRE?= =?us-ascii?q?nH4FOfj6CYQEBgWGDCjKCJgSLJCWCCIxOjRMJAoIJhhiEMYd8G4JvklmKV5Y?= =?us-ascii?q?tAhEVgTAmAi+BVnAVOyoBgkEJiwk8gSmDWkExkB6BIQEB?=
X-IronPort-AV: E=Sophos;i="5.60,431,1549929600"; d="scan'208";a="267434771"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 May 2019 21:55:45 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x44Ltjld021392 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 4 May 2019 21:55:45 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 4 May 2019 16:55:44 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1473.003; Sat, 4 May 2019 16:55:44 -0500
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: Haoyu song <haoyu.song@huawei.com>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Review of draft-song-opsawg-ntf-03
Thread-Index: AQHU7hgEQ3mjcRUHmk+F50KEkLqkO6ZUXuCAgAehAAA=
Date: Sat, 4 May 2019 21:55:44 +0000
Message-ID: <4D11F8CC-06B3-4B64-AB50-DF8E04A3826E@cisco.com>
References: <c8d48489-e34e-6854-f3a1-f447f913dab0@cisco.com> <78A2745BE9B57D4F9D27F86655EB87F9376B3FC7@sjceml521-mbs.china.huawei.com>
In-Reply-To: <78A2745BE9B57D4F9D27F86655EB87F9376B3FC7@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.88.20]
Content-Type: text/plain; charset="utf-8"
Content-ID: <66BB51E3A6178D4EBAB1ED3E3F04CFED@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/z78G6iIkbqU08VfcOqrSztHCFXA>
Subject: Re: [OPSAWG] Review of draft-song-opsawg-ntf-03
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2019 21:55:50 -0000

DQoNCj4gT24gQXByIDI5LCAyMDE5LCBhdCAyMToyNSwgSGFveXUgc29uZyA8aGFveXUuc29uZ0Bo
dWF3ZWkuY29tPiB3cm90ZToNCj4gDQo+IEhpIEpvZSwNCj4gDQo+IEknbSB3b3JraW5nIG9uIHJl
dmlzaW5nIHRoZSBkcmFmdC4gDQo+IA0KPiBCZWxvdyBhcmUgc29tZSB0aG91Z2h0cyBvbiB0aGUg
aXNzdWVzIHlvdSByYWlzZWQgYWJvdXQgU2VjdGlvbiAyOg0KPiANCj4gMSkgSSdsbCBwb3NpdGlv
biBBSSBhIG1vcmUgZm9yd2FyZCBsb29raW5nIHRlY2huaXF1ZSB0aGF0IGNhbiB0YWtlIGFkdmFu
dGFnZSBvZiBuZXR3b3JrIHRlbGVtZXRyeS4NCg0KVGhhbmtzLg0KDQo+IA0KPiAyKSBOTVJHIGlz
IHdvcmtpbmcgb24gIHByb3ZpZGUgYSBmb3JtYWwgZGVmaW5pdGlvbiBvZiAiaW50ZW50IiBzbyBJ
IHRoaW5rIHdlIGNhbiB1c2UgdGhhdCBhcyBhIHJlZmVyZW5jZSB0byBjbGFyaWZ5IHRoZSBidXp6
IHdvcmQuDQoNClllcywgdGhhdCB3YXMgbXkgdGhpbmtpbmcgYXMgd2VsbC4gIEkgbWF5IGhhdmUg
bWVudGlvbmVkIE5NUkcgaW4gYSBwcmV2aW91cyBtZWV0aW5nIHRvIG1ha2Ugc3VyZSB0aGlzIGFs
aWducyB3aXRoIHRoZWlyIHdvcmsuDQoNCj4gDQo+IDMpIFdoZW4gSSBzYXkgInRoZSBzeXN0ZW0g
Ym90dGxlbmVjayBpcyBzaGlmdGluZyBmcm9tIGRhdGEgY29uc3VtcHRpb24gdG8gZGF0YSBzdXBw
bHkiLCAgd2hhdCBJIG1lYW4gaXMgIHRoYXQgbm93IHRoZSBkYXRhIHByb2Nlc3NpbmcgY2FwYWJp
bGl0eSBpcyBncmVhdGx5IGltcHJvdmVkIGFuZCBtYW55IGFwcGxpY2F0aW9ucyBhcmUgaHVuZ3J5
IGZvciBtb3JlIGRhdGEgeWV0IHRoZSBuZXR3b3JrICBsYWdzIGJlaGluZCBpbiBwcm92aWRpbmcg
ZW5vdWdoIGhpZ2ggcXVhbGl0eSBkYXRhIGluIGEgdGltZWx5IG1hbm5lci4gSSBhZ3JlZSB3ZSBt
dXN0IGhhdmUgYSB3YXkgdG8gdHJhbnNsYXRlIHRoYXQgZGF0YSBpbnRvIHVzZWZ1bCwgYWN0aW9u
YWJsZSBpbmZvcm1hdGlvbi4gSSB0aGluayB0aGlzIGlzIGFsc28gYSBwYXJ0IG9mIGpvYiBvZiBu
ZXR3b3JrIHRlbGVtZXRyeS4gTmV0d29yayB0ZWxlbWV0cnkgaXMgbm90IGp1c3Qgc3VwcGx5aW5n
IHJhdyBkYXRhLCBidXQgc3VwcGx5aW5nIHVzZWZ1bCBhbmQgYWN0aW9uYWJsZSBkYXRhLg0KDQpJ
dCBhYnNvbHV0ZWx5IGlzLiAgSeKAmWQgbGlrZSB0byBzZWUgdGhlIGRvY3VtZW50IGNsYXJpZmll
ZCB0byBtYWtlIHRoaXMgZXhwbGljaXQuICBNb3JlIGRhdGEgZm9yIHNvbWUgd2lsbCBqdXN0IG1l
YW4gbW9yZSB0byBzdG9yZSBhbmQgbW9yZSBjb25mdXNpb24gYWJvdXQgd2hhdCBzZW5zZSB0byBt
YWtlIG9mIGl0LiAgTW9yZSBpc27igJl0IGFsd2F5cyBiZXR0ZXIgdW5sZXNzIHRoYXQgbW9yZSBo
ZWxwcyBtYWtlIGJldHRlciBkZWNpc2lvbnMuDQoNCkpvZQ0KDQo+IA0KPiBCZXN0IHJlZ2FyZHMs
DQo+IEhhb3l1DQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBPUFNB
V0cgW21haWx0bzpvcHNhd2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEpvZSBDbGFy
a2UNCj4gU2VudDogTW9uZGF5LCBBcHJpbCAwOCwgMjAxOSA3OjMxIEFNDQo+IFRvOiBvcHNhd2dA
aWV0Zi5vcmcNCj4gU3ViamVjdDogW09QU0FXR10gUmV2aWV3IG9mIGRyYWZ0LXNvbmctb3BzYXdn
LW50Zi0wMw0KPiANCj4gQXMgSSBwcm9taXNlZCBhdCB0aGUgbWljIGF0IDEwNCwgSSBoYXZlIGEg
bW9yZSBjb21wcmVoZW5zaXZlIHJldmlldyBvZiB0aGlzIGRyYWZ0Lg0KPiANCj4gSSdsbCB0YWNr
bGUgdGhpcyBzZWN0aW9uLWJ5LXNlY3Rpb24uICBUaGVzZSBhcmUgYSBjb21iaW5hdGlvbiBvZiBu
aXRzIGFuZCBtb3JlIHN1YnN0YW50aXZlIGNvbW1lbnRzLg0KPiANCj4gPT09DQo+IA0KPiBJbiB0
aGUgYWJzdHJhY3QsIHlvdSBoYXZlIGEgc2VudGVuY2U6DQo+IA0KPiBOZXR3b3JrIHRlbGVtZXRy
eSBwcm9taXNlcyBiZXR0ZXIgZmxleGliaWxpdHksIHNjYWxhYmlsaXR5LCBhY2N1cmFjeSwgY292
ZXJhZ2UsIGFuZCBwZXJmb3JtYW5jZS4uLg0KPiANCj4gVGhpcyBsZWZ0IG1lIHdvbmRlcmluZywg
InRoYW4gd2hhdD8iICBUaGF0IGlzLCBJIHRoaW5rIHlvdeKAmXJlIHRyeWluZyB0byBzYXkgdGhh
dCB3aXRoIHJlc3BlY3QgdG8gdHJhZGl0aW9uYWwgcG9sbC1iYXNlZCBuZXR3b3JrIG1vbml0b3Jp
bmcsIHRlbGVtZXRyeSBwcm92aWRlcyB0aGVzZSBhZHZhbnRhZ2VzLiAgSWYgeW91J3JlIGdvaW5n
IHRvIHNheSBzb21ldGhpbmcgaXMgYmV0dGVyLCBpdCB3b3VsZCBoZWxwIHRvIGNvbXBhcmUgdGhh
dCB0byBzb21ldGhpbmcgZWxzZSBpbiBvcmRlciB0byBwcm92aWRlIGJldHRlciBjbGFyaXR5LnBy
DQo+IA0KPiA9PT0NCj4gDQo+IFNlY3Rpb24gMToNCj4gDQo+IHMvaWRlYWwgbWVhbi9pZGVhbCBt
ZWFucy8NCj4gDQo+IHMvdGVsZW1ldHJ5IHJlbWFpbi90ZWxlbWV0cnkgcmVtYWlucy8NCj4gDQo+
ID09PQ0KPiANCj4gU2VjdGlvbiAyOg0KPiANCj4gVGhlIGZpcnN0IHNlbnRlbmNlIG9mIHlvdXIg
bW90aXZhdGlvbiBib3RoZXJzIG1lLiAgSSBkb27igJl0IGJ1eSBpdC4gIFllcywgc29tZSBhcmUg
dXNpbmcgbWFjaGluZSBsZWFybmluZyB0byBwdWxsIGluc2lnaHRzIG91dCBvZiDigJxiaWcgZGF0
YSzigJ0gYnV0IHRoZSB3YXkgdGhpcyByZWFkcywgQUkgaXMgY29tbW9ucGxhY2UgaW4gbmV0d29y
a2luZy4gIEkgd291bGQgc2F5IHRoaXMgaXMgc3RpbGwgdmVyeSBtdWNoIGluIG5pY2hlIGFyZWFz
IGFuZCByZXNlYXJjaC4gIE9uZSBrZXkgaXNzdWUgd2l0aCB0aGUgdmFzdCBhbW91bnRzIG9mIGRh
dGEgdGhhdCBzb21lIG5ldHdvcmtzIHByb2R1Y2UgaXMgc29ydGluZyB0aHJvdWdoIGl0IHRvIGZp
bmQgdXNlZnVsIGluZm9ybWF0aW9uLiAgTGFyZ2Ugb3BlcmF0b3JzIG1heSBoYXZlIHRoZSBtZWFu
cyB0byBkbyBNTCwgYnV0IG90aGVycyBzdHJ1Z2dsZSB0byBtYWtlIHNlbnNlIG9mIHRoaXMgZGF0
YS4NCj4gDQo+IFlvdSB1c2UgdGhlIHRlcm0gImludGVudC1kcml2ZW4gYXV0b25vbW91cyBuZXR3
b3JrLiIgIEkgYXNrZWQgYXJvdW5kIHdpdGggc29tZSBvcGVyYXRvcnMgYW5kIG90aGVyIHZlbmRv
cnMsIGFuZCB0aGlzIGlzIDEwMCUgYnV6eiB3b3JkLg0KPiBQZW9wbGUgZWl0aGVyIGRvbid0IGtu
b3cgd2hhdCBpdCBtZWFucyBvciBkZWZpbmUgaXQgdXNpbmcgZXZlbiBtb3JlIGJ1enp3b3Jkcy4g
IEkga25vdyBlYWNoIHZlbmRvciBoYXMgdGhlaXIgb3duIG1lYW5pbmcgZm9yIHRoaXMsIGJ1dCB0
aGVzZSB0ZXJtcyBvbiBub3Qgd2lkZWx5IGtub3duLiAgWW91ciBkb2N1bWVudCBhaW1zIHRvIGNs
YXJpZnkgdGF4b25vbXkuICBJIHdvdWxkIGNsYXJpZnkgdGhpcyBidXp6eSBwaHJhc2UuDQo+IA0K
PiBJbiB5b3VyIHRoaXJkIHBhcmFncmFwaCwgeW91IHNheSwgInRoZSBzeXN0ZW0gYm90dGxlbmVj
ayBpcyBzaGlmdGluZyBmcm9tIGRhdGEgY29uc3VtcHRpb24gdG8gZGF0YSBzdXBwbHkuIiAgSSBk
aXNhZ3JlZS4gIFRlbGVtZXRyeSBpcyBmdXJ0aGVyaW5nIHRoZSBkYXRhIGNvbnN1bXB0aW9uIHBy
b2JsZW0uICBNb3JlIGRhdGEgZG9lc24ndCBtZWFuIG1vcmUgaW5zaWdodC4gIE1vcmUgZGF0YSBt
ZWFucyBtb3JlIGhlYWRhY2hlLiAgSW4gYWRkaXRpb24gdG8gZ2V0dGluZyBtb3JlIGRhdGEgbW9y
ZSBlYXNpbHksIHdlIF9tdXN0XyBoYXZlIGEgd2F5IHRvIHRyYW5zbGF0ZSB0aGF0IGRhdGEgaW50
byB1c2VmdWwsIGFjdGlvbmFibGUgaW5mb3JtYXRpb24uICBUaGlzIGdvZXMgdG8gQmVub2l0J3Mg
dGFsayBvbiB0ZWxlbWV0cnkgb24gVGh1cnNkYXkgYXQgMTA0LiAgSG93IGRvIHdlIHVwLWxldmVs
IHRoZSB2YWx1ZSBvZiB0ZWxlbWV0cnk/DQo+IA0KPiA9PT0NCj4gDQo+IFNlY3Rpb24gMi4xOg0K
PiANCj4gcy9BbiBpbnRlbnRzL0FuIGludGVudC8NCj4gDQo+ID09PQ0KPiANCj4gU2VjdGlvbiAy
LjI6DQo+IA0KPiBUaGUgc2VudGVuY2UgIlRoZXNlIGNvbnZlbnRpb24gdGVjaG5pcXVlcyBhcmUg
bm90IHN1ZmZpY2llbnQgdG8gc3VwcG9ydCB0aGUgYWJvdmUgdXNlIGNhc2VzIGZvciB0aGUgZm9s
bG93aW5nIHJlYXNvbnM6IiBkb2Vzbid0IG1ha2Ugc2Vuc2UuDQo+IFRoZXJlIGFyZSBzb21lIGdy
YW1tYXRpY2FsIGlzc3VlcyBoZXJlLiAgQ29uc2lkZXIgcmVwaHJhc2luZy4gIE1heWJlLCAiVGhl
c2UgY29udmVudGlvbmFsIHRlY2huaXF1ZXMiLg0KPiANCj4gPT09DQo+IA0KPiBTZWN0aW9uIDIu
MzoNCj4gDQo+IFlvdSBkZWZpbmUgSUROIGFzIEludGVudC1Ecml2ZW4gTmV0d29yaywgYnV0IEkg
d291bGQgYWdhaW4gc2F5IHlvdSBuZWVkIHRvIGRlZmluZSB0aGlzIGluIGl0cyBlbnRpcmV0eSBz
byB0aGUgcmVhZGVyIGlzIGNsZWFyLiAgWW91IGRvIGRlZmluZSwgImFuIGludGVudCIgYnV0IElE
Ti9JQk4gaXMgbW9yZSBjb21wcmVoZW5zaXZlIHRoYW4gdGhhdC4NCj4gDQo+ID09PQ0KPiANCj4g
U2VjdGlvbiA0LjE6DQo+IA0KPiBzL2F2YWlhYmxlL2F2YWlsYWJsZS8NCj4gDQo+IFlvdSBkZWZp
bmUgZGlmZmVyZW50IHR5cGVzIG9mIHRlbGVtZXRyeSBkYXRhIGFzICJTaW1wbGUgRGF0YSIgYW5k
IHRoZW4gIkN1c3RvbSBEYXRhIi4gIE1pZ2h0IEkgc3VnZ2VzdCB5b3UgcmVuYW1lIEN1c3RvbSBE
YXRhIHRvIENvbXBsZXggRGF0YSBhcyAiY29tcGxleCIgdGVuZHMgdG8gdHlwaWNhbGx5IHJlZmVy
IHRvIHNvbWUgbGV2ZWwgb2YgbXVsdGlwbGUgY29tYmluYXRpb24gb3IgYWdncmVnYXRpb24uDQo+
IA0KPiA9PT0NCj4gDQo+IFNlY3Rpb24gNC4yOg0KPiANCj4gQ2FuIHlvdSB0YWxrIG1vcmUgYWJv
dXQgd2hhdCB5b3UgbWVhbiBieSBzb2NpYWwgZGF0YSBhbmQgd2h5IGVudmlyb25tZW50YWwgaXMg
ZGVmaW5lZCB0byBiZSBleHRlcm5hbD8gIEkgY2FuIGhhdmUgb24tYm9hcmQgc2Vuc29ycyB0aGF0
IHJlbGF5IGludGVybmFsIGVudmlyb25tZW50YWwgZGF0YS4NCj4gDQo+IFdoeSBpcyBleHRlcm5h
bCBkYXRhIG5vdCBvZmZlcmVkIG92ZXIgSFRUUD8gIEkgaW1hZ2luZSAic29jaWFsIiB3b3VsZCBi
ZSBIVFRQLCBidXQgd2l0aG91dCBtb3JlIGRlZmluaXRpb24sIEknbSBub3Qgc3VyZS4NCj4gDQo+
ID09PQ0KPiANCj4gU2VjdGlvbiA0LjQ6DQo+IA0KPiBXaHkgaXNuJ3QgZ1JQQyBsaXN0ZWQgaW4g
dGhlIFNpbXBsZSBEYXRhIHF1ZXJ5Pw0KPiANCj4gVW5kZXIgQ3VzdG9tIERhdGEgUXVlcnksIHRo
ZXJlIGlzIGEg4oCcWUFORyBGU03igJ0gZHJhZnQgYXMgYW4gaW5kaXZpZHVhbCBkcmFmdCBpbiBu
ZXRtb2QsIGJ1dCBpdOKAmXMgbm90IGNsZWFyIHdoYXQgdGhlIGZ1dHVyZSBpcy4gIFRoZXJlIHNl
ZW1zIHRvIGJlIGEgZ2VuZXJhbCB0aG91Z2h0IHRoYXQgZXZlbnQtZHJpdmVuIFlBTkcgaXMgdXNl
ZnVsLCBidXQgaWYgdGhhdCB3aWxsIGJlIGFuIEZTTSBwZXIgc2UgaXMgeWV0IHRvIGJlIHNlZW4u
DQo+IA0KPiBXaGF0IGlzIFBCVD8gIEkgZGlkbid0IHNlZSBpdCBpbiBnbG9zc2FyeS4NCj4gDQo+
ID09PQ0KPiANCj4gVGhhdCdzIGl0IGZvciBub3cuICBJIHRoaW5rIHRoaXMgd2lsbCBnaXZlIHlv
dSBhIGxvdCB0byBjaGV3IG9uLg0KPiANCj4gSm9lDQo+IA0KPiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBPUFNBV0cgbWFpbGluZyBsaXN0DQo+IE9Q
U0FXR0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29w
c2F3Zw0KDQo=


From nobody Sat May  4 20:32:49 2019
Return-Path: <zhoutianran@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695C812014E for <opsawg@ietfa.amsl.com>; Sat,  4 May 2019 20:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 Lv0ey0uwjfn7 for <opsawg@ietfa.amsl.com>; Sat,  4 May 2019 20:32:46 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 331511200D8 for <opsawg@ietf.org>; Sat,  4 May 2019 20:32:46 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id CC81EE08FFDBC018C9C2 for <opsawg@ietf.org>; Sun,  5 May 2019 04:32:43 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 5 May 2019 04:32:43 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Sun, 5 May 2019 11:32:39 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Minutes for 104
Thread-Index: AQHVAsOq7LR4S1eZ802KyMKxrGhc06Zb38Qg
Date: Sun, 5 May 2019 03:32:38 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21BEDDCC1A@NKGEML515-MBX.china.huawei.com>
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com>
In-Reply-To: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.156.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/WyffznSWcdG1f5D0abINJt547Og>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2019 03:32:48 -0000

Thanks Joe for the minute.
I just add the missing part on NTF.
https://datatracker.ietf.org/meeting/104/materials/minutes-104-opsawg-01


Cheers,
Tianran

> -----Original Message-----
> From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Joe Clarke
> (jclarke)
> Sent: Sunday, May 05, 2019 5:52 AM
> To: opsawg@ietf.org
> Subject: [OPSAWG] Minutes for 104
>=20
> After a long delay I have posted the draft minutes from the IETF 104 opsa=
wg/Ops
> Area session.  I took these from notes I did in Etherpad as well as the v=
ideo
> recording on YouTube.  I missed one Huawei name at the mic with the NTF d=
raft,
> but I think I captured most everything else.
>=20
> Please review and Tianran or I know what we need to change.
>=20
> Thanks.
>=20
> https://datatracker.ietf.org/meeting/104/materials/minutes-104-opsawg-00
>=20
> Joe
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


From nobody Wed May  8 03:12:15 2019
Return-Path: <ietfc@btconnect.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAEFE12022D for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 03:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level: 
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 HduKF9CJxnTG for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 03:12:11 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150120.outbound.protection.outlook.com [40.107.15.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26AF712003E for <opsawg@ietf.org>; Wed,  8 May 2019 03:12:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0XDkH+21oSLjlrJBMrICbljjP5J3YyKuPYed3XhdWhE=; b=GG51rmvV/3umFs1dlxKt3F7BzMaqix1z7Dq731IYXXRwL43Ugq2jVbRmCkV/b6Ik2rp0kxd031r6kvqczWuko+FNQgxl8SRYYlY9NUq4KhM9L1VZVkSwHQqVRCbVLoCYrQhY6GcHKEmGADb16sCUHuG43SXe6AOD4opd0PwH39I=
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com (10.175.242.156) by VI1PR07MB5886.eurprd07.prod.outlook.com (20.177.202.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.18; Wed, 8 May 2019 10:12:08 +0000
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b]) by VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b%3]) with mapi id 15.20.1878.019; Wed, 8 May 2019 10:12:08 +0000
From: tom petch <ietfc@btconnect.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Minutes for 104
Thread-Index: AQHVBYZ+PNi8GRISn0WMBzsAxPcPoQ==
Date: Wed, 8 May 2019 10:12:08 +0000
Message-ID: <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net>
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: LO2P265CA0329.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a4::29) To VI1PR07MB3118.eurprd07.prod.outlook.com (2603:10a6:802:20::28)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c88bbd01-6d19-45ab-c1b5-08d6d39da0e8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB5886; 
x-ms-traffictypediagnostic: VI1PR07MB5886:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <VI1PR07MB588691F9776B2544B891369DA0320@VI1PR07MB5886.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0031A0FFAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39860400002)(376002)(396003)(366004)(136003)(13464003)(189003)(199004)(66476007)(81166006)(26005)(8676002)(66946007)(73956011)(66446008)(64756008)(66556008)(186003)(81156014)(53546011)(386003)(229853002)(2906002)(3846002)(6506007)(86362001)(316002)(6486002)(6436002)(86152003)(25786009)(44736005)(8936002)(50226002)(6306002)(6512007)(9686003)(5660300002)(71190400001)(486006)(71200400001)(446003)(476003)(6246003)(7736002)(84392002)(256004)(4744005)(305945005)(53936002)(478600001)(44716002)(62236002)(52116002)(76176011)(6116002)(4720700003)(102836004)(81686011)(81816011)(61296003)(66066001)(14454004)(966005)(14496001)(99286004)(110136005)(1556002)(2501003)(68736007)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB5886; H:VI1PR07MB3118.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 7W4jQGeSd/sADXcjDEiOGRa4Mqv0wH3Edsf4aggUzCJwMxLuPYazqNUEGguoSiY0b7/ce42sGroYqMPTxFDIsHBg5ByXt9Oi2vwVzWGjN7ifwunamHhQnfG6YUhgBLOUEf4qztXdZ9RLY83AFjfjWfl+EdMZsiALCFwvgN8LDct81wZk6/TMTGeqY1DBrF90fyKExTsCgAhoYWx9B5KkjqJcs2RG7FzhzTx1bje/XL/TM0EJBUUSXvHsdWRgSuT9cQzdN53G6W2R/F7PoiLts/1otKqwDxfWVlvanvbCI7zgIcMxjW6DquZqZTHl8UVht/6r80Mh8JkGLZAotNv63Ntd4sBzhrtL4LHl1XuBVYhL11q+oIvpnBlTkQtWlewxiyJsiKWoffDLddXsOggtgEgOye8H5Hzv03Xb7LyAvp0=
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FE3096DF730E2249AF75E8E00439E2CA@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c88bbd01-6d19-45ab-c1b5-08d6d39da0e8
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2019 10:12:08.5676 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5886
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/tEOzdwSDteh7sV_aHH4GBIOXdY0>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 10:12:14 -0000

Joe

I am struck by

"CCMIB Sean Turner 5 minutes
Sean wants no one to comment and no one commented"

which seems consistent; no identifier for the whatever-it-is and so
no-one said anything!

Tom Petch

----- Original Message -----
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: <opsawg@ietf.org>
Sent: Saturday, May 04, 2019 10:52 PM
Subject: [OPSAWG] Minutes for 104


> After a long delay I have posted the draft minutes from the IETF 104
opsawg/Ops Area session.  I took these from notes I did in Etherpad as
well as the video recording on YouTube.  I missed one Huawei name at the
mic with the NTF draft, but I think I captured most everything else.
>
> Please review and Tianran or I know what we need to change.
>
> Thanks.
>
>
https://datatracker.ietf.org/meeting/104/materials/minutes-104-opsawg-00
>
> Joe
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


From nobody Wed May  8 07:25:17 2019
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399BF120289 for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 07:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 y0_hoYHRX_gX for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 07:24:57 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 163D312010C for <opsawg@ietf.org>; Wed,  8 May 2019 07:24:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1816; q=dns/txt; s=iport; t=1557325497; x=1558535097; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uJ+Q6K4a9E43aoL3HDagAELdMHdFqSbEDBZ6whOkUxY=; b=NIxq7ZYQ5IHadYovO6Zez0jVOcYcrY3mr8mlyZ9SbDfmBm1pJktJEOvC sTr70jV53L0AgEMTGylOy53LiJpLQaTfexfdj35RaPQj1JP8/dLs6KbJf bnOogyQ0Rcg+CHWAzSUNaKRjhY8cs7lXsONDnANl+3OZGzw3WeR+Q4KVy U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAACj5dJc/5hdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUgMBAQEBAQsBghBpVDAoCoQGlR6YUoF7CQcBARgNCoN?= =?us-ascii?q?5RgIXgXEjNQgOAQMBAQQBAQIBBG0cDIVKAQEBAwEBASEROgsFBwQCAQgRBAE?= =?us-ascii?q?BAQICJgICAiULFQgIAgQOBYMiAYF7Dw+tF4EvhDIBAwICgQ2EXQaBCycBi00?= =?us-ascii?q?XgUA/gTgfgTeBFT6CYQEBA4FeF4JzMoImBIsJgk2EbZR/CQKCCYYdjDIbghC?= =?us-ascii?q?GRItBgUKLb4cCjikCERWBMCABNoFWcBU7KgGCQYIbF4hghT9BMYF2jXiBIQE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.60,446,1549929600"; d="scan'208";a="559853685"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 May 2019 14:24:55 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x48EOtIS021002 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 May 2019 14:24:56 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 8 May 2019 09:24:55 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1473.003; Wed, 8 May 2019 09:24:55 -0500
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: tom petch <ietfc@btconnect.com>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Minutes for 104
Thread-Index: AQHVAsOqfBfQq0M+FUivFu/qx8odj6ZhoeYA
Date: Wed, 8 May 2019 14:24:55 +0000
Message-ID: <682E7E7C-84D8-4DAF-9F76-CE519682B8CB@cisco.com>
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com> <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net>
In-Reply-To: <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.87.86]
Content-Type: text/plain; charset="utf-8"
Content-ID: <565A7756F48E624E90F1F2B5BB32DCFF@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/qWowkmNbNgi7_RdvwLIWgsq939o>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 14:25:04 -0000

DQoNCj4gT24gTWF5IDgsIDIwMTksIGF0IDA2OjEyLCB0b20gcGV0Y2ggPGlldGZjQGJ0Y29ubmVj
dC5jb20+IHdyb3RlOg0KPiANCj4gSm9lDQo+IA0KPiBJIGFtIHN0cnVjayBieQ0KPiANCj4gIkND
TUlCIFNlYW4gVHVybmVyIDUgbWludXRlcw0KPiBTZWFuIHdhbnRzIG5vIG9uZSB0byBjb21tZW50
IGFuZCBubyBvbmUgY29tbWVudGVkIg0KPiANCj4gd2hpY2ggc2VlbXMgY29uc2lzdGVudDsgbm8g
aWRlbnRpZmllciBmb3IgdGhlIHdoYXRldmVyLWl0LWlzIGFuZCBzbw0KPiBuby1vbmUgc2FpZCBh
bnl0aGluZyENCg0KSSBkaWRu4oCZdCBrbm93IGhvdyB0byBzdW1tYXJpemUgdGhhdCBhbnkgZGlm
ZmVyZW50bHkuICBUaGF04oCZcyBtb3JlIG9yIGxlc3Mgd2hhdCBoZSBzYWlkIGF0IHRoZSBtaWMu
ICBCdXQgaGlzIHByZXNlbnRhdGlvbiBpcyB0aGVyZSBmb3IgdGhlIGRldGFpbHMgb2Ygd2hhdCBo
ZSB3YW50cy4gIA0KDQpKb2UNCg0KPiANCj4gVG9tIFBldGNoDQo+IA0KPiAtLS0tLSBPcmlnaW5h
bCBNZXNzYWdlIC0tLS0tDQo+IEZyb206ICJKb2UgQ2xhcmtlIChqY2xhcmtlKSIgPGpjbGFya2VA
Y2lzY28uY29tPg0KPiBUbzogPG9wc2F3Z0BpZXRmLm9yZz4NCj4gU2VudDogU2F0dXJkYXksIE1h
eSAwNCwgMjAxOSAxMDo1MiBQTQ0KPiBTdWJqZWN0OiBbT1BTQVdHXSBNaW51dGVzIGZvciAxMDQN
Cj4gDQo+IA0KPj4gQWZ0ZXIgYSBsb25nIGRlbGF5IEkgaGF2ZSBwb3N0ZWQgdGhlIGRyYWZ0IG1p
bnV0ZXMgZnJvbSB0aGUgSUVURiAxMDQNCj4gb3BzYXdnL09wcyBBcmVhIHNlc3Npb24uICBJIHRv
b2sgdGhlc2UgZnJvbSBub3RlcyBJIGRpZCBpbiBFdGhlcnBhZCBhcw0KPiB3ZWxsIGFzIHRoZSB2
aWRlbyByZWNvcmRpbmcgb24gWW91VHViZS4gIEkgbWlzc2VkIG9uZSBIdWF3ZWkgbmFtZSBhdCB0
aGUNCj4gbWljIHdpdGggdGhlIE5URiBkcmFmdCwgYnV0IEkgdGhpbmsgSSBjYXB0dXJlZCBtb3N0
IGV2ZXJ5dGhpbmcgZWxzZS4NCj4+IA0KPj4gUGxlYXNlIHJldmlldyBhbmQgVGlhbnJhbiBvciBJ
IGtub3cgd2hhdCB3ZSBuZWVkIHRvIGNoYW5nZS4NCj4+IA0KPj4gVGhhbmtzLg0KPj4gDQo+PiAN
Cj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzEwNC9tYXRlcmlhbHMvbWlu
dXRlcy0xMDQtb3BzYXdnLTAwDQo+PiANCj4+IEpvZQ0KPj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IE9QU0FXRyBtYWlsaW5nIGxpc3QNCj4+IE9Q
U0FXR0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9v
cHNhd2cNCj4gDQoNCg==


From nobody Wed May  8 08:37:44 2019
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26DE4120127 for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 08:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 moL-z_oSmOCG for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 08:37:40 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F61B120123 for <opsawg@ietf.org>; Wed,  8 May 2019 08:37:40 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id m32so20628034qtf.0 for <opsawg@ietf.org>; Wed, 08 May 2019 08:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kWRHvgceMdP6aHSFAyTHmA6yjsEHTL5Tpaw3CoYPJ9M=; b=YSLEGSng8u4Yc6JuXHZC/Uu4svJE68EU4eU7UOIMPshgTvkM+za440jg0NZY3oZPhO VXnGW6XK6+3DkrajGY8S0Bb0pODazQUcuiFku8Ui44xSOYpYv5wdtPb0xR8uXFVDo5NC k5mqlEZ91bR0QVAvlYO+py/kjSOrKdVR32PN14lseXOLnKYlkjQiAfWz4wUhDuMF7obF 83GcjyfyIt45IlqpfagI4hFni1XoR4Jsa9hOmHipTcWHw8VY6YHj0gRlgD2qUiatRLOo FBnW1RMeDcq5myas6c8EU3LQ5AC18gP/+Dc8yxMohcNb7+M2JPrO6DsiqtA9cdo9HXoE 4H0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kWRHvgceMdP6aHSFAyTHmA6yjsEHTL5Tpaw3CoYPJ9M=; b=nTQRGCzaNgvAFtGFNCCTBjViBAAwKdiJ8CJxCzbs6ALsFMKBbAU3IiArtScHixiDIk xHlXBMdDgTjWoJKoVIjTkdjOeNnczjl24mEq8aN8eZON1ULAjdKQH9rLCVfK1Kx2ysAB JMzjRfScjd14K3CTZY59cGEHze9xHI/aIPt3Pwa201oHmO8N0S9uv/yiVwOwn9JsxaQL ZmZsV0RshKqbcGsgYMp2UJgDaUITdH44hYviU33mmwJ9t4Em0MXbo/RGXqq84BhI9qgx LFVHB1IoT6TgMLV/9/4UbxdmvMZtyOzKBBwjZ9x0upa+D9Z1VneYg+0kToL0rK12FA0Y uyfw==
X-Gm-Message-State: APjAAAUuUrbKU1/ur9he0q4lO0SMUVFQWIDuzpW9KDp2cY84qFcriCAA Amb4ZpyKs/c1vA7kdVs+zwevNy6jVa9p8fs768Ax2g==
X-Google-Smtp-Source: APXvYqy61O5M3RsiX0wx1T76fTsOGg1lP2dJB70pXEcA8EqNckwa/jMPuNxULfXY8C5uNkJGpjL5gYbdE0TPRbJhVR8=
X-Received: by 2002:a0c:c16c:: with SMTP id i41mr31879627qvh.183.1557329858670;  Wed, 08 May 2019 08:37:38 -0700 (PDT)
MIME-Version: 1.0
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com> <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net> <682E7E7C-84D8-4DAF-9F76-CE519682B8CB@cisco.com>
In-Reply-To: <682E7E7C-84D8-4DAF-9F76-CE519682B8CB@cisco.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 8 May 2019 11:37:27 -0400
Message-ID: <CAHw9_iLVYOhdpxqzFuE6ms7TivJpQsPTE-wRzh+kp_jX6Uv9dg@mail.gmail.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, tom petch <ietfc@btconnect.com>
Content-Type: multipart/alternative; boundary="00000000000006427f0588621d5d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/NnYge2LxuKs8hhTIdEoFMvykzUA>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 15:37:43 -0000

--00000000000006427f0588621d5d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This was largely a =E2=80=9Chere is a document which we want to send throug=
h the
ISE, does the WG want it instead / anyone have any objections?=E2=80=9D

He and I had decided that it was polite to check with the WG, even though
we were fairly sure the WG would not want it...

W

On Wed, May 8, 2019 at 10:25 AM Joe Clarke (jclarke) <jclarke@cisco.com>
wrote:

>
>
> > On May 8, 2019, at 06:12, tom petch <ietfc@btconnect.com> wrote:
> >
> > Joe
> >
> > I am struck by
> >
> > "CCMIB Sean Turner 5 minutes
> > Sean wants no one to comment and no one commented"
> >
> > which seems consistent; no identifier for the whatever-it-is and so
> > no-one said anything!
>
> I didn=E2=80=99t know how to summarize that any differently.  That=E2=80=
=99s more or less
> what he said at the mic.  But his presentation is there for the details o=
f
> what he wants.
>
> Joe
>
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
> > To: <opsawg@ietf.org>
> > Sent: Saturday, May 04, 2019 10:52 PM
> > Subject: [OPSAWG] Minutes for 104
> >
> >
> >> After a long delay I have posted the draft minutes from the IETF 104
> > opsawg/Ops Area session.  I took these from notes I did in Etherpad as
> > well as the video recording on YouTube.  I missed one Huawei name at th=
e
> > mic with the NTF draft, but I think I captured most everything else.
> >>
> >> Please review and Tianran or I know what we need to change.
> >>
> >> Thanks.
> >>
> >>
> > https://datatracker.ietf.org/meeting/104/materials/minutes-104-opsawg-0=
0
> >>
> >> Joe
> >> _______________________________________________
> >> OPSAWG mailing list
> >> OPSAWG@ietf.org
> >> https://www.ietf.org/mailman/listinfo/opsawg
> >
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>
--=20
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf

--00000000000006427f0588621d5d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"auto">This was largely a =E2=80=9Chere is a document which=
 we want to send through the ISE, does the WG want it instead / anyone have=
 any objections?=E2=80=9D</div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">He and I had decided that it was polite to check with the WG, eve=
n though we were fairly sure the WG would not want it...</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">W</div><div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Wed, May 8, 2019 at 10:25 AM Joe =
Clarke (jclarke) &lt;<a href=3D"mailto:jclarke@cisco.com">jclarke@cisco.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
&gt; On May 8, 2019, at 06:12, tom petch &lt;<a href=3D"mailto:ietfc@btconn=
ect.com" target=3D"_blank">ietfc@btconnect.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Joe<br>
&gt; <br>
&gt; I am struck by<br>
&gt; <br>
&gt; &quot;CCMIB Sean Turner 5 minutes<br>
&gt; Sean wants no one to comment and no one commented&quot;<br>
&gt; <br>
&gt; which seems consistent; no identifier for the whatever-it-is and so<br=
>
&gt; no-one said anything!<br>
<br>
I didn=E2=80=99t know how to summarize that any differently.=C2=A0 That=E2=
=80=99s more or less what he said at the mic.=C2=A0 But his presentation is=
 there for the details of what he wants.=C2=A0 <br>
<br>
Joe<br>
<br>
&gt; <br>
&gt; Tom Petch<br>
&gt; <br>
&gt; ----- Original Message -----<br>
&gt; From: &quot;Joe Clarke (jclarke)&quot; &lt;<a href=3D"mailto:jclarke@c=
isco.com" target=3D"_blank">jclarke@cisco.com</a>&gt;<br>
&gt; To: &lt;<a href=3D"mailto:opsawg@ietf.org" target=3D"_blank">opsawg@ie=
tf.org</a>&gt;<br>
&gt; Sent: Saturday, May 04, 2019 10:52 PM<br>
&gt; Subject: [OPSAWG] Minutes for 104<br>
&gt; <br>
&gt; <br>
&gt;&gt; After a long delay I have posted the draft minutes from the IETF 1=
04<br>
&gt; opsawg/Ops Area session.=C2=A0 I took these from notes I did in Etherp=
ad as<br>
&gt; well as the video recording on YouTube.=C2=A0 I missed one Huawei name=
 at the<br>
&gt; mic with the NTF draft, but I think I captured most everything else.<b=
r>
&gt;&gt; <br>
&gt;&gt; Please review and Tianran or I know what we need to change.<br>
&gt;&gt; <br>
&gt;&gt; Thanks.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt; <a href=3D"https://datatracker.ietf.org/meeting/104/materials/minutes-=
104-opsawg-00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.iet=
f.org/meeting/104/materials/minutes-104-opsawg-00</a><br>
&gt;&gt; <br>
&gt;&gt; Joe<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; OPSAWG mailing list<br>
&gt;&gt; <a href=3D"mailto:OPSAWG@ietf.org" target=3D"_blank">OPSAWG@ietf.o=
rg</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/opsawg</a=
><br>
&gt; <br>
<br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org" target=3D"_blank">OPSAWG@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature">I don&#39;t think the execution is relev=
ant when it was obviously a bad idea in the first place.<br>This is like pu=
tting rabid weasels in your pants, and later expressing regret at having ch=
osen those particular rabid weasels and that pair of pants.<br>=C2=A0 =C2=
=A0---maf</div>

--00000000000006427f0588621d5d--


From nobody Wed May  8 15:37:55 2019
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E3012013E for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 15:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 SarCgA6GWa5i for <opsawg@ietfa.amsl.com>; Wed,  8 May 2019 15:37:51 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6DBA1200EF for <opsawg@ietf.org>; Wed,  8 May 2019 15:37:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2116; q=dns/txt; s=iport; t=1557355071; x=1558564671; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=/rjOZnrySB3s+ZFFzw8KyjUkcfAmJr8FSKsBOSJ0+P8=; b=lbCBUcrnZG89W3aHcBHjnGywsGki6QYDLHANgNXiUyvoWEAxCk/nb5eP KjQ5Vo+a7p/wK+PdHLk59SfvZNuVcemrF/r3sKOml92Io0HZG+iPi+ga4 ETGwe+/epedEusP266WmPJEi4aqEZBqvHp3tejdHRx+okr+HqI776Xp03 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAAAAWtNc/5pdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBghBpVDAoCoQHiByMXSWYUoF7CQcBARg?= =?us-ascii?q?NCoN5RgIXgXEjNAkOAQMBAQQBAQIBBG0cDIVKAQEBAwEBASEROgsFBwQCAQg?= =?us-ascii?q?RBAEBAQICJgICAiULFQgIAgQOBYMiAYF7Dw+tYIEvhDIBAwICgQ2EXwaBCyc?= =?us-ascii?q?Bi00XgUA/gREnDBOBN4EVPoJhAQEDgV4XgnMygiYEiw+CR4RtgXKTDQkCggm?= =?us-ascii?q?GHYwyG4IQhkSLQYFCi2+HAo4pAhEVgTAfOIFWcBU7KgGCQYIbF4hghT9BMYF?= =?us-ascii?q?2jTGBIQEB?=
X-IronPort-AV: E=Sophos;i="5.60,447,1549929600"; d="scan'208";a="545186879"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 May 2019 22:37:40 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x48MbeMI013522 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 May 2019 22:37:40 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 8 May 2019 17:37:39 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1473.003; Wed, 8 May 2019 17:37:39 -0500
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: tom petch <ietfc@btconnect.com>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Minutes for 104
Thread-Index: AQHVAsOqfBfQq0M+FUivFu/qx8odj6ZiK5KA
Date: Wed, 8 May 2019 22:37:39 +0000
Message-ID: <51686EE9-2261-4FBD-8E32-8A21371B6642@cisco.com>
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com> <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net>
In-Reply-To: <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.87.86]
Content-Type: text/plain; charset="utf-8"
Content-ID: <AC0D9FBC06B6F84BA37916D240EF64FE@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/_IcbB91_Vvt1qJsH8Z4Em4EtI5Q>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 22:37:54 -0000

DQoNCj4gT24gTWF5IDgsIDIwMTksIGF0IDA2OjEyLCB0b20gcGV0Y2ggPGlldGZjQGJ0Y29ubmVj
dC5jb20+IHdyb3RlOg0KPiANCj4gSm9lDQo+IA0KPiBJIGFtIHN0cnVjayBieQ0KPiANCj4gIkND
TUlCIFNlYW4gVHVybmVyIDUgbWludXRlcw0KPiBTZWFuIHdhbnRzIG5vIG9uZSB0byBjb21tZW50
IGFuZCBubyBvbmUgY29tbWVudGVkIg0KPiANCj4gd2hpY2ggc2VlbXMgY29uc2lzdGVudDsgbm8g
aWRlbnRpZmllciBmb3IgdGhlIHdoYXRldmVyLWl0LWlzIGFuZCBzbw0KPiBuby1vbmUgc2FpZCBh
bnl0aGluZyENCg0KVG9tLCB0byB5b3VyIHBvaW50IGFib3V0IGFuIGlkZW50aWZpZXIsIEkgdXBs
b2FkZWQgYSByZXZpc2lvbiB0byB0aGUgbWludXRlcyB0aGF0IGluY2x1ZGVzIHRoZSBsaW5rIHRv
IHRoZSBub3ctZXhwaXJlZCBkcmFmdCBvbiB3aGljaCBTZWFu4oCZcyBwcmVzZW50YXRpb24gd2Fz
IGJhc2VkLg0KDQpBcyBXYXJyZW4gc2FpZCAoYW5kIGlzIHN0YXRlZCBpbiBTZWFu4oCZcyBzbGlk
ZXMpLCB0aGlzIHdhcyBzb2NpYWxpemF0aW9uIG9mIHdvcmsgc28gdGhhdCBpdCBkaWRu4oCZdCBi
bGluZHNpZGUgdGhlIHdvcmtpbmcgZ3JvdXAgYXMgaXQgcHJvZ3Jlc3NlcyB0byB0aGUgSUVTRy4g
IEkgYWxzbyBhZGRlZCBzb21lIGFkZGl0aW9uYWwgbWludXRlcyB0ZXh0IHRvIHRoYXQgZWZmZWN0
Lg0KDQpKb2UNCg0KPiANCj4gVG9tIFBldGNoDQo+IA0KPiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tDQo+IEZyb206ICJKb2UgQ2xhcmtlIChqY2xhcmtlKSIgPGpjbGFya2VAY2lzY28uY29t
Pg0KPiBUbzogPG9wc2F3Z0BpZXRmLm9yZz4NCj4gU2VudDogU2F0dXJkYXksIE1heSAwNCwgMjAx
OSAxMDo1MiBQTQ0KPiBTdWJqZWN0OiBbT1BTQVdHXSBNaW51dGVzIGZvciAxMDQNCj4gDQo+IA0K
Pj4gQWZ0ZXIgYSBsb25nIGRlbGF5IEkgaGF2ZSBwb3N0ZWQgdGhlIGRyYWZ0IG1pbnV0ZXMgZnJv
bSB0aGUgSUVURiAxMDQNCj4gb3BzYXdnL09wcyBBcmVhIHNlc3Npb24uICBJIHRvb2sgdGhlc2Ug
ZnJvbSBub3RlcyBJIGRpZCBpbiBFdGhlcnBhZCBhcw0KPiB3ZWxsIGFzIHRoZSB2aWRlbyByZWNv
cmRpbmcgb24gWW91VHViZS4gIEkgbWlzc2VkIG9uZSBIdWF3ZWkgbmFtZSBhdCB0aGUNCj4gbWlj
IHdpdGggdGhlIE5URiBkcmFmdCwgYnV0IEkgdGhpbmsgSSBjYXB0dXJlZCBtb3N0IGV2ZXJ5dGhp
bmcgZWxzZS4NCj4+IA0KPj4gUGxlYXNlIHJldmlldyBhbmQgVGlhbnJhbiBvciBJIGtub3cgd2hh
dCB3ZSBuZWVkIHRvIGNoYW5nZS4NCj4+IA0KPj4gVGhhbmtzLg0KPj4gDQo+PiANCj4gaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzEwNC9tYXRlcmlhbHMvbWludXRlcy0xMDQt
b3BzYXdnLTAwDQo+PiANCj4+IEpvZQ0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+IE9QU0FXRyBtYWlsaW5nIGxpc3QNCj4+IE9QU0FXR0BpZXRm
Lm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHNhd2cNCj4g
DQoNCg==


From nobody Fri May 10 09:46:32 2019
Return-Path: <ietfc@btconnect.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC64C1201EB for <opsawg@ietfa.amsl.com>; Fri, 10 May 2019 09:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level: 
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 bgP8rKvGkeBg for <opsawg@ietfa.amsl.com>; Fri, 10 May 2019 09:46:23 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70100.outbound.protection.outlook.com [40.107.7.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D215C1200FF for <opsawg@ietf.org>; Fri, 10 May 2019 09:46:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RscfvneLr2vtwxsSLqlp23cIVZnpSVJrIMRdIdtxppQ=; b=e0ia03JbmqNaaeAlgZfp8j1uSMM5UnU0CmhVLbDp9WJInlPWHhW0S9ZDbhCir3b/XHpFi3pkBimr61kq6N1fSoflMWHuQTgTIqIUU+twdFsrESWUjNB20LScXof8mO4SESye7QgsODKhYFADNnFwR41Mzp69fcWI4qHaIj8GUEU=
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com (10.175.242.156) by VI1PR07MB5038.eurprd07.prod.outlook.com (20.177.203.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.18; Fri, 10 May 2019 16:46:20 +0000
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b]) by VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b%3]) with mapi id 15.20.1900.006; Fri, 10 May 2019 16:46:20 +0000
From: tom petch <ietfc@btconnect.com>
To: Warren Kumari <warren@kumari.net>, "Joe Clarke (jclarke)" <jclarke@cisco.com>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Minutes for 104
Thread-Index: AQHVBYZ+PNi8GRISn0WMBzsAxPcPoQ==
Date: Fri, 10 May 2019 16:46:20 +0000
Message-ID: <011801d5074f$61e66e80$4001a8c0@gateway.2wire.net>
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com> <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net> <682E7E7C-84D8-4DAF-9F76-CE519682B8CB@cisco.com> <CAHw9_iLVYOhdpxqzFuE6ms7TivJpQsPTE-wRzh+kp_jX6Uv9dg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: LNXP265CA0088.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:76::28) To VI1PR07MB3118.eurprd07.prod.outlook.com (2603:10a6:802:20::28)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 705208a4-b88a-4431-20d7-08d6d567071c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB5038; 
x-ms-traffictypediagnostic: VI1PR07MB5038:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <VI1PR07MB50383AB20A50A6E6EC87AC3DA00C0@VI1PR07MB5038.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0033AAD26D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(346002)(39860400002)(376002)(13464003)(51914003)(189003)(199004)(446003)(71200400001)(86152003)(62236002)(71190400001)(61296003)(186003)(102836004)(44716002)(476003)(50226002)(14496001)(4720700003)(66066001)(2906002)(84392002)(478600001)(966005)(6116002)(14454004)(66476007)(81156014)(8676002)(81166006)(99286004)(8936002)(66946007)(73956011)(66446008)(64756008)(66556008)(3846002)(305945005)(81686011)(9686003)(4326008)(76176011)(81816011)(6246003)(7736002)(6306002)(1556002)(256004)(68736007)(486006)(6486002)(53936002)(86362001)(229853002)(5660300002)(316002)(110136005)(52116002)(6512007)(26005)(25786009)(53546011)(44736005)(6506007)(386003)(6436002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB5038; H:VI1PR07MB3118.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: kqEwIkZEBX/vD+S3VYcrsZgHrOQ2WvbQZit6OX4zhn0lT7/dxuseUvKBz0cX+K82Q8Ht+Z3Hr1w1M1BZZLlLQJJbtsK5jqQd2rNHaIqN/w3+UqK029ABclwC1Hnzqny+/JIU7FClDYtzd6VzSt1sZxW+4P7pdjt9rVfgq80X28kJAiMA6MZHfsXYdywtWjiMM0F6Z+p9GH7HoMlQt9+Bnjr5b9TczAyg8BzWNxxIY6JymsRGRHQ8lj8JPAuxPzotUP5PS52Db05XH1Xg7RMFnFRmyHqqBBimnVDUGJbnAXwvsoJ3EFTETUvN971OZCpELcYLhNv8UTsZf9L0PIBwGj2rpRvIWdXZJ0okT99bmhEeHZoumCM9ulydOnswKTwQqliuL1jOg/pxu0EpQhlIbrOqkuSgmJ7pC9GLIoMXLik=
Content-Type: text/plain; charset="utf-8"
Content-ID: <76FBBCCC3D222B4D8A781427261693AC@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 705208a4-b88a-4431-20d7-08d6d567071c
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2019 16:46:20.1103 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5038
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/R-uoM7ndMCpHLXG40yaOtTk2DZw>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 16:46:28 -0000

V2FycmVuDQoNClRoYW5rcyBmb3IgdGhlIGluZm8uDQoNCkl0IHNlZW1zIHRvIG1lIHRoYXQNCmRy
YWZ0LXR1cm5lci1jY21pYi0wMg0KaXMgZG9pbmcgZm9yIFNNSSB3aGF0IGEgbnVtYmVyIG9mIEkt
RCBhcmUgc3RydWdnbGluZyAoSU1ITykgdG8gZG8gZm9yDQpORVRDT05GL1lBTkcgcmlnaHQgbm93
Lg0KDQpBcGFydCBmcm9tIHRoZSBvdmVyYWxsIG9iamVjdGl2ZSBlLmcuDQoiaXQgZGVzY3JpYmVz
IG1hbmFnZWQgb2JqZWN0cyB1c2VkIHRvDQogICBtYW5hZ2Uga2V5IG1hbmFnZW1lbnQgaW1wbGVt
ZW50YXRpb25zIGluY2x1ZGluZyBhc3ltbWV0cmljIGtleXMsDQogICBzeW1tZXRyaWMga2V5cywg
dHJ1c3QgYW5jaG9ycywgYW5kIGNyeXB0b2dyYXBoaWMtcmVsYXRlZCBmaXJtd2FyZSINCnRoZXkg
c2VlbSB0byBoYXZlIGxpdHRsZSBvciBub3RoaW5nIGluIGNvbW1vbjsgYW5kIEkga25vdyB3aGlj
aCBhcHByb2FjaA0Kc2VlbXMsIHRvIGEgbm9uLWNyeXB0b2dyYXBoZXIgbGlrZSBtZSwgdG8gaGF2
ZSB0aGUgcmlnaHQgcmVzb25hbmNlLg0KDQpJdCBpcyBoYXJkIHRvIGJlIHNwZWNpZmljIGJlY2F1
c2UNCmRyYWZ0LXR1cm5lci1jY21pYi0wMg0KaXMgZGlzYXN0cm91c2x5IHNob3J0IG9mIGRlc2Ny
aXB0aXZlIHRleHQsIG5vdCBmaXQgdG8gYmUgYW4gUkZDIElNSE8uDQpJdCB3b3VsZCBiZSBhIHNo
YW1lIGlmIGl0IHdlcmUgdG8gcHJvY2VlZCBpbiBpdHMgcHJlc2VudCBmb3JtIGp1c3QgYXMgaXQN
CndvdWxkIGJlIGEgc2hhbWUgaWYgdGhlIGNvbnRlbnRzIHdlcmUgbm90IHVzZWQgdG8gaW5mb3Jt
IHRob3NlIHdvcmtpbmcNCm9uIHRoZSBORVRDT05GL05FVE1PRCBlcXVpdmFsZW50cy4NCg0KVG9t
IFBldGNoDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206ICJXYXJyZW4gS3Vt
YXJpIiB3YXJyZW5Aa3VtYXJpLm5ldA0KU2VudDogV2VkbmVzZGF5LCBNYXkgMDgsIDIwMTkgNDoz
NyBQTQ0KDQpUaGlzIHdhcyBsYXJnZWx5IGEg4oCcaGVyZSBpcyBhIGRvY3VtZW50IHdoaWNoIHdl
IHdhbnQgdG8gc2VuZCB0aHJvdWdoIHRoZQ0KSVNFLCBkb2VzIHRoZSBXRyB3YW50IGl0IGluc3Rl
YWQgLyBhbnlvbmUgaGF2ZSBhbnkgb2JqZWN0aW9ucz/igJ0NCg0KSGUgYW5kIEkgaGFkIGRlY2lk
ZWQgdGhhdCBpdCB3YXMgcG9saXRlIHRvIGNoZWNrIHdpdGggdGhlIFdHLCBldmVuDQp0aG91Z2gN
CndlIHdlcmUgZmFpcmx5IHN1cmUgdGhlIFdHIHdvdWxkIG5vdCB3YW50IGl0Li4uDQoNClcNCg0K
T24gV2VkLCBNYXkgOCwgMjAxOSBhdCAxMDoyNSBBTSBKb2UgQ2xhcmtlIChqY2xhcmtlKSA8amNs
YXJrZUBjaXNjby5jb20+DQp3cm90ZToNCg0KPg0KPg0KPiA+IE9uIE1heSA4LCAyMDE5LCBhdCAw
NjoxMiwgdG9tIHBldGNoIDxpZXRmY0BidGNvbm5lY3QuY29tPiB3cm90ZToNCj4gPg0KPiA+IEpv
ZQ0KPiA+DQo+ID4gSSBhbSBzdHJ1Y2sgYnkNCj4gPg0KPiA+ICJDQ01JQiBTZWFuIFR1cm5lciA1
IG1pbnV0ZXMNCj4gPiBTZWFuIHdhbnRzIG5vIG9uZSB0byBjb21tZW50IGFuZCBubyBvbmUgY29t
bWVudGVkIg0KPiA+DQo+ID4gd2hpY2ggc2VlbXMgY29uc2lzdGVudDsgbm8gaWRlbnRpZmllciBm
b3IgdGhlIHdoYXRldmVyLWl0LWlzIGFuZCBzbw0KPiA+IG5vLW9uZSBzYWlkIGFueXRoaW5nIQ0K
Pg0KPiBJIGRpZG7igJl0IGtub3cgaG93IHRvIHN1bW1hcml6ZSB0aGF0IGFueSBkaWZmZXJlbnRs
eS4gIFRoYXTigJlzIG1vcmUgb3INCmxlc3MNCj4gd2hhdCBoZSBzYWlkIGF0IHRoZSBtaWMuICBC
dXQgaGlzIHByZXNlbnRhdGlvbiBpcyB0aGVyZSBmb3IgdGhlDQpkZXRhaWxzIG9mDQo+IHdoYXQg
aGUgd2FudHMuDQo+DQo+IEpvZQ0KPg0KPiA+DQo+ID4gVG9tIFBldGNoDQo+ID4NCj4gPiAtLS0t
LSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQo+ID4gRnJvbTogIkpvZSBDbGFya2UgKGpjbGFya2Up
IiA8amNsYXJrZUBjaXNjby5jb20+DQo+ID4gVG86IDxvcHNhd2dAaWV0Zi5vcmc+DQo+ID4gU2Vu
dDogU2F0dXJkYXksIE1heSAwNCwgMjAxOSAxMDo1MiBQTQ0KPiA+IFN1YmplY3Q6IFtPUFNBV0dd
IE1pbnV0ZXMgZm9yIDEwNA0KPiA+DQo+ID4NCj4gPj4gQWZ0ZXIgYSBsb25nIGRlbGF5IEkgaGF2
ZSBwb3N0ZWQgdGhlIGRyYWZ0IG1pbnV0ZXMgZnJvbSB0aGUgSUVURg0KMTA0DQo+ID4gb3BzYXdn
L09wcyBBcmVhIHNlc3Npb24uICBJIHRvb2sgdGhlc2UgZnJvbSBub3RlcyBJIGRpZCBpbiBFdGhl
cnBhZA0KYXMNCj4gPiB3ZWxsIGFzIHRoZSB2aWRlbyByZWNvcmRpbmcgb24gWW91VHViZS4gIEkg
bWlzc2VkIG9uZSBIdWF3ZWkgbmFtZSBhdA0KdGhlDQo+ID4gbWljIHdpdGggdGhlIE5URiBkcmFm
dCwgYnV0IEkgdGhpbmsgSSBjYXB0dXJlZCBtb3N0IGV2ZXJ5dGhpbmcgZWxzZS4NCj4gPj4NCj4g
Pj4gUGxlYXNlIHJldmlldyBhbmQgVGlhbnJhbiBvciBJIGtub3cgd2hhdCB3ZSBuZWVkIHRvIGNo
YW5nZS4NCj4gPj4NCj4gPj4gVGhhbmtzLg0KPiA+Pg0KPiA+Pg0KPiA+DQpodHRwczovL2RhdGF0
cmFja2VyLmlldGYub3JnL21lZXRpbmcvMTA0L21hdGVyaWFscy9taW51dGVzLTEwNC1vcHNhd2ct
MDANCj4gPj4NCj4gPj4gSm9lDQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+ID4+IE9QU0FXRyBtYWlsaW5nIGxpc3QNCj4gPj4gT1BTQVdHQGll
dGYub3JnDQo+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb3BzYXdn
DQo+ID4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gT1BTQVdHIG1haWxpbmcgbGlzdA0KPiBPUFNBV0dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHNhd2cNCj4NCi0tDQpJIGRvbid0IHRoaW5r
IHRoZSBleGVjdXRpb24gaXMgcmVsZXZhbnQgd2hlbiBpdCB3YXMgb2J2aW91c2x5IGEgYmFkIGlk
ZWENCmluDQp0aGUgZmlyc3QgcGxhY2UuDQpUaGlzIGlzIGxpa2UgcHV0dGluZyByYWJpZCB3ZWFz
ZWxzIGluIHlvdXIgcGFudHMsIGFuZCBsYXRlciBleHByZXNzaW5nDQpyZWdyZXQgYXQgaGF2aW5n
IGNob3NlbiB0aG9zZSBwYXJ0aWN1bGFyIHJhYmlkIHdlYXNlbHMgYW5kIHRoYXQgcGFpciBvZg0K
cGFudHMuDQogICAtLS1tYWYNCg0K


From nobody Mon May 13 05:54:27 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E14D41200EB; Mon, 13 May 2019 05:54:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: opsawg@ietf.org, ietf@ietf.org, draft-ietf-opsawg-tacacs.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <155775206584.23645.18248080061887454144@ietfa.amsl.com>
Date: Mon, 13 May 2019 05:54:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/RlLwGMZtPQi-q9gPMvjt3JlxiXs>
Subject: [OPSAWG] Genart telechat review of draft-ietf-opsawg-tacacs-13
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2019 12:54:26 -0000

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-opsawg-tacacs-13
Reviewer: Stewart Bryant
Review Date: 2019-05-13
IETF LC End Date: None
IESG Telechat date: 2019-05-16

Summary:

There are a number of issues called out below that need addressing before publication.

Someone needs to micro-check the text to make sure that all terms are defined and referenced.
I picked up a few, but there were a lot I did not have time to check.

Major issues:

SB> The IANA section should ask IANA to point to this RFC as a reference
SB> for port 49

============


   The first MD5 hash is generated by concatenating the session_id, the
   secret key, the version number and the sequence number and then
   running MD5 over that stream.  All of those input values are
   available in the packet header, except for the secret key which is a
   shared secret between the TACACS+ client and server.

SB> MD5 make a good checksum, but I am surprised to see it used in this
SB> application in a new protocol.

=============

   All TACACS+ packets begin with the following 12-byte header.  The
   header describes the remainder of the packet:

SB> If ever there was an error in a long term session, how
SB> how would you find in in the following packet structure?
SB> Presumably from an incorrect major version and sequence number?

SB> Some details on the error cases and the unconditional "safety"
SB> of the protocol would be useful.

==========

      TAC_PLUS_AUTHEN_TYPE_ASCII := 0x01

      TAC_PLUS_AUTHEN_TYPE_PAP := 0x02

      TAC_PLUS_AUTHEN_TYPE_CHAP := 0x03

      TAC_PLUS_AUTHEN_TYPE_ARAP := 0x04 (deprecated)

      TAC_PLUS_AUTHEN_TYPE_MSCHAP := 0x05

      TAC_PLUS_AUTHEN_TYPE_MSCHAPV2 := 0x06



SB> There are lots of lists similar to the above.
SB> I have not checked them all, but a number of the types 
SB> in this and subsequent parts of the design don't seem
SB> to be defined or have a definitive reference

===========

 The START packet MUST contain a username and the data
   field MUST contain the PAP ASCII password.  A PAP authentication only
   consists of a username and password RFC 1334 [RFC1334] . The REPLY
   from the server MUST be either a PASS, FAIL or ERROR.

SB> Should there note be a note that RFC1334 is obsolete?

===========

Minor issues:

The use of the term "packet" as a unit of data is confusing, since the protocol
is carried over TCP which is a streaming protocol.

They are really TACAS+ PDUs

=========

(For example, Cisco uses "tty10"
   to denote the tenth tty line and "Async10" to denote the tenth async
   interface).  
SB> Is it correct to quote a particular vendor in an RFC of this type?

========

      TAC_PLUS_PRIV_LVL_MAX := 0x0f

      TAC_PLUS_PRIV_LVL_ROOT := 0x0f

      TAC_PLUS_PRIV_LVL_USER := 0x01

      TAC_PLUS_PRIV_LVL_MIN := 0x00

SB> Where are these defined?

========
Nits/editorial comments:

      The normative description of Legacy features such as ARAP and
SB> ARAP not expanded anywhere in document.

=====

SB> telnet and rlogin need references

=====
   is the user is connected via ISDN or a POTS, 
SB> Are ISDN and POTS well known IETF terms?

=====

   It is not legal for an attribute name to contain either of the
   separators.  It is legal for attribute values to contain the
   separators.  
SB> Is "legal" the correct term here?



From nobody Tue May 14 09:33:53 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 588991201D5; Tue, 14 May 2019 09:33:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Deborah Brungard via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Deborah Brungard <db3546@att.com>
Message-ID: <155785161334.30214.9742358968370478777.idtracker@ietfa.amsl.com>
Date: Tue, 14 May 2019 09:33:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/AvuH7rXhyObSMe3IevE-3zZUBUc>
Subject: [OPSAWG] Deborah Brungard's No Objection on draft-ietf-opsawg-tacacs-13: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2019 16:33:44 -0000

Deborah Brungard has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

While the status is an Informational document, not PS, I still would
prefer if earlier in the document it provided the reader with deployment
concerns e.g. the introduction.

The current introduction states a "wide range" of clients and servers
are already deployed. Not until section 10 is the reader informed
"Multiple implementations of the protocol described in the original
TACACS+ Draft `The Draft' [TheDraft] have been deployed.  As the
protocol was never standardized, current implementations may be
incompatible in non-obvious ways". And section 10.5 on Best
Practices which has the new restriction that it not be deployed
with other traffic. This information is needed much
earlier in the document to give context for the reader.



From nobody Wed May 15 05:58:58 2019
Return-Path: <session-request@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8DF1200BA; Wed, 15 May 2019 05:58:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: ibagdona@gmail.com, opsawg@ietf.org, jclarke@cisco.com, opsawg-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155792513562.17597.2698511829651955047.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 05:58:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/sL2UJTJHYaDSmyVEKN0MCn8i4Ng>
Subject: [OPSAWG] opsawg - New Meeting Session Request for IETF 105
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 12:58:56 -0000

A new meeting session request has just been submitted by Joe Clarke, a Chair of the opsawg working group.


---------------------------------------------------------
Working Group Name: Operations and Management Area Working Group
Area Name: Operations and Management Area
Session Requester: Joe Clarke

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 75
Conflicts to Avoid: 
 First Priority: nvo3 ippm rtgwg netconf netmod
 Second Priority: idr detnet



People who must be present:
  Warren &quot;Ace&quot; Kumari
  Joe Clarke
  Tianran Zhou
  Ignas Bagdonas

Resources Requested:

Special Requests:
  PLEASE NOTE: Combined OpsAWG / OpsAREA
---------------------------------------------------------


From nobody Wed May 15 11:03:05 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1A5120475; Wed, 15 May 2019 11:03:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Message-ID: <155794338418.30711.17566495330645891210.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 11:03:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/98q1RGqqdGc-J5643fD8d1ugPM4>
Subject: [OPSAWG] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draf?= =?utf-8?q?t-ietf-opsawg-tacacs-13=3A_=28with_COMMENT=29?=
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 18:03:04 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

A couple of comments/question:

1) I would like to see it more explicitly mentioned in the title, abstract, and
introduction that this is only documenting the protocol as deployed today.
Usually we use titles like “Company X’s TACACS+ protocol”; this is probably not
applicable here but maybe something like “Documentation of the TACACS+
Protocol” would work as well…?

2) If Single Connection Mode is used and the connection is idle for a while, it
can be possible that some middlebox or the server lost state and the connection
is actually not available anymore. I guess it could be good to explicit mention
this case and say something like if a RST or timeout is encountered for a
connection in Single Connection Mode, the client should try to open a new
connection and resend the request immediately.

3) I would recommend to define the term “session” in section 3 (as it seems to
a central term that is important to understand correctly).

4) Sec 10.5.1: “TACACS+ servers MUST NOT leak sensitive data.”
Not sure if that is an actionable requirement, as I would assume leaking is
often done by accident. Maybe “TACACS+ servers MUST store sensitive data
securely.”… or something…? Not sure  how much better that is… Actually the next
sentence could probably be normative: S/TACACS+ servers should not expose
shared secrets in logs./TACACS+ servers MUST NOT expose shared secrets in logs./

5) One question regarding the unencrypted/non-obfuscated mode: Why was this
mode (and TAC_PLUS_UNENCRYPTED_FLAG=1) not deprecated completely? You mention
briefly somewhere that this is/was used for debugging but then later say that
modern tools should also support debugging of obfuscated traffic.

6) Sec 10.5.5: “TACACS+ servers SHOULD deprecate the redirection mechanism.”
I believe you want to use a MUST here because you anyway only specify this for
servers that follow or update to this spec; it will of course not change
existing implementations…



From nobody Wed May 15 11:48:46 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53302120175; Wed, 15 May 2019 11:48:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <155794611732.30470.1197104619504417977.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 11:48:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Fy9WfT9vcAQhNRJJbGj-hFoxPak>
Subject: [OPSAWG] Alexey Melnikov's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 18:48:38 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I appreciate that this is documenting an existing protocol and I am very glad
that it is being documented. However there are several things which are still
not documented well enough/not in enough details to implement. So I would like
to discuss these issues before recommending approval of this document:

1) 4.6.  Text Encoding

   All text fields in TACACS+ MUST be printable US-ASCII, excepting

Please add a reference to RFC 20 (for US-ASCII) here. Without out it
"printable" has no meaning.

   special consideration given to user field and data fields used for
   passwords.

   To ensure interoperability of current deployments, the TACACS+ client
   and server MUST handle user fields and those data fields used for
   passwords as 8-bit octet strings.  The deployment operator MUST
   ensure that consistent character encoding is applied from the end
   client to the server.  The encoding SHOULD be UTF-8, and other

Please add Normative RFC 3629 reference here for UTF-8.

   encodings outside printable US-ASCII SHOULD be deprecated.

I am not sure what this mean. You didn't define allowed encoding (really you
mean charsets).

2) In 5.1:

   The printable US-ASCII name of the client port on which the
   authentication is taking place,

This doesn't mean anything. Is there a registry? It doesn't look like you are
using transport service name registry for this. Is it a fixed list?

   and its length in bytes.  The value
   of this field is client specific.  (For example, Cisco uses "tty10"
   to denote the tenth tty line and "Async10" to denote the tenth async
   interface).  The port_len indicates the length of the port field, in
   bytes.

3) Later in 5.1:

   A printable US-ASCII string indicating the remote location from which
   the user has connected to the client.  It is intended to hold a
   network address

What are the allowed formats for IPv4 and IPv6? Or is this just human readable?

   if the user is connected via a network, a caller ID
   is the user is connected via ISDN or a POTS, or any other remote
   location information that is available.

4) In 5.4:

   If the information being requested by the server form the client is
   sensitive, then the server should set the TAC_PLUS_REPLY_FLAG_NOECHO
   flag.  When the client queries the user for the information, the
   response MUST NOT be echoed as it is entered.

What does the last sentence mean? (When is it ever echoed?) Are you missing a
forward reference or some explanation of echoing?

5) KRB5 and KRB4 need normative references.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In 4.8:

4.8.  The TACACS+ Packet Header

   The total length of the packet body (not including the header).

In network byte order? There is some text about that in 4.9, but readers don't
know that yet.

In 6.1:

   The arguments are the primary elements of the authorization
   interaction.  In the request packet they describe the specifics of
   the authorization that is being requested.  Each argument is encoded
   in the packet as a single arg filed (arg_1...  arg_N) with a

Typo: filed --> field.

   corresponding length fields (which indicates the length of each
   argument in bytes).

Later in the same section:

   Optional arguments are ones that may be disregarded by either client
   or server.  Mandatory arguments require that the receiving side can
   handle the attribute, that is: its implementation and configuration
   includes the details of how to act on it.  If the client receives a
   mandatory argument that it cannot handle, it MUST consider the
   authorization to have failed.  It is legal to send an attribute-value
   pair with a zero length value.

Last sentence: do you just mean that the value can be empty?

In 8.1:

   Date Time

   Absolute date/times are specified in seconds since the epoch, 12:00am
   Jan 1 1970.  The timezone MUST be UTC unless a timezone attribute is
   specified.  Stardate is canonically inconsistent and so SHOULD NOT be
   used.

I am not sure what the last sentence means.

In 8.2:

8.2.  Authorization Attributes

   For example: "shell", "tty-server", "connection", "system" and
   "firewall".  This attribute MUST always be included.

Is this a full list or is there a registry?

Later in the same section:

   remote_host (String)

What is the syntax of this field?

10.4.  Security of Accounting Sessions

      Replace accounting data with new valid or garbage which prevents
      to provide distraction

"prevents to provide distraction" doesn't read well.

      or hide information related to their
      authentication and/or authorization attack attempts.

In 10.5.1:

   TACACS+ server administrators SHOULD change secret keys at regular
   intervals.

Humans are very bad at this. So I think it would be better if this is changed
to add a requirement on management UIs.

10.5.3.  Authentication

   To help TACACS+ administraots select the stronger authentication

Typo: administrators.



From nobody Wed May 15 11:55:48 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 967B112077E; Wed, 15 May 2019 11:55:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <155794654061.30693.7206500631491410439.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 11:55:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/ramaCqnBk1zqZR_JBXtDYl-iL7w>
Subject: [OPSAWG] Alissa Cooper's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 18:55:41 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(1) The Gen-ART reviewer Stewart Bryant (SB) asked the following:

     TAC_PLUS_PRIV_LVL_MAX := 0x0f

     TAC_PLUS_PRIV_LVL_ROOT := 0x0f

     TAC_PLUS_PRIV_LVL_USER := 0x01

     TAC_PLUS_PRIV_LVL_MIN := 0x00

SB> Where are these defined?

Please define the semantics of these values.

(2) Stewart also noted the following:

     TAC_PLUS_AUTHEN_TYPE_ASCII := 0x01

     TAC_PLUS_AUTHEN_TYPE_PAP := 0x02

     TAC_PLUS_AUTHEN_TYPE_CHAP := 0x03

     TAC_PLUS_AUTHEN_TYPE_ARAP := 0x04 (deprecated)

     TAC_PLUS_AUTHEN_TYPE_MSCHAP := 0x05

     TAC_PLUS_AUTHEN_TYPE_MSCHAPV2 := 0x06

SB> There are lots of lists similar to the above.
SB> I have not checked them all, but a number of the types
SB> in this and subsequent parts of the design don't seem
SB> to be defined or have a definitive reference

The way I would say this is that the document seems to be written for people
who have already deployed this protocol, and elides details that would make it
comprehensible to a new implementor. But it also contemplates the prospect of
new implementations. If new implementations are actually expected (which I was
surprised about, but can believe), I agree with Stewart that each of the field
values need a definition that explains its semantic. If new implementations are
not expected, then the reference to new implementations should be removed.

(3) How is "secure deployment" defined? Since this is used as a restriction in
several places, I think it needs to be defined precisely.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with Deborah's comment, and would further suggest that the lack of
modern security mechanisms in this protocol needs to be called out in the
introduction, with a reference to Section 10.

Please respond to the Gen-ART review, which makes several suggestions for
needed clarifications.

In Section 2, please use the RFC 8174 boilerplate.



From nobody Wed May 15 11:57:49 2019
Return-Path: <alissa@cooperw.in>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 912A11201BE; Wed, 15 May 2019 11:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=It6YZVkt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=DX/BWCt1
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 BVsEMG0euME4; Wed, 15 May 2019 11:57:30 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C39B1207A2; Wed, 15 May 2019 11:57:30 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 46AB2313; Wed, 15 May 2019 14:57:29 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 15 May 2019 14:57:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=a 7YBGRqbxIodqtoYrjlVklvzHv8m5CcpolIczuI9Xyk=; b=It6YZVktRKDM4hDCF FHk/0j1fRdn1jPvs0O/W+UL4ux2can8KensAPmY3l59VMLnHchH4C1Vc1vVaXNF1 4PYvnSTNZJMWZZKdBMc3UV2k78AZ67zU+TpcBNLQzAQupaBWtGbdxRqwZKXR0+4p Ljx9fmg1oqtpNf+cSk79bclmq8MBL41kT8h1yw0cJqdBe3O/3j0oyfnar2NPyM/d bqqnqUF69achtDy0MhHQpGpfMaeOBd3PzD6Mu736cj+Nt4g5qQoSqbzxs3CaCCsn OZhJebHdO9EJ1vjU2w+3nb4e8y9hTeqE0GvKLql+WvdRYRySHd2/KbXkhx2r8bdZ rFccA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=a7YBGRqbxIodqtoYrjlVklvzHv8m5CcpolIczuI9X yk=; b=DX/BWCt10UUA5e6UbAyLTIEchtrA+DbpMJz/gWiwb55tGFszWvlErewab 3l4r2CvXr8oHCmVnArRRHbS7Sqkmv8AEiQojdPNhDbiISPc9+qk/OP1Hihf+TLk8 /N3GEZPJJsTkgGr12RJItbRmsEzzGzilV2rxtrVpa4uGCgaIrVhjxClOjrug281H AhX6TYurXla+U+VIrGAczDByv9s/d8T7JSRA6FYNDwG3yGrkjgGw4HgCG+ZgHhdM gybooSlexdkGgQE3EG7Uz4HMWGa1o2bh0aTQZZMQ8sK7Vasaid921QZbTnVSdHBZ 33VN4YGnxabzSeAcd5oRCWki6yJEQ==
X-ME-Sender: <xms:GGHcXHj2vZfXnoEEIuNxdTpScLrVLkwh-hafLeGLxBc7i-5Uxm9t2w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrleekgdduvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrkeelnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:GGHcXKBghWbbNNZz_Y3YLuH0JKqgMBPKRHiyBz-VpBhOfUQIv7n3vA> <xmx:GGHcXEvaYoOtC0TH-BnjfJCZtIohtRI-ew_HrFXWW2x9Ky6YcsZ7qg> <xmx:GGHcXPacNDA_J_K2LFucCGGBfMkNalv86VkvKTlvnkQZqno5MPPJYQ> <xmx:GGHcXG_txYthOj-97i-3aF5bqFrsAvCb-bA0L9MUVsmKZUPbC3rqwA>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.89]) by mail.messagingengine.com (Postfix) with ESMTPA id 4083010378; Wed, 15 May 2019 14:57:28 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <155775206584.23645.18248080061887454144@ietfa.amsl.com>
Date: Wed, 15 May 2019 14:57:26 -0400
Cc: gen-art@ietf.org, opsawg@ietf.org, ietf@ietf.org, draft-ietf-opsawg-tacacs.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2ED46465-7FBE-49D5-BD71-0A3BCF72F8AD@cooperw.in>
References: <155775206584.23645.18248080061887454144@ietfa.amsl.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/9DphiR_O2Uux6RklAU9KtFbOwNE>
Subject: Re: [OPSAWG] [Gen-art] Genart telechat review of draft-ietf-opsawg-tacacs-13
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 18:57:34 -0000

Stewart, thanks for your review. I have entered a DISCUSS ballot based =
on a couple of your points.

Alissa

> On May 13, 2019, at 8:54 AM, Stewart Bryant via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Stewart Bryant
> Review result: Almost Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-opsawg-tacacs-13
> Reviewer: Stewart Bryant
> Review Date: 2019-05-13
> IETF LC End Date: None
> IESG Telechat date: 2019-05-16
>=20
> Summary:
>=20
> There are a number of issues called out below that need addressing =
before publication.
>=20
> Someone needs to micro-check the text to make sure that all terms are =
defined and referenced.
> I picked up a few, but there were a lot I did not have time to check.
>=20
> Major issues:
>=20
> SB> The IANA section should ask IANA to point to this RFC as a =
reference
> SB> for port 49
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
>   The first MD5 hash is generated by concatenating the session_id, the
>   secret key, the version number and the sequence number and then
>   running MD5 over that stream.  All of those input values are
>   available in the packet header, except for the secret key which is a
>   shared secret between the TACACS+ client and server.
>=20
> SB> MD5 make a good checksum, but I am surprised to see it used in =
this
> SB> application in a new protocol.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>   All TACACS+ packets begin with the following 12-byte header.  The
>   header describes the remainder of the packet:
>=20
> SB> If ever there was an error in a long term session, how
> SB> how would you find in in the following packet structure?
> SB> Presumably from an incorrect major version and sequence number?
>=20
> SB> Some details on the error cases and the unconditional "safety"
> SB> of the protocol would be useful.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>      TAC_PLUS_AUTHEN_TYPE_ASCII :=3D 0x01
>=20
>      TAC_PLUS_AUTHEN_TYPE_PAP :=3D 0x02
>=20
>      TAC_PLUS_AUTHEN_TYPE_CHAP :=3D 0x03
>=20
>      TAC_PLUS_AUTHEN_TYPE_ARAP :=3D 0x04 (deprecated)
>=20
>      TAC_PLUS_AUTHEN_TYPE_MSCHAP :=3D 0x05
>=20
>      TAC_PLUS_AUTHEN_TYPE_MSCHAPV2 :=3D 0x06
>=20
>=20
>=20
> SB> There are lots of lists similar to the above.
> SB> I have not checked them all, but a number of the types=20
> SB> in this and subsequent parts of the design don't seem
> SB> to be defined or have a definitive reference
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> The START packet MUST contain a username and the data
>   field MUST contain the PAP ASCII password.  A PAP authentication =
only
>   consists of a username and password RFC 1334 [RFC1334] . The REPLY
>   from the server MUST be either a PASS, FAIL or ERROR.
>=20
> SB> Should there note be a note that RFC1334 is obsolete?
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Minor issues:
>=20
> The use of the term "packet" as a unit of data is confusing, since the =
protocol
> is carried over TCP which is a streaming protocol.
>=20
> They are really TACAS+ PDUs
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> (For example, Cisco uses "tty10"
>   to denote the tenth tty line and "Async10" to denote the tenth async
>   interface). =20
> SB> Is it correct to quote a particular vendor in an RFC of this type?
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D
>=20
>      TAC_PLUS_PRIV_LVL_MAX :=3D 0x0f
>=20
>      TAC_PLUS_PRIV_LVL_ROOT :=3D 0x0f
>=20
>      TAC_PLUS_PRIV_LVL_USER :=3D 0x01
>=20
>      TAC_PLUS_PRIV_LVL_MIN :=3D 0x00
>=20
> SB> Where are these defined?
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D
> Nits/editorial comments:
>=20
>      The normative description of Legacy features such as ARAP and
> SB> ARAP not expanded anywhere in document.
>=20
> =3D=3D=3D=3D=3D
>=20
> SB> telnet and rlogin need references
>=20
> =3D=3D=3D=3D=3D
>   is the user is connected via ISDN or a POTS,=20
> SB> Are ISDN and POTS well known IETF terms?
>=20
> =3D=3D=3D=3D=3D
>=20
>   It is not legal for an attribute name to contain either of the
>   separators.  It is legal for attribute values to contain the
>   separators. =20
> SB> Is "legal" the correct term here?
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed May 15 12:12:52 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A099412001B; Wed, 15 May 2019 12:12:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <155794757064.30599.16805992272677304176.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 12:12:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/LQ-klalA7V-f10aI8msleCN2Vac>
Subject: [OPSAWG] Roman Danyliw's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 19:12:51 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(1) I appreciate the deliberate and thoughtful attempt in this section to
enumerate the possible risks/attacks and mitigations of the protocol as is.  In
addition to the top-level risks in Section 10.1, I can see the value of
maintaining symmetry between Sections 5+10.2; 6+10.3 and 7+10.4.  In the spirit
of the middle ground this draft is trying to realize (document the as-is, but
highlight the issues), I have the following feedback:

(a) Section 10.1.  I recommend replacing the first three paragraphs of Section
10.1 (“TACACS+ protocol does not …”, “While the protocol …”, and “Even though
…”) with the following text synthesized from Joe Salowey’s LC review
(https://mailarchive.ietf.org/arch/msg/secdir/rsqrNbVEKph1RdWh836Ard73pHs) and
the current introduction:

TACACS+ protocol does not include a security mechanism that would meet
modern-day requirements.  These security mechanisms would be best referred to
as “obfuscation” and not “encryption” since they provide no meaningful
integrity, privacy or replay protection.  An attacker with access to the data
stream should be assumed to be able to read and modify all TACACS+ packets.
Without mitigation, a range of risks such as the following are possible:

Accounting information may be modified by the man-in-the-middle attacker,
making such logs unsuitable and untrustable for auditing purposes.

Invalid or misleading values may be inserted by the man-in-the-middle attacker
in various fields at known offsets to try and circumvent the authentication or
authorization checks even inside the obfuscated body.

(b) I recommend finding an alternative home and strengthening the text “For
this reason, deployments SHOULD NOT use connections with
TAC_PLUS_UNENCRYPTED_FLAG, as mentioned in the Best Practices section (Section
10.5)”.  It seemed odd to mix deployment guidance in a list of risks as
currently written.  I take Andrej Ota’s point from
https://mailarchive.ietf.org/arch/msg/secdir/UgtsSfh1RaauNoMRi87FRqtI0YI that
there is no harm in requiring the obfuscation, such as it is.  Furthermore, why
couldn’t this be MUST NOT use?

(c) Section 10.5.3.  I concur with the SECDIR recommendation and the follow-up
discussion with Andrej Ota per
https://mailarchive.ietf.org/arch/msg/secdir/UgtsSfh1RaauNoMRi87FRqtI0YI which
would: s/stronger authentication/less weak/

(2) Section 10.2.  I’m confused by the deprecation of
TAC_PLUS_AUTHEN_STATUS_FOLLOW but a seemingly weaker “SHOULD NOT be used in
modern deployments”.  I was expecting a MUST NOT.

(3) Section 10.4.  Why shouldn’t accounting sessions also use secure transport
per 10.5 (like 10.3 and 10.4) given the risks outlined in the text?  I was
expecting to see this section open with “Accounting Session SHOULD be used via
a secure transport (see Best Practices section (Section 10.5))".


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(1) Editorial Nits:

** Section 10.5.3.  Typo.  s/administraots/administrators/
** Global.  Various places in the document have an extra space between the end
of a reference and the closing period.  Recommend: s/] ./]./g

(2) I endorse Mirja and Deborah’s point that strong text is needed in Section 1
to state that this document is describing the current deployment of the
protocol which has serious security issues.



From nobody Wed May 15 13:35:17 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B781200FE; Wed, 15 May 2019 13:35:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <155795250991.30689.1445498577568703956.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 13:35:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/2oiBcQlAH7W96wMyMV9ezgfYIDw>
Subject: [OPSAWG] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-opsawg-tacacs-13=3A_=28with_COMMENT=29?=
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 20:35:10 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the work everyone has put into this document. I have some comments
and some nits. I also support most of the other comments issued by the IESG
members.

And, I appreciate the time taken to document a protocol that I used in the mid
90's ;-) it took sometime to document it... I also appreciate the use of
'obfuscation' in section 4.7.

== COMMENTS ==
- section 1, I am unsure whether the 'today' in 'It is primarily used today...'
still stands in 2019. - a little late to ask, but, is there any reason why
draft-dahm-opsawg-tacacs does not refer to 'The Draft' in the datatracker? -
section 4.8, the flag values are 0x01 and 0x04, but what about the other bits?
Should they be considered as 0 and ignored on reception? - section 5.1, should
TAC_PLUS_AUTHEN_SVC_ARAP := 0x04 also be deprecated ? - section 5.4.2.1 about
'ASCII login' while I understand that years ago it was ASCII only hence the
name of the value but the text is unclear whether UTF-8 could be used (assuming
that the network devices support this character set) - section 8.2, the route
attribute is defined only for IPv4 while the T+ can send IPv6 addresses to the
client. Is it sensible?

== NITS ==
- abstract TACACS is an acronym which should be expanded in the abstract
- section 3 could be updated esp around "character mode front end and then
allow the user to telnet" - section 4.1 add that the port 49 has been allocated
by the IANA ? - section 4.3 talks about flags but the packet format is also
presented in section . Not a logical flow - section 8.1 s/IPV6 address text
representation defined/IPv6 address text representation is defined/ (lower case
V as well) - section 8.2, please clarify the inacl value, is it an ACL name or
an ASCII representation of the list of ACL entries?



From nobody Wed May 15 16:11:53 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7F8A12002F; Wed, 15 May 2019 16:11:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Suresh Krishnan <suresh@kaloom.com>
Message-ID: <155796191292.30544.5541464850362872029.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 16:11:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/I-NgfNCpg8eNCysdgkeJ5IdWV9I>
Subject: [OPSAWG] Suresh Krishnan's No Objection on draft-ietf-opsawg-tacacs-13: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 23:11:53 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

* Section 8.1.

"IPV6 address text representation defined in RFC 4291 [RFC4291]"

I would much prefer using RFC5952 here as it tightens rules a bit over RFC4291
and cuts down the flexibility to make text comparisons easier.

"Stardate is canonically inconsistent and so SHOULD NOT be used."

as in "Acting Captain's log, Stardate 2258.42. We have had no word from Captain
Pike..."? I agree that it is canonically inconsistent but this will be very
confusing for non-Trekkies. Is this really needed here?



From nobody Wed May 15 22:10:37 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C1512006D; Wed, 15 May 2019 22:10:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <155798342993.30658.12691604092353398933.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 22:10:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/jHMLDAzfwb6lXtl-VJdhrJ7WKhk>
Subject: [OPSAWG] Barry Leiba's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 05:10:30 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I support the DISCUSS ballots by Alexey and Roman, as well as the comments by
Deborah and Alissa that more text be in the introduction about the status and
limitations here.

I also need to add to Alexey’s DISCUSS on 4.6, Text Encoding:

   To ensure interoperability of current deployments, the TACACS+ client
   and server MUST handle user fields and those data fields used for
   passwords as 8-bit octet strings.  The deployment operator MUST
   ensure that consistent character encoding is applied from the end
  client to the server.

This is a mine field.  Treating passwords as raw octets without concern for
encoding and normalization can cause authentication failures and can be used to
attack systems where non-ASCII passwords are in use.

Suppose I enter “crème brûlée” as my password. How that’s represented in UTF-8
depends upon my input device, as there are at least two valid representations
of each accented vowel.  Without normalization/canonicalization, passwords
entered on different input devices might not match, blocking my access.  And we
haven’t touched on bidirectional issues (mixing, say, Hebrew and English
characters).

The precis framework has detailed explanations of how to deal with usernames
and passwords — see RFC 8265 (and, for the overall precis framework, RFC 8264).

   The encoding SHOULD be UTF-8, and other
   encodings outside printable US-ASCII SHOULD be deprecated.”

This doesn’t make sense with respect to how we use “deprecated”.  You need to
say “are deprecated”, meaning that we recommend against using them.  There’s no
BCP 14 “SHOULD” involved here.





From nobody Wed May 15 23:04:48 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 830B3120092; Wed, 15 May 2019 23:04:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Adam Roach <adam@nostrum.com>
Message-ID: <155798668553.30465.3681431548982215622.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 23:04:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/cB8Q-RtwDLjOL5o5mNi9eqjE5zo>
Subject: [OPSAWG] Adam Roach's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 06:04:46 -0000

Adam Roach has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks to everyone who has worked on documenting the TACACS+ protocol
as it is used today.

I understand the desire to publish this document as a status other than
Historic, as the protocol remains in use today. However, the shortcomings
cited in the "Security Considerations" section are quite profound, and
really bear highlighting in the document way before we get into what is
fundamentally end material.

I have serious misgivings about publishing this document as anything
other than Historic without some prominent text early in the document
(e.g., in the Introduction section) that warns implementors of the
several caveats detailed in section 10 and its subsections. They don't
need to be explained here, but some language along the lines of the
following really needs to be present in order to scope the document:

   Note that the original TACACS+ implementations did not address all of the
   baseline security concerns which are considered when designing modern
   protocols.  This document does not change this situation, and implementors
   should use caution when evaluating the suitability of TACACS+ for any given
   use.  Please see section 10 for additional details.

---------------------------------------------------------------------------

§4.6:

>  To ensure interoperability of current deployments, the TACACS+ client
>  and server MUST handle user fields and those data fields used for
>  passwords as 8-bit octet strings.  The deployment operator MUST
>  ensure that consistent character encoding is applied from the end
>  client to the server.  The encoding SHOULD be UTF-8, and other
>  encodings outside printable US-ASCII SHOULD be deprecated.

Without specification of preparation profiles for usernames and passwords,
this is an incomplete specification of how to transmit non-ASCII
usernames and passwords. While there are other solutions, the easy
way to address this is to normatively reference RFC 7613, and select
one of its username preparation profiles, and indicate its password
preparation profile.

The most basic problem here is that I might create a username and/or password
on a machine that uses one mapping for a non-ASCII character, and later try to
log in on a machine that uses a different, but semantically equivalent,
mapping for that same character. This is a clear interop issue.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


ID Nits reports:

  ** Obsolete normative reference: RFC 1334 (Obsoleted by RFC 1994)

---------------------------------------------------------------------------

§2:

>  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>  document are to be interpreted as described in RFC 2119 RFC2119
>  [RFC2119].

Please use the boilerplate from RFC 8174.

---------------------------------------------------------------------------

§4.3:

>  The packet header contains the TAC_PLUS_SINGLE_CONNECT_FLAG used by
>  the client and server to negotiate the use of Single Connect Mode.

This is a bit jarring, as the document hasn't yet established the existence
of a packet header, or of flag in that header. It might be better to pull
section 4.8 earlier in the document -- at least before this sentence --
so that readers have some context for understanding what's going on.

---------------------------------------------------------------------------

§4.7:

>  Server implementations MUST allow a unique secret key to be
>  associated with every client.

Nit: "...with each client."

---------------------------------------------------------------------------

§5.1:

>  network address if the user is connected via a network, a caller ID
>  is the user is connected via ISDN or a POTS

Nit: "...if the user..."

---------------------------------------------------------------------------

§5.4.2.1:

Is the intention here to limit the characters in the user name and the
password to be only those in the ASCII range? Section 4.6 would seem to
indicate that this isn't the case, but the title of this section throws
that into doubt. If the text in 4.6 is the guiding text here, perhaps
section 5.4.2.1 should indicate that the term "ASCII" is used only for
historical reasons, and that both usernames and passwords can contain
UTF-8-encoded character strings.

---------------------------------------------------------------------------

§5.4.2.2:

>  the data
>  field MUST contain the PAP ASCII password.

Same comment as for section 5.4.2.1, above.

---------------------------------------------------------------------------

§5.4.2.3:

>  defined in the PPP Authentication RFC RFC 1334 [RFC1334] and then
>  compare that value with the response.

Nit: "...and then compares..."

---------------------------------------------------------------------------

§5.4.2.7.  ASCII change password request

Same comment as for section 5.4.2.1.

---------------------------------------------------------------------------

§5.4.3:

>  If this
>  flag is set, the data portion of the message may contain an ASCII
>  message explaining the reason for the abort.

Does this mean "ASCII" or does it mean "UTF-8"? If it actually means
"ASCII," then localization -- especially to localities that use
non-latin-based alphabets -- will be incredibly challenging.

---------------------------------------------------------------------------

§6.2 and §7.2:

>  server_msg, server_msg_len
>
>  This is a printable US-ASCII string that may be presented to the
>  user.
>
>  data, data_len
>
>  This is a printable US-ASCII string that may be presented on an
>  administrative display, console or log

Same comment as for section 5.4.3.

---------------------------------------------------------------------------

§8.1:

>  All attribute values are encoded as printable US-ASCII strings.  The
>  following type representations SHOULD be followed
...
>  String
>
>  Many values have no specific type representation and so are
>  interpreted as plain strings.

Same comment as for section 5.4.3.

---------------------------------------------------------------------------

§8.3:

>  err_msg (String)
>
>  A printable US-ASCII string describing the status of the action.

Same comment as for section 5.4.3.

---------------------------------------------------------------------------

§10.5.3:

>  To help TACACS+ administraots select the stronger authentication

Nit: "...administrators..."

---------------------------------------------------------------------------



From nobody Wed May 15 23:21:14 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 16AD9120091; Wed, 15 May 2019 23:21:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <155798766808.30465.13613903853679159439.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 23:21:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/ygEEv5cLbqtnc-wFj2UyB_oB6nk>
Subject: [OPSAWG] Alexey Melnikov's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 06:21:08 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(One small addition to my earlier comments, see new DISCUSS point 6)

I appreciate that this is documenting an existing protocol and I am very glad
that it is being documented. However there are several things which are still
not documented well enough/not in enough details to implement. So I would like
to discuss these issues before recommending approval of this document:

1) 4.6.  Text Encoding

   All text fields in TACACS+ MUST be printable US-ASCII, excepting

Please add a reference to RFC 20 (for US-ASCII) here. Without out it
"printable" has no meaning.

   special consideration given to user field and data fields used for
   passwords.

   To ensure interoperability of current deployments, the TACACS+ client
   and server MUST handle user fields and those data fields used for
   passwords as 8-bit octet strings.  The deployment operator MUST
   ensure that consistent character encoding is applied from the end
   client to the server.  The encoding SHOULD be UTF-8, and other

Please add Normative RFC 3629 reference here for UTF-8.

   encodings outside printable US-ASCII SHOULD be deprecated.

I am not sure what this mean. You didn't define allowed encoding (really you
mean charsets).

2) In 5.1:

   The printable US-ASCII name of the client port on which the
   authentication is taking place,

This doesn't mean anything. Is there a registry? It doesn't look like you are
using transport service name registry for this. Is it a fixed list?

   and its length in bytes.  The value
   of this field is client specific.  (For example, Cisco uses "tty10"
   to denote the tenth tty line and "Async10" to denote the tenth async
   interface).  The port_len indicates the length of the port field, in
   bytes.

3) Later in 5.1:

   A printable US-ASCII string indicating the remote location from which
   the user has connected to the client.  It is intended to hold a
   network address

What are the allowed formats for IPv4 and IPv6? Or is this just human readable?

   if the user is connected via a network, a caller ID
   is the user is connected via ISDN or a POTS, or any other remote
   location information that is available.

4) In 5.4:

   If the information being requested by the server form the client is
   sensitive, then the server should set the TAC_PLUS_REPLY_FLAG_NOECHO
   flag.  When the client queries the user for the information, the
   response MUST NOT be echoed as it is entered.

What does the last sentence mean? (When is it ever echoed?) Are you missing a
forward reference or some explanation of echoing?

5) KRB5 and KRB4 need normative references.

6) Does this document need to obsolete RFC 1492?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In 4.8:

4.8.  The TACACS+ Packet Header

   The total length of the packet body (not including the header).

In network byte order? There is some text about that in 4.9, but readers don't
know that yet.

In 6.1:

   The arguments are the primary elements of the authorization
   interaction.  In the request packet they describe the specifics of
   the authorization that is being requested.  Each argument is encoded
   in the packet as a single arg filed (arg_1...  arg_N) with a

Typo: filed --> field.

   corresponding length fields (which indicates the length of each
   argument in bytes).

Later in the same section:

   Optional arguments are ones that may be disregarded by either client
   or server.  Mandatory arguments require that the receiving side can
   handle the attribute, that is: its implementation and configuration
   includes the details of how to act on it.  If the client receives a
   mandatory argument that it cannot handle, it MUST consider the
   authorization to have failed.  It is legal to send an attribute-value
   pair with a zero length value.

Last sentence: do you just mean that the value can be empty?

In 8.1:

   Date Time

   Absolute date/times are specified in seconds since the epoch, 12:00am
   Jan 1 1970.  The timezone MUST be UTC unless a timezone attribute is
   specified.  Stardate is canonically inconsistent and so SHOULD NOT be
   used.

I am not sure what the last sentence means.

In 8.2:

8.2.  Authorization Attributes

   For example: "shell", "tty-server", "connection", "system" and
   "firewall".  This attribute MUST always be included.

Is this a full list or is there a registry?

Later in the same section:

   remote_host (String)

What is the syntax of this field?

10.4.  Security of Accounting Sessions

      Replace accounting data with new valid or garbage which prevents
      to provide distraction

"prevents to provide distraction" doesn't read well.

      or hide information related to their
      authentication and/or authorization attack attempts.

In 10.5.1:

   TACACS+ server administrators SHOULD change secret keys at regular
   intervals.

Humans are very bad at this. So I think it would be better if this is changed
to add a requirement on management UIs.

10.5.3.  Authentication

   To help TACACS+ administraots select the stronger authentication

Typo: administrators.



From nobody Thu May 16 07:35:07 2019
Return-Path: <adam@nostrum.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F20120098; Thu, 16 May 2019 07:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level: 
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 qWAmAh2oEx7Z; Thu, 16 May 2019 07:35:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F13C1200D8; Thu, 16 May 2019 07:35:00 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x4GEYpUv063574 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 16 May 2019 09:34:52 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1558017293; bh=Ff1xszl6IZLxmUFxvye7ZB27sIMJ7ykauBH2uzppX3g=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=e4m924/Lm7U45u1Zbo18vl8eBdCUV01QLlvIKcVRRsK1/nWAPglJf7HnHB2Nku6wT WQYsR3pH/3Znk+wX00q/wBeKHQeeQXCrwGd0t9wLnkP3vZMF6pngzKl5Vv/cPaGdVs zT9S+ouMjrzAxfMJQ72yvmVnLWI3EKadbP9FSPNQ=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: The IESG <iesg@ietf.org>
Cc: jclarke@cisco.com, opsawg@ietf.org, draft-ietf-opsawg-tacacs@ietf.org, opsawg-chairs@ietf.org
References: <155798668553.30465.3681431548982215622.idtracker@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <1967dd24-5e1f-bdce-7a8f-f2db5548c7f1@nostrum.com>
Date: Thu, 16 May 2019 09:34:46 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <155798668553.30465.3681431548982215622.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/VszVZc6iaCycZVr4U4pW7N-o0SQ>
Subject: Re: [OPSAWG] Adam Roach's Discuss on draft-ietf-opsawg-tacacs-13: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 14:35:05 -0000

On 5/16/19 1:04 AM, Adam Roach via Datatracker wrote:
> Without specification of preparation profiles for usernames and passwords,
> this is an incomplete specification of how to transmit non-ASCII
> usernames and passwords. While there are other solutions, the easy
> way to address this is to normatively reference RFC 7613, and select
> one of its username preparation profiles, and indicate its password
> preparation profile. 


And I completely missed that RFC 7613 has been obsoleted by RFC 8265. 
Please consult RFC 8265 instead.

/a


From nobody Thu May 16 10:29:29 2019
Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B71B1200E9; Thu, 16 May 2019 10:29:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-tacacs@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <155802776203.19810.13364995689196377998.idtracker@ietfa.amsl.com>
Date: Thu, 16 May 2019 10:29:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/v5jM0Wi513znZOLtbn-XmWH5Wvo>
Subject: [OPSAWG] Alissa Cooper's No Objection on draft-ietf-opsawg-tacacs-13: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 17:29:22 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-opsawg-tacacs-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

My DISCUSS moved to Alexey's ballot. My original comment is below:

I agree with Deborah's comment, and would further suggest that the lack of
modern security mechanisms in this protocol needs to be called out in the
introduction, with a reference to Section 10.

Please respond to the Gen-ART review, which makes several suggestions for
needed clarifications.

In Section 2, please use the RFC 8174 boilerplate.



From nobody Mon May 27 10:16:36 2019
Return-Path: <oscar.gonzalezdedios@telefonica.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E302120020 for <opsawg@ietfa.amsl.com>; Mon, 27 May 2019 10:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.com
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 ZIQYofhEnGpj for <opsawg@ietfa.amsl.com>; Mon, 27 May 2019 10:16:31 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20111.outbound.protection.outlook.com [40.107.2.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4EB91200B7 for <OPSAWG@ietf.org>; Mon, 27 May 2019 10:16:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GJ/3vJSrJ9TVVQnl1PeJZxQkcueE8otikJXxnf+d01k=; b=KAfGkdotZVrKY3wtUasGTOoZFbS6/Cw09qGm27zbFM8np+ynbGvoSvpQcug5bQSRlBj7x/bE2r8Hjhehe5EOzdMhs8FIkTZbFMp4P7Zpmzzia3NI5SGlfyMumhVn2QIMztjry5R4Pq2urrkDAVw204mrZAfYxHN7knAX+O0++CM=
Received: from DB6PR0601MB2613.eurprd06.prod.outlook.com (10.168.81.10) by DB6PR0601MB2600.eurprd06.prod.outlook.com (10.168.81.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.21; Mon, 27 May 2019 17:16:28 +0000
Received: from DB6PR0601MB2613.eurprd06.prod.outlook.com ([fe80::c948:5d22:8a45:c78a]) by DB6PR0601MB2613.eurprd06.prod.outlook.com ([fe80::c948:5d22:8a45:c78a%3]) with mapi id 15.20.1922.021; Mon, 27 May 2019 17:16:27 +0000
From: =?iso-8859-1?Q?Oscar_Gonz=E1lez_de_Dios?= <oscar.gonzalezdedios@telefonica.com>
To: "OPSAWG@ietf.org" <OPSAWG@ietf.org>
Thread-Topic: Feedback and operators+implementers input for L3NM draft-aguado-opsawg-l3sm-l3nm-00
Thread-Index: AdUUr686Fiz6gxpBTmCuoZzr7ekSrg==
Date: Mon, 27 May 2019 17:16:27 +0000
Message-ID: <DB6PR0601MB2613943EAA214958166C9D43FD1D0@DB6PR0601MB2613.eurprd06.prod.outlook.com>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=oscar.gonzalezdedios@telefonica.com; 
x-originating-ip: [195.235.92.33]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 25543db9-0b73-48e3-67bf-08d6e2c70df1
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DB6PR0601MB2600; 
x-ms-traffictypediagnostic: DB6PR0601MB2600:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DB6PR0601MB2600B6E4A3F1738E8642CDF2FD1D0@DB6PR0601MB2600.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0050CEFE70
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(396003)(136003)(376002)(366004)(346002)(189003)(199004)(40134004)(786003)(74316002)(316002)(7736002)(236005)(53936002)(5660300002)(68736007)(6436002)(66946007)(9686003)(6506007)(6306002)(54896002)(55016002)(45776006)(73956011)(26005)(81156014)(66446008)(64756008)(66556008)(66476007)(2501003)(102836004)(76116006)(86362001)(66574012)(5640700003)(8676002)(7696005)(6116002)(14444005)(256004)(790700001)(81166006)(486006)(606006)(33656002)(66066001)(476003)(8936002)(25786009)(99286004)(19627235002)(3846002)(966005)(413944005)(14454004)(2906002)(508600001)(52536014)(2351001)(6916009)(71190400001)(71200400001)(186003)(32563001)(9010500006); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0601MB2600; H:DB6PR0601MB2613.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Ck3XKf9ZJDX/40Dv16XmtfvPRK8x4t4sDqYKL44QKk4Fog4e5wQsft7BWawlfGziHHzaEKsnf+9e2MmEAg2eirZHoV5S97UV9g3LK3tMTHBcJtczJCOkNPjmRtpFBUKECM5OvnagkJUtAXevvUxhPLBZLvRYf9pmhG0MaVfam0lcRA+Y1BAr7pkGLETlBtKBEHeYlz2qGoLjRjl51ExKFmPCQ5lSBG2SB08PF8tVWp29eFfW12YD+zk3ymXHBv4OLJdlK4YM51qfWQRNpW/Aw+QwcNoAWAfQmDdgfAAnVI/Wll10waTiegSEGHQOKzwUcnqJrsfX5VQdZgP5oy2Xf1ArMYBH8CLMjQBBd7DOVUM1BegBYLZOMFWTG73N5bLtdYo6iDSRBQAagQYR2vhzho5DtPn84/1t1cIZZgc0bVI=
Content-Type: multipart/alternative; boundary="_000_DB6PR0601MB2613943EAA214958166C9D43FD1D0DB6PR0601MB2613_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 25543db9-0b73-48e3-67bf-08d6e2c70df1
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 May 2019 17:16:27.8146 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: oscar.gonzalezdedios@telefonica.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0601MB2600
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/K-SWx5ItfMpaq9Wmy2kso8lWfJE>
Subject: [OPSAWG] Feedback and operators+implementers input for L3NM draft-aguado-opsawg-l3sm-l3nm-00
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2019 17:16:35 -0000

--_000_DB6PR0601MB2613943EAA214958166C9D43FD1D0DB6PR0601MB2613_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Opsawg colleagues,

     I would like to ask for feedback on an operator-led initiative to buil=
d a L3VPN Network Yang model (let's refer to it as L3NM). The first draft i=
s available in https://tools.ietf.org/html/draft-aguado-opsawg-l3sm-l3nm-00=
.

      Please note that the yang model itself is still a work in progress, a=
nd the first intention is to show the need of having such a model and how i=
t related to current initiatives. The starting point of the work is the L3V=
PN Yang model defined in RFC 8299.  More complex deployment scenarios invol=
ving the  coordination of different VPN instances and different technologie=
s to  provide end-to-end VPN connectivity is out of scope of this document,=
  but is discussed in https://tools.ietf.org/html/draft-evenwu-opsawg-yang-=
composed-vpn-03 .
    RFC 8309 splits the service models into "Customer Service Model" and "S=
ervice Delivery Model". The L3SM Yang model, defined in RFC 8299, is valid =
for the customer to network operator conversation, but if operators want to=
 use it for the conversations between the B/OSS (business and operation sup=
port systems) and the network orchestrator (or controller, depending on the=
 terminology used) then the model has some gaps. There are two options:


A)      "Augment" approach. This is the approach shown in version 00. The m=
odel in RFC 8299 is extended via augmentation to cover the gaps. Still, som=
e parameters defined by L3SM may not be necessary for the network version o=
f the service model (those more related to the customer, which are mandator=
y for the direct customer interface).

B)      "Prune and extend" approach. This approach will present an easier w=
ay to ignore and prune unnecessary information defined at L3SM. At the same=
 time, any extension can be presented as part of the main module, and not a=
s augments of an existing model. However, many content would be similar to =
L3SM

In the draft you can find a first set of topics covered by the model.  The =
scenarios covered include: the integration of ethernet and encapsulation pa=
rameters, the extension for transport resources (e.g. RTs and RDs) to be or=
chestrated from the management system, far-end  configuration of PEs not ma=
naged by the management system and the definition for PE identification. No=
te the end customer does not really care about the internal network resourc=
es, neither does care exactly which PE is used. Those decisions are taken b=
y the operator, that then with the help of the control systems will deploy =
the service.

    We would like to ask input from operators/service providers who might u=
se this model and from software implementers who might code the model.

    Best Regards,

                Oscar

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=F3n privilegiada o confidencial y es para uso exclus=
ivo de la persona o entidad de destino. Si no es usted. el destinatario ind=
icado, queda notificado de que la lectura, utilizaci=F3n, divulgaci=F3n y/o=
 copia sin autorizaci=F3n puede estar prohibida en virtud de la legislaci=
=F3n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo =
comunique inmediatamente por esta misma v=EDa y proceda a su destrucci=F3n.

The information contained in this transmission is privileged and confidenti=
al information intended only for the use of the individual or entity named =
above. If the reader of this message is not the intended recipient, you are=
 hereby notified that any dissemination, distribution or copying of this co=
mmunication is strictly prohibited. If you have received this transmission =
in error, do not read it. Please immediately reply to the sender that you h=
ave received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio=
, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex=
clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des=
tinat=E1rio indicado, fica notificado de que a leitura, utiliza=E7=E3o, div=
ulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o pode estar proibida em virtude=
 da legisla=E7=E3o vigente. Se recebeu esta mensagem por erro, rogamos-lhe =
que nos o comunique imediatamente por esta mesma via e proceda a sua destru=
i=E7=E3o

--_000_DB6PR0601MB2613943EAA214958166C9D43FD1D0DB6PR0601MB2613_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:191454967;
	mso-list-type:hybrid;
	mso-list-template-ids:-1173565620 -381778074 201981977 201981979 201981967=
 201981977 201981979 201981967 201981977 201981979;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:53.25pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:89.25pt;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:125.25pt;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:161.25pt;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:197.25pt;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:233.25pt;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:269.25pt;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:305.25pt;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:341.25pt;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:698051008;
	mso-list-type:hybrid;
	mso-list-template-ids:-976739708 1367111832 201981977 201981979 201981967 =
201981977 201981979 201981967 201981977 201981979;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ES" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Dear Opsawg colleagues,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp; I woul=
d like to ask for feedback on an operator-led initiative to build a L3VPN N=
etwork Yang model (let&#8217;s refer to it as L3NM). The first draft is ava=
ilable in
<a href=3D"https://tools.ietf.org/html/draft-aguado-opsawg-l3sm-l3nm-00">ht=
tps://tools.ietf.org/html/draft-aguado-opsawg-l3sm-l3nm-00</a>.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Please note that the yang model itself is still a work in progress, and the=
 first intention is to show the need of having such a model and how it rela=
ted to current initiatives. The starting point of the work is
 the L3VPN Yang model defined in RFC 8299. &nbsp;More complex deployment sc=
enarios involving the&nbsp; coordination of different VPN instances and dif=
ferent technologies to&nbsp; provide end-to-end VPN connectivity is out of =
scope of this document,&nbsp; but is discussed in
<a href=3D"https://tools.ietf.org/html/draft-evenwu-opsawg-yang-composed-vp=
n-03">https://tools.ietf.org/html/draft-evenwu-opsawg-yang-composed-vpn-03<=
/a> .<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;RFC 830=
9 splits the service models into &#8220;Customer Service Model&#8221; and &=
#8220;Service Delivery Model&#8221;. The L3SM Yang model, defined in RFC 82=
99, is valid for the customer to network operator conversation, but if oper=
ators
 want to use it for the conversations between the B/OSS (business and opera=
tion support systems) and the network orchestrator (or controller, dependin=
g on the terminology used) then the model has some gaps. There are two opti=
ons:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">A)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">&#8220;Augment&#8221; a=
pproach. This is the approach shown in version 00. The model in RFC 8299 is=
 extended via augmentation to cover the gaps. Still, some parameters define=
d by L3SM may not be necessary for the network
 version of the service model (those more related to the customer, which ar=
e mandatory for the direct customer interface).
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">B)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">&#8220;Prune and extend=
&#8221; approach. This approach will present an easier way to ignore and pr=
une unnecessary information defined at L3SM. At the same time, any extensio=
n can be presented as part of the main module,
 and not as augments of an existing model. However, many content would be s=
imilar to L3SM<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:18.0pt"><span lang=3D"EN-US">In=
 the draft you can find a first set of topics covered by the model. &nbsp;T=
he scenarios covered include: the integration of ethernet and encapsulation=
 parameters, the extension for transport resources
 (e.g. RTs and RDs) to be orchestrated from the management system, far-end&=
nbsp; configuration of PEs not managed by the management system and the def=
inition for PE identification. Note the end customer does not really care a=
bout the internal network resources,
 neither does care exactly which PE is used. Those decisions are taken by t=
he operator, that then with the help of the control systems will deploy the=
 service.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp; &nbsp;&nbsp;We would lik=
e to ask input from operators/service providers who might use this model an=
d from software implementers who might code the model.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp; Best Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Oscar &nbsp;&nb=
sp; <o:p></o:p></span></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=F3n privilegiada o confidencial y es para uso exclus=
ivo de la persona o entidad de destino. Si no es usted. el destinatario ind=
icado, queda notificado de que la
 lectura, utilizaci=F3n, divulgaci=F3n y/o copia sin autorizaci=F3n puede e=
star prohibida en virtud de la legislaci=F3n vigente. Si ha recibido este m=
ensaje por error, le rogamos que nos lo comunique inmediatamente por esta m=
isma v=EDa y proceda a su destrucci=F3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al information intended only for the use of the individual or entity named =
above. If the reader of this message is not the intended recipient, you are=
 hereby notified that any dissemination,
 distribution or copying of this communication is strictly prohibited. If y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=E1rio=
, pode conter informa=E7=E3o privilegiada ou confidencial e =E9 para uso ex=
clusivo da pessoa ou entidade de destino. Se n=E3o =E9 vossa senhoria o des=
tinat=E1rio indicado, fica notificado de que a
 leitura, utiliza=E7=E3o, divulga=E7=E3o e/ou c=F3pia sem autoriza=E7=E3o p=
ode estar proibida em virtude da legisla=E7=E3o vigente. Se recebeu esta me=
nsagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mes=
ma via e proceda a sua destrui=E7=E3o<br>
</font>
</body>
</html>

--_000_DB6PR0601MB2613943EAA214958166C9D43FD1D0DB6PR0601MB2613_--

