A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication
RFC 6465
Recipient expansions
| Mail trigger | To | Cc |
|---|---|---|
| doc_added_comment | avtext-chairs@ietf.org, ben@nostrum.com, rfc6465@ietf.org | |
| doc_external_resource_change_requested | avtext-chairs@ietf.org, gonzalo.camarillo@ericsson.com | |
| doc_state_edited | avtext-chairs@ietf.org, ben@nostrum.com, gonzalo.camarillo@ericsson.com, rfc6465@ietf.org | |
| ipr_posted_on_doc |
The following Last Call announcement was sent out (ends 2020-12-09): From: The IESG To: IETF-Announce CC: draft-ietf-roll-useofrplinfo@ietf.org, roll-chairs@ietf.org, roll@ietf.org, consultancy@vanderstok.org, aretana.ietf@gmail.com, Peter Van der Stok Reply-To: last-call@ietf.org Sender: Subject: Last Call: (Using RPI Option Type, Routing Header for Source Routes and IPv6-in-IPv6 encapsulation in the RPL Data Plane) to Proposed Standard The IESG has received a request from the Routing Over Low power and Lossy networks WG (roll) to consider the following document: - 'Using RPI Option Type, Routing Header for Source Routes and IPv6-in- IPv6 encapsulation in the RPL Data Plane' 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 last-call@ietf.org mailing lists by 2020-12-09. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document looks at different data flows through LLN (Low-Power and Lossy Networks) where RPL (IPv6 Routing Protocol for Low-Power and Lossy Networks) is used to establish routing. The document enumerates the cases where RFC6553 (RPI Option Type), RFC6554 |
avt@ietf.org, ipr-announce@ietf.org |