RFC 7829 on SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol
A new Request for Comments is now available in online RFC libraries. RFC 7829 Title: SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol Author: Y. Nishida, P. Natarajan, A. Caro, P. Amer, K. Nielsen Status: Standards Track Stream: IETF Date: April 2016 Mailbox:nish...@wide.ad.jp, prena...@cisco.com, ac...@bbn.com, a...@udel.edu, karen.niel...@tieto.com Pages: 23 Characters: 53922 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-tsvwg-sctp-failover-16.txt URL:https://www.rfc-editor.org/info/rfc7829 DOI:http://dx.doi.org/10.17487/RFC7829 The Stream Control Transmission Protocol (SCTP) supports multihoming. However, when the failover operation specified in RFC 4960 is followed, there can be significant delay and performance degradation in the data transfer path failover. This document specifies a quick failover algorithm and introduces the SCTP Potentially Failed (SCTP-PF) destination state in SCTP Path Management. This document also specifies a dormant state operation of SCTP that is required to be followed by an SCTP-PF implementation, but it may equally well be applied by a standard SCTP implementation, as described in RFC 4960. Additionally, this document introduces an alternative switchback operation mode called "Primary Path Switchover" that will be beneficial in certain situations. This mode of operation applies to both a standard SCTP implementation and an SCTP-PF implementation. The procedures defined in the document require only minimal modifications to the specification in RFC 4960. The procedures are sender-side only and do not impact the SCTP receiver. 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 7779 on Directional Airtime Metric Based on Packet Sequence Numbers for Optimized Link State Routing Version 2 (OLSRv2)
A new Request for Comments is now available in online RFC libraries. RFC 7779 Title: Directional Airtime Metric Based on Packet Sequence Numbers for Optimized Link State Routing Version 2 (OLSRv2) Author: H. Rogge, E. Baccelli Status: Experimental Stream: IETF Date: April 2016 Mailbox:henning.ro...@fkie.fraunhofer.de, emmanuel.bacce...@inria.fr Pages: 21 Characters: 43953 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-manet-olsrv2-dat-metric-12.txt URL:https://www.rfc-editor.org/info/rfc7779 DOI:http://dx.doi.org/10.17487/RFC7779 This document specifies a Directional Airtime (DAT) link metric for usage in Optimized Link State Routing version 2 (OLSRv2). This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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
IDR WG Virtual Interim Meetings: 16 May 2016 and 27 June 2016
The Inter-Domain Routing (idr) Working Group will hold virtual interim meetings as follows: Date: 16 May 2016 Time: 10-11pm ET (17 May 2016 02:00-03:00 UTC) Topics: Flow Specification + Yang model +TBD Date: 27 June 2016 IDR Time: 10-11am ET (14:00-15:00 UTC) Topics: Flow Specification + Yang model + TBD These IDR interims will be discuss-based as augmentation to the IDR list discussions. All presentations will be due a week before, and authors may create a video from their presentation to present. WebEx information will be distributed on the IDR mailing list (i...@ietf.org).
Last Call: (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
The IESG has received a request from an individual submitter to consider the following document: - 'Guidelines for Writing an IANA Considerations Section in RFCs' as Best Current Practice 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 2016-05-17. 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 Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values used in these fields do not have conflicting uses, and to promote interoperability, their allocation is often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, IANA needs guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the guidance given to IANA is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. The file can be obtained via https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/ballot/ No IPR declarations have been submitted directly on this I-D.
