Re: Mirja Kühlewind's No Objection on draft-ietf-rtgwg-ni-model-08: (with COMMENT)
"Acee Lindem (acee)" <acee@cisco.com> Mon, 05 February 2018 23:12 UTC
Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB55D124E15; Mon, 5 Feb 2018 15:12:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 N0LNWanJcTB6; Mon, 5 Feb 2018 15:12:27 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3634912025C; Mon, 5 Feb 2018 15:12:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2350; q=dns/txt; s=iport; t=1517872347; x=1519081947; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=IooXEPhw2em4i6bXsOh00eNh/yn7LG51bhOnpLVyl6I=; b=hRbN0tENXZiR4hCH/xfhHguEwK1goOKPJXPp3FopDxpxoMc/HXH7XTuJ 1NodFumEwl/f5Lz5//ygMuyd+1pRPFR02PDLPI6kL8LcDs2EUNAR5BjTF QRRtOPl6QBTjCKrraz7ITqaUYd1XOn0oNtSlfmSloqZSr8TmeHb8hibA/ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmAADD43ha/5RdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYNRZnAoCoNbiiSOMJlKFYIDCiOFGAIagjNUGAEBAQEBAQEBAmsohSQGIxFFEAIBCBoCJgICAjAVBQsCBAENBYo1ELxSgieIeoF4AQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBD4NbghWDaIMFgy8CAQEBAYE6ARIBBxiDFzGCNAWKZpk/AogXgSWMM4IehiaLc4JbixKJXAIRGQGBOwEfOWBXEQhwFWcBghuDCoFteAGMLoElgRcBAQE
X-IronPort-AV: E=Sophos;i="5.46,466,1511827200"; d="scan'208";a="352357104"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Feb 2018 23:12:26 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w15NCPkL009884 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 5 Feb 2018 23:12:26 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 5 Feb 2018 18:12:25 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Mon, 5 Feb 2018 18:12:24 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-rtgwg-ni-model@ietf.org" <draft-ietf-rtgwg-ni-model@ietf.org>, Yingzhen Qu <yingzhen.ietf@gmail.com>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Mirja Kühlewind's No Objection on draft-ietf-rtgwg-ni-model-08: (with COMMENT)
Thread-Topic: Mirja Kühlewind's No Objection on draft-ietf-rtgwg-ni-model-08: (with COMMENT)
Thread-Index: AQHTntbINET/yV8IO0CIv+488gCb1A==
Date: Mon, 05 Feb 2018 23:12:24 +0000
Message-ID: <A2308EF1-563F-4E80-A46D-2D5374E7EA4E@cisco.com>
References: <151782756152.5649.4225576974862497097.idtracker@ietfa.amsl.com>
In-Reply-To: <151782756152.5649.4225576974862497097.idtracker@ietfa.amsl.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.116.152.195]
Content-Type: text/plain; charset="utf-8"
Content-ID: <546CAB33F7DE4048AD87B22CA24B0ED4@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Lk_abIgflyZU2GB3BsHQ_Wxp5Hk>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2018 23:12:29 -0000
Hi Mirja, On 2/5/18, 5:46 AM, "Mirja Kühlewind" <ietf@kuehlewind.net> wrote: Mirja Kühlewind has entered the following ballot position for draft-ietf-rtgwg-ni-model-08: 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-rtgwg-ni-model/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Two minor editorial comments: 1) Sec 1.2: I'm surprised to see an open issue listed here. Is there already any plan to address this somehow or is that listed to inform the reader, however, in the second case I would probably rather call it 'limitation' or something like this... I've removed it. 2) Sec 2: "In this document, we consider network devices that support protocols and functions defined within the IETF Routing Area, e.g, routers, firewalls, and hosts. " I assume that this yang module can also be used for routing protocols and functions that have not been defined in the IETF? Yes - but we are only "considering" protocols and functions defined in the IETF. I'll remove "Routing Area". Thanks, Acee
- Mirja Kühlewind's No Objection on draft-ietf-rtgw… Mirja Kühlewind
- Re: Mirja Kühlewind's No Objection on draft-ietf-… Acee Lindem (acee)