RFC 8395 on Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
A new Request for Comments is now available in online RFC libraries. RFC 8395 Title: Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels Author: K. Patel, S. Boutros, J. Liste, B. Wen, J. Rabadan Status: Standards Track Stream: IETF Date: June 2018 Mailbox:ke...@arrcus.com, sbout...@vmware.com, jli...@cisco.com, bin_...@cable.comcast.com, jorge.raba...@nokia.com Pages: 10 Characters: 17404 Updates:RFC 4761 I-D Tag:draft-ietf-bess-fat-pw-bgp-04.txt URL:https://www.rfc-editor.org/info/rfc8395 DOI:10.17487/RFC8395 This document defines protocol extensions required to synchronize flow label states among Provider Edges (PEs) when using the BGP-based signaling procedures. These protocol extensions are equally applicable to point-to-point Layer 2 Virtual Private Networks (L2VPNs). This document updates RFC 4761 by defining new flags in the Control Flags field of the Layer2 Info Extended Community. This document is a product of the BGP Enabled Services 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 8351 on The PKCS #8 EncryptedPrivateKeyInfo Media Type
A new Request for Comments is now available in online RFC libraries. RFC 8351 Title: The PKCS #8 EncryptedPrivateKeyInfo Media Type Author: S. Leonard Status: Informational Stream: Independent Date: June 2018 Mailbox:dev+i...@seantek.com Pages: 7 Characters: 14797 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-seantek-pkcs8-encrypted-03.txt URL:https://www.rfc-editor.org/info/rfc8351 DOI:10.17487/RFC8351 This document registers the application/pkcs8-encrypted media type for the EncryptedPrivateKeyInfo type of PKCS #8. An instance of this media type carries a single encrypted private key, BER-encoded as a single EncryptedPrivateKeyInfo value. 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 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
Document Action: 'Information Model for Abstraction and Control of TE Networks (ACTN)' to Informational RFC (draft-ietf-teas-actn-info-model-10.txt)
The IESG has approved the following document: - 'Information Model for Abstraction and Control of TE Networks (ACTN)' (draft-ietf-teas-actn-info-model-10.txt) as Informational RFC This document is the product of the Traffic Engineering Architecture and Signaling Working Group. The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-teas-actn-info-model/ Technical Summary This draft provides an information model for Abstraction and Control of Traffic Engineered Networks (ACTN). Working Group Summary This is part of the initial set of ACTN documents worked on by the WG. There was some debate prior to WG adoption on whether this needs to be a temporary document (just remain active till the corresponding data models are put together) or not. There was consensus to take it through to the publication process. Document Quality This document has been discussed and reviewed thoroughly by the WG. While there have been no official statements on the adoption and implementation of this information model, the authors are from multiple vendors, and implementation is expected. Personnel Who is the Document Shepherd for this document? Vishnu Pavan Beeram Who is the Responsible Area Director? Deborah Brungard
RFC 8406 on Taxonomy of Coding Techniques for Efficient Network Communications
A new Request for Comments is now available in online RFC libraries. RFC 8406 Title: Taxonomy of Coding Techniques for Efficient Network Communications Author: B. Adamson, C. Adjih, J. Bilbao, V. Firoiu, F. Fitzek, S. Ghanem, E. Lochin, A. Masucci, M-J. Montpetit, M. Pedersen, G. Peralta, V. Roca, Ed., P. Saxena, S. Sivakumar Status: Informational Stream: IRTF Date: June 2018 Mailbox:brian.adam...@nrl.navy.mil, cedric.ad...@inria.fr, jbil...@ikerlan.es, victor.fir...@baesystems.com, frank.fit...@tu-dresden.de, samah.gha...@gmail.com, emmanuel.loc...@isae-supaero.fr, antoniamaria.masu...@orange.com, ma...@mjmontpetit.com, m...@es.aau.dk, gpera...@ikerlan.es, vincent.r...@inria.fr, paresh.sax...@ansur.es, ssent...@cisco.com Pages: 15 Characters: 32724 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-nwcrg-network-coding-taxonomy-08.txt URL:https://www.rfc-editor.org/info/rfc8406 DOI:10.17487/RFC8406 This document summarizes recommended terminology for Network Coding concepts and constructs. It provides a comprehensive set of terms in order to avoid ambiguities in future IRTF and IETF documents on Network Coding. This document is the product of the Coding for Efficient Network Communications Research Group (NWCRG), and it is in line with the terminology used by the RFCs produced by the Reliable Multicast Transport (RMT) and FEC Framework (FECFRAME) IETF working groups. This document is a product of the NetWork Coding for Efficient Network Communications 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
Last Call: (Marking SIP Messages to be Logged) to Proposed Standard
The IESG has received a request from the INtermediary-safe SIP session ID WG (insipid) to consider the following document: - 'Marking SIP Messages to be Logged' 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-07-10. 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 SIP networks use signaling monitoring tools to diagnose user reported problems and for regression testing if network or user agent software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signaling will take between user agents, and therefore impractical to monitor SIP signaling end-to-end. This document describes an indicator for the SIP protocol which can be used to mark signaling as being of interest to logging. Such marking will typically be applied as part of network testing controlled by the network operator and not used in normal user agent signaling. Operators of all networks on the signaling path can agree to carry such marking end-to-end, including the originating and terminating SIP user agents, even if a session originates and terminates in different networks. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-marking/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-marking/ballot/ No IPR declarations have been submitted directly on this I-D.
Last Call: (Ambisonics in an Ogg Opus Container) to Proposed Standard
The IESG has received a request from the Internet Wideband Audio Codec WG (codec) to consider the following document: - 'Ambisonics in an Ogg Opus Container' 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-07-10. 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 defines an extension to the Opus audio codec to encapsulate coded ambisonics using the Ogg format. It also contains updates to RFC 7845 to reflect necessary changes in the description of channel mapping families. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-codec-ambisonics/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-codec-ambisonics/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/3200/
Document Action: 'Hierarchical Service Function Chaining (hSFC)' to Informational RFC (draft-ietf-sfc-hierarchical-11.txt)
The IESG has approved the following document: - 'Hierarchical Service Function Chaining (hSFC)' (draft-ietf-sfc-hierarchical-11.txt) as Informational RFC This document is the product of the Service Function Chaining Working Group. The IESG contact persons are Alvaro Retana, Deborah Brungard and Martin Vigoureux. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-sfc-hierarchical/ Technical Summary Instead of considering a single SFC control plane that can manage complete service paths from one end of the network to the other, the document adopts an approach that decomposes large networks into smaller domains operated by as many SFC sub-domains (under the same administrative entity). This approach is called: Hierarchical Service Function Chaining (hSFC) The goals of hSFC are to make a large-scale network easier to reason about, simpler to control and to support independent functional groups within large network operators. Working Group Summary Two WGLCs were made for this document. The second one was mainly to confirm that the comments raised during the first call are well addressed. There seems to be consensus in the working group that the document is ready for publication. Document Quality The Document intended status is Informational. There is no known implementation. Personnel Behcet Sarikaya is the Document Shepherd Martin Vigoureux is the Responsible AD
RFC 8382 on Shared Bottleneck Detection for Coupled Congestion Control for RTP Media
A new Request for Comments is now available in online RFC libraries. RFC 8382 Title: Shared Bottleneck Detection for Coupled Congestion Control for RTP Media Author: D. Hayes, Ed., S. Ferlin, M. Welzl, K. Hiorth Status: Experimental Stream: IETF Date: June 2018 Mailbox:dav...@simula.no, sim...@ferlin.io, mich...@ifi.uio.no, krist...@ifi.uio.no Pages: 25 Characters: 49095 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rmcat-sbd-11.txt URL:https://www.rfc-editor.org/info/rfc8382 DOI:10.17487/RFC8382 This document describes a mechanism to detect whether end-to-end data flows share a common bottleneck. This mechanism relies on summary statistics that are calculated based on continuous measurements and used as input to a grouping algorithm that runs wherever the knowledge is needed. This document is a product of the RTP Media Congestion Avoidance Techniques 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
