From nobody Tue Apr 16 18:38:46 2019 Return-Path: X-Original-To: lime@ietfa.amsl.com Delivered-To: lime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C74120198; Tue, 16 Apr 2019 18:38:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 PO-JQxD6TgRH; Tue, 16 Apr 2019 18:38:42 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64161200DB; Tue, 16 Apr 2019 18:38:42 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id EE4C6B8020F; Tue, 16 Apr 2019 18:38:39 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lime@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20190417013839.EE4C6B8020F@rfc-editor.org> Date: Tue, 16 Apr 2019 18:38:39 -0700 (PDT) Archived-At: Subject: [Lime] =?utf-8?q?RFC_8531_on_Generic_YANG_Data_Model_for_Connect?= =?utf-8?q?ion-Oriented_Operations=2C_Administration=2C_and_Maintenance_?= =?utf-8?q?=28OAM=29_Protocols?= X-BeenThere: lime@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2019 01:38:45 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8531 Title: Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols Author: D. Kumar, Q. Wu, Z. Wang Status: Standards Track Stream: IETF Date: April 2019 Mailbox: dekumar@cisco.com, bill.wu@huawei.com, wangzitao@huawei.com Pages: 54 Characters: 98223 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lime-yang-connection-oriented-oam-model-07.txt URL: https://www.rfc-editor.org/info/rfc8531 DOI: 10.17487/RFC8531 This document presents a base YANG data model for connection-oriented Operations, Administration, and Maintenance (OAM) protocols. It provides a technology-independent abstraction of key OAM constructs for such protocols. The model presented here can be extended to include technology-specific details. This guarantees uniformity in the management of OAM protocols and provides support for nested OAM workflows (i.e., performing OAM functions at different levels through a unified interface). The YANG data model in this document conforms to the Network Management Datastore Architecture. This document is a product of the Layer Independent OAM Management in the Multi-Layer Environment Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Tue Apr 16 18:39:13 2019 Return-Path: X-Original-To: lime@ietfa.amsl.com Delivered-To: lime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7181202DA; Tue, 16 Apr 2019 18:38:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 AqZ2rvRvfPpg; Tue, 16 Apr 2019 18:38:55 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D01212029C; Tue, 16 Apr 2019 18:38:55 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 6453CB80316; Tue, 16 Apr 2019 18:38:52 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lime@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20190417013852.6453CB80316@rfc-editor.org> Date: Tue, 16 Apr 2019 18:38:52 -0700 (PDT) Archived-At: Subject: [Lime] =?utf-8?q?RFC_8532_on_Generic_YANG_Data_Model_for_the_Man?= =?utf-8?q?agement_of_Operations=2C_Administration=2C_and_Maintenance_=28O?= =?utf-8?q?AM=29_Protocols_That_Use_Connectionless_Communications?= X-BeenThere: lime@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2019 01:39:05 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8532 Title: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications Author: D. Kumar, Z. Wang, Q. Wu, Ed., R. Rahman, S. Raghavan Status: Standards Track Stream: IETF Date: April 2019 Mailbox: dekumar@cisco.com, wangzitao@huawei.com, bill.wu@huawei.com, rrahman@cisco.com, srihari@cisco.com Pages: 59 Characters: 107655 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lime-yang-connectionless-oam-18.txt URL: https://www.rfc-editor.org/info/rfc8532 DOI: 10.17487/RFC8532 This document presents a base YANG Data model for the management of Operations, Administration, and Maintenance (OAM) protocols that use connectionless communications. The data model is defined using the YANG data modeling language, as specified in RFC 7950. It provides a technology-independent abstraction of key OAM constructs for OAM protocols that use connectionless communication. The base model presented here can be extended to include technology-specific details. There are two key benefits of this approach: First, it leads to uniformity between OAM protocols. Second, it supports both nested OAM workflows (i.e., performing OAM functions at the same level or different levels through a unified interface) as well as interactive OAM workflows (i.e., performing OAM functions at the same level through a unified interface). This document is a product of the Layer Independent OAM Management in the Multi-Layer Environment Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Tue Apr 16 18:39:22 2019 Return-Path: X-Original-To: lime@ietfa.amsl.com Delivered-To: lime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E441202B6; Tue, 16 Apr 2019 18:39:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 ueKhYLCAI6pU; Tue, 16 Apr 2019 18:39:09 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EDBB1202FF; Tue, 16 Apr 2019 18:39:09 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 2E06CB804D2; Tue, 16 Apr 2019 18:39:06 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lime@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20190417013906.2E06CB804D2@rfc-editor.org> Date: Tue, 16 Apr 2019 18:39:06 -0700 (PDT) Archived-At: Subject: [Lime] =?utf-8?q?RFC_8533_on_A_YANG_Data_Model_for_Retrieval_Met?= =?utf-8?q?hods_for_the_Management_of_Operations=2C_Administration=2C_and_?= =?utf-8?q?Maintenance_=28OAM=29_Protocols_That_Use_Connectionless_Communi?= =?utf-8?q?cations?= X-BeenThere: lime@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2019 01:39:17 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8533 Title: A YANG Data Model for Retrieval Methods for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications Author: D. Kumar, M. Wang, Q. Wu, Ed., R. Rahman, S. Raghavan Status: Standards Track Stream: IETF Date: April 2019 Mailbox: dekumar@cisco.com, wangzitao@huawei.com, bill.wu@huawei.com, rrahman@cisco.com, srihari@cisco.com Pages: 41 Characters: 75234 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lime-yang-connectionless-oam-methods-13.txt URL: https://www.rfc-editor.org/info/rfc8533 DOI: 10.17487/RFC8533 This document presents a retrieval method YANG data model for connectionless Operations, Administration, and Maintenance (OAM) protocols. It provides technology-independent RPC operations for OAM protocols that use connectionless communication. The retrieval methods model herein presented can be extended to include technology- specific details. There are two key benefits of this approach: First, it leads to uniformity between OAM protocols. Second, it supports both nested OAM workflows (i.e., performing OAM functions at different or the same levels through a unified interface) as well as interactive OAM workflows (i.e., performing OAM functions at the same levels through a unified interface). This document is a product of the Layer Independent OAM Management in the Multi-Layer Environment Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC