Document Action: 'LPWAN Overview' to Informational RFC (draft-ietf-lpwan-overview-10.txt)
The IESG has approved the following document: - 'LPWAN Overview' (draft-ietf-lpwan-overview-10.txt) as Informational RFC This document is the product of the IPv6 over Low Power Wide-Area Networks Working Group. The IESG contact persons are Suresh Krishnan and Terry Manderson. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-lpwan-overview/ Technical Summary This document is an overview of the set of Low-Power Wide-Area Network technologies being considered in the IETF and of the gaps that exist between the needs of those technologies and the goal of running IP in LPWANs. The four baseline LPWAN technologies are described at a level, which allows to identify the necessary adaptations for each of them. The document provides overviews of the characteristics of the PHY and MAC layers of the various technologies, the deployment topologies, addressing and security features. It is not a critical review of the technologies and its goal is not to provide a comparison between them. Instead, it's purpose is to enable the understanding of the features of the "IP over LPWAN" design space. The document also provides a guide on the terminologies used across the various baseline technologies. Working Group Summary The document is the combined effort of representatives of the four baseline LPWAN technologies, each authoring the part corresponding to their technology. Significant parts of the gap analysis have been contributed by other WG participants. With 12 contributing authors, the document is the fruit of a constructive work of many different organizations and individuals. Document Quality The document provides an informational overview of technologies, which were defined outside the IETF. Each of the baseline technology providers (alliances, standardization bodies, companies) have designated corresponding authors for the relative sections. The gap analysis and the other common sections were widely reviewed and discussed by the many authors of the document (12) and the WG as whole. The document is of excellent quality. The LPWAN technologies evolve rapidly, and the document provides a view that is frozen at the time of the writing. Personnel The document shepherd is Alexander Pelov. The responsible Area Director is Suresh Krishnan.
Last Call: (Extensions to RSVP-TE for LSP Egress Local Protection) to Proposed Standard
The IESG has received a request from the Traffic Engineering Architecture and Signaling WG (teas) to consider the following document: - 'Extensions to RSVP-TE for LSP Egress Local Protection' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2018-02-27. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for locally protecting the egress node(s) of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic Engineered (TE) Label Switched Path (LSP). The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-teas-rsvp-egress-protection/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-teas-rsvp-egress-protection/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2537/ https://datatracker.ietf.org/ipr/2310/ https://datatracker.ietf.org/ipr/2079/
Last Call: (Signal-Free LISP Multicast) to Experimental RFC
The IESG has received a request from the Locator/ID Separation Protocol WG (lisp) to consider the following document: - 'Signal-Free LISP Multicast' as Experimental RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2018-02-27. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract When multicast sources and receivers are active at LISP sites, the core network is required to use native multicast so packets can be delivered from sources to group members. When multicast is not available to connect the multicast sites together, a signal-free mechanism can be used to allow traffic to flow between sites. The mechanism within here uses unicast replication and encapsulation over the core network for the data-plane and uses the LISP mapping database system so encapsulators at the source LISP multicast site can find decapsulators at the receiver LISP multicast sites. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-lisp-signal-free-multicast/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-lisp-signal-free-multicast/ballot/ No IPR declarations have been submitted directly on this I-D.
Protocol Action: 'YANG Model for Network Instances' to Proposed Standard (draft-ietf-rtgwg-ni-model-10.txt)
The IESG has approved the following document: - 'YANG Model for Network Instances' (draft-ietf-rtgwg-ni-model-10.txt) as Proposed Standard This document is the product of the Routing Area Working Group. The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/ Technical Summary This document describes a YANG data model for Network Instances (NIs). The network instance container is used to represent virtual routing and forwarding instances (VRFs) and virtual switching instances (VSIs). VRFs and VSIs are commonly used to isolate routing and switching domains, for example to create virtual private networks, each with their own active protocols and routing/switching policies. The YANG data module defined in this draft can be used to configure and manage VRFs and VSIs. Working Group Summary This draft has been thoroughly discussed in the WG. The draft adoption and progress has received full support from the WG. All comments have been addressed. The draft is ready for publication. There is discussion in NetMod about the normative reference, schema mount, but even if the changes currently in discussion (not written down) were to happen, the only impact would be (allegedly) on the appendix. The normal process of holding an RFC publication until its references are done should suffice. Document Quality The draft went through initial reviews by YANG-Doctors and the quality is good. A subset of the proposed model has been implemented. The draft (version-02) has been reviewed by Routing Directorate QA and YANG Doctors. Personnel Yingzhen Qu is the Document Shepherd. Alia Atlas is the Responsible Area Director.
RFC 8325 on Mapping Diffserv to IEEE 802.11
A new Request for Comments is now available in online RFC libraries. RFC 8325 Title: Mapping Diffserv to IEEE 802.11 Author: T. Szigeti, J. Henry, F. Baker Status: Standards Track Stream: IETF Date: February 2018 Mailbox:szig...@cisco.com, jerhe...@cisco.com, fredbaker.i...@gmail.com Pages: 37 Characters: 91530 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-tsvwg-ieee-802-11-11.txt URL:https://www.rfc-editor.org/info/rfc8325 DOI:10.17487/RFC8325 As Internet traffic is increasingly sourced from and destined to wireless endpoints, it is crucial that Quality of Service (QoS) be aligned between wired and wireless networks; however, this is not always the case by default. This document specifies a set of mappings from Differentiated Services Code Point (DSCP) to IEEE 802.11 User Priority (UP) to reconcile the marking recommendations offered by the IETF and the IEEE so as to maintain consistent QoS treatment between wired and IEEE 802.11 wireless networks. This document is a product of the Transport Area Working Group 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-edi...@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
RFC 8316 on Autonomic Networking Use Case for Distributed Detection of Service Level Agreement (SLA) Violations
A new Request for Comments is now available in online RFC libraries. RFC 8316 Title: Autonomic Networking Use Case for Distributed Detection of Service Level Agreement (SLA) Violations Author: J. Nobre, L. Granville, A. Clemm, A. Gonzalez Prieto Status: Informational Stream: IRTF Date: February 2018 Mailbox:jcno...@unisinos.br, granvi...@inf.ufrgs.br, lud...@clemm.org, agonzalez...@vmware.com Pages: 16 Characters: 40002 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-nmrg-autonomic-sla-violation-detection-13.txt URL:https://www.rfc-editor.org/info/rfc8316 DOI:10.17487/RFC8316 This document describes an experimental use case that employs autonomic networking for the monitoring of Service Level Agreements (SLAs). The use case is for detecting violations of SLAs in a distributed fashion. It strives to optimize and dynamically adapt the autonomic deployment of active measurement probes in a way that maximizes the likelihood of detecting service-level violations with a given resource budget to perform active measurements. This optimization and adaptation should be done without any outside guidance or intervention. This document is a product of the IRTF Network Management Research Group (NMRG). It is published for informational purposes. This document is a product of the Network Management Research Group of the IRTF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist https://www.irtf.org/mailman/listinfo/irtf-announce 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-edi...@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
RFC 8315 on Cancel-Locks in Netnews Articles
A new Request for Comments is now available in online RFC libraries. RFC 8315 Title: Cancel-Locks in Netnews Articles Author: M. Baeuerle Status: Standards Track Stream: IETF Date: February 2018 Mailbox:michael.baeue...@stz-e.de Pages: 20 Characters: 42347 Updates:RFC 5537 I-D Tag:draft-baeuerle-netnews-cancel-lock-09.txt URL:https://www.rfc-editor.org/info/rfc8315 DOI:10.17487/RFC8315 This document defines an extension to the Netnews Article Format that may be used to authenticate the withdrawal of existing articles. This document updates RFC 5537. 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-edi...@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
