IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Revision to Registration Procedures for Multiple BMP Registries (draft-ietf-grow-bmp-registries-change)
By John Scudder, 2018-12-09 TXT HTML PDF
Abstract: This document updates RFC 7854, BGP Monitoring Protocol (BMP) by making a change to the registration procedures for several registries. Specifically, any BMP registry with a range of 32768-65530 designated "Specification Required" has that range re- designated as "First Come First Served".
- Level 1 Area Abstraction for IS-IS (draft-li-lsr-isis-area-abstraction)
By Tony Li, 2018-12-07 TXT HTML PDF
Abstract: Link state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies, leading to scale issues.
- Hierarchical IS-IS (draft-li-lsr-isis-hierarchical-isis)
By Tony Li, 2018-12-07 TXT HTML PDF
Abstract: The IS-IS routing protocol was originally defined with a two level hierarchical structure. This was adequate for the networks at the time. As we continue to expand the scale of our networks, it is apparent that additional hierarchy would be a welcome degree of flexibility in network design.
- Multicast DF Election for EVPN Based on bandwidth or quantity (draft-liu-bess-evpn-mcast-bw-quantity-df-election)
By Yisong Liu, Mike McBride, 2018-12-09 TXT HTML PDF
Abstract: Ethernet Virtual Private Network (EVPN, RFC7432) is becoming prevalent in Data Centers, Data Center Interconnect (DCI) and Service Provider VPN applications. When multi-homing from a CE to multiple PEs, including links in an EVPN instance on a given Ethernet Segment, in an all-active redundancy mode, [RFC7432] describes a basic mechanism to elect a Designated Forwarder (DF), and [I-D.ietf-bess- evpn-df-election-framework] improves basic DF election by a HRW algorithm. [I-D.ietf-bess-evpn-per-mcast-flow-df-election] enhances the HRW algorithm for the multicast flows to perform DF election at the granularity of (ESI, VLAN, Mcast flow). This document specifies a new algorithm, based on multicast bandwidth utilization and multicast state quantity, in order for the multicast flows to elect a DF.
- IANA Registry Updates for OpenPGP (draft-openpgp-iana-registry-updates)
By Ronald Tse, Werner Koch, Derek Atkins, 2018-12-07 TXT HTML PDF
Abstract: This document describes a number of changes to the OpenPGP (RFC 4880) IANA registries that range from adding notes to the registry to changing registration policies. These changes were motivated by recently proposed extensions to OpenPGP. Existing IANA OpenPGP registry policies are defined by RFC 4880.
Updated Drafts
- remoteStorage (draft-dejong-remotestorage)
By Michiel de Jong, F. Kooman, 2018-12-08 TXT HTML PDF
Abstract: This draft describes a protocol by which client-side applications, running inside a web browser, can communicate with a data storage server that is hosted on a different domain name. This way, the provider of a web application need not also play the role of data storage provider. The protocol supports storing, retrieving, and removing individual documents, as well as listing the contents of an individual folder, and access control is based on bearer tokens.
- An Inventory of Transport-centric Functions Provided by Middleboxes: An Operator Perspective (draft-dolson-transport-middlebox)
By David Dolson, Juho Snellman, Mohamed Boucadair, Christian Jacquenet, 2018-12-06 TXT HTML PDF
Abstract: This document summarizes an operator's perception of the benefits that may be provided by intermediary devices that execute functions beyond normal IP forwarding. Such intermediary devices are often called "middleboxes".
- IDNA2008 and Unicode 11.0.0 (draft-faltstrom-unicode11)
By Patrik Faltstrom, 2018-12-09 TXT HTML PDF
Abstract: This document describes the changes between Unicode 6.3.0 and Unicode 11.0.0 in the context of IDNA2008. It further suggests a path forward for the IETF to ensure IDNA2008 follows the evolution of the Unicode Standard.
- VXLAN GPE Extension for Packets Exchange Between Control and User Plane of vBNG (draft-hu-nvo3-vxlan-gpe-extension-for-vbng)
By Shujun Hu, Fengwei Qin, Zhenqiang Li, Zitao Wang, Ting Ao, 2018-12-09 TXT HTML PDF
Abstract: This document briefly describes the architecture of control plane and user plane separated vBNG and define the extension of VXLAN-GPE for PPPoE/IPoE dialup packets exchange between control plane and user plane.
- An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4 (draft-ietf-6tisch-architecture)
By Pascal Thubert, 2018-12-07 TXT HTML PDF
Abstract: This document describes a network architecture that provides low- latency, low-jitter and high-reliability packet delivery. It combines a high speed powered backbone and subnetworks using IEEE 802.15.4 time-slotted channel hopping (TSCH) to meet the requirements of LowPower wireless deterministic applications.
- Guidelines for using the Multiplexing Features of RTP to Support Multiple Media Streams (draft-ietf-avtcore-multiplex-guidelines)
By Magnus Westerlund, Bo Burman, Colin Perkins, Harald Alvestrand, Roni Even, 2018-12-07 TXT HTML PDF
Abstract: The Real-time Transport Protocol (RTP) is a flexible protocol that can be used in a wide range of applications, networks, and system topologies. That flexibility makes for wide applicability, but can complicate the application design process. One particular design question that has received much attention is how to support multiple media streams in RTP. This memo discusses the available options and design trade-offs, and provides guidelines on how to use the multiplexing features of RTP to support multiple media streams.
- MVPN/EVPN Tunnel Aggregation with Common Labels (draft-ietf-bess-mvpn-evpn-aggregation-label)
By Zhaohui Zhang, Eric Rosen, Wen Lin, Zhenbin Li, IJsbrand Wijnands, 2018-12-07 TXT HTML PDF
Abstract: The MVPN specifications allow a single Point-to-Multipoint (P2MP) tunnel to carry traffic of multiple VPNs. The EVPN specifications allow a single P2MP tunnel to carry traffic of multiple Broadcast Domains (BDs). These features require the ingress router of the P2MP tunnel to allocate an upstream-assigned MPLS label for each VPN or for each BD. A packet sent on a P2MP tunnel then carries the label that is mapped to its VPN or BD. (In some cases, a distinct upstream-assigned is needed for each flow.) Since each ingress router allocates labels independently, with no coordination among the ingress routers, the egress routers may need to keep track of a large number of labels. The number of labels may need to be as large (or larger) than the product of the number of ingress routers times the number of VPNs or BDs. However, the number of labels can be greatly reduced if the association between a label and a VPN or BD is made by provisioning, so that all ingress routers assign the same label to a particular VPN or BD. New procedures are needed in order to take advantage of such provisioned labels. These new procedures also apply to Multipoint-to-Multipoint (MP2MP) tunnels. This document updates RFCs 6514, 7432 and 7582 by specifying the necessary procedures.
- Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams (draft-ietf-bfcpbis-rfc4583bis)
By Gonzalo Camarillo, Tom Kristensen, Christer Holmberg, 2018-12-08 TXT HTML PDF
Abstract: This document defines the Session Description Protocol (SDP) offer/ answer procedures for negotiating and establishing Binary Floor Control Protocol (BFCP) streams.
- DNS Stateful Operations (draft-ietf-dnsop-session-signal)
By Ray Bellis, Stuart Cheshire, John Dickinson, Sara Dickinson, Ted Lemon, Tom Pusateri, 2018-12-06 TXT HTML PDF
Abstract: This document defines a new DNS OPCODE for DNS Stateful Operations (DSO). DSO messages communicate operations within persistent stateful sessions, using type-length-value (TLV) syntax. Three TLVs are defined that manage session timeouts, termination, and encryption padding, and a framework is defined for extensions to enable new stateful operations. This document updates RFC 1035 by adding a new DNS header opcode which has different message semantics, and a new result code. This document updates RFC 7766 by redefining a session, providing new guidance on connection re-use, and providing a new mechanism for handling session idle timeouts.
- Expect-CT Extension for HTTP (draft-ietf-httpbis-expect-ct)
By estark@google.com, 2018-12-09 TXT HTML PDF
Abstract: This document defines a new HTTP header field named Expect-CT, which allows web host operators to instruct user agents to expect valid Signed Certificate Timestamps (SCTs) to be served on connections to these hosts. Expect-CT allows web host operators to discover misconfigurations in their Certificate Transparency deployments. Further, web host operaters can use Expect-CT to ensure that, if a UA which supports Expect-CT accepts a misissued certificate, that certificate will be discoverable in Certificate Transparency logs.
- Consolidated IASA2-Related Document Updates (draft-ietf-iasa2-consolidated-upd)
By John Klensin, 2018-12-07 TXT HTML PDF
Abstract: In 2018, the IETF began the transition to a new administrative structure and updated its IETF Administrative Support Activity (IASA) to a new "IASA 2.0" structure. In addition to more substantive changes that are described in other documents, the transition to the 2018 IETF Administrative Support structure changes several position titles and organizational relationships that are referenced elsewhere. Rather than reissue those referencing documents individually, this specification provides updates to them and deprecates some now-obsolete documents to ensure that there is no confusion due to these changes.
- Initial Performance Metric Registry Entries (draft-ietf-ippm-initial-registry)
By Alfred Morton, Marcelo Bagnulo, Philip Eardley, Kevin D'Souza, 2018-12-09 TXT HTML PDF
Abstract: This memo defines the Initial Entries for the Performance Metrics Registry. This version includes:
- Registry for Performance Metrics (draft-ietf-ippm-metric-registry)
By Marcelo Bagnulo, Benoit Claise, Philip Eardley, Alfred Morton, Aamer Akhter, 2018-12-09 TXT HTML PDF
Abstract: This document defines the format for the Performance Metrics registry and defines the IANA Registry for Performance Metrics. This document also gives a set of guidelines for Registered Performance Metric requesters and reviewers.
- OWAMP and TWAMP Well-Known Port Assignments (draft-ietf-ippm-port-twamp-test)
By Alfred Morton, Gregory Mirsky, 2018-12-09 TXT HTML PDF
Abstract: This memo explains the motivation and describes the re-assignment of well-known ports for the One-way Active Measurement Protocol and Two- way Active Measurement Protocol (OWAMP and TWAMP) protocols for control and measurement, and clarifies the meaning and composition of these standards track protocol names for the industry.
- Guidelines for Defining Packet Timestamps (draft-ietf-ntp-packet-timestamps)
By Tal Mizrahi, Joachim Fabini, Alfred Morton, 2018-12-09 TXT HTML PDF
Abstract: This document specifies guidelines for defining binary packet timestamp formats in networking protocols at various layers. It also presents three recommended timestamp formats. The target audience of this memo includes network protocol designers. It is expected that a new network protocol that requires a packet timestamp will, in most cases, use one of the recommended timestamp formats. If none of the recommended formats fits the protocol requirements, the new protocol specification should specify the format of the packet timestamp according to the guidelines in this document.
- RTP Payload Format for Flexible Forward Error Correction (FEC) (draft-ietf-payload-flexible-fec-scheme)
By Mo Zanaty, Varun Singh, Ali Begen, Giridhar Mandyam, 2018-12-07 TXT HTML PDF
Abstract: This document defines new RTP payload formats for the Forward Error Correction (FEC) packets that are generated by the non-interleaved and interleaved parity codes from source media encapsulated in RTP. These parity codes are systematic codes, where a number of FEC repair packets are generated from a set of source packets from one or more source RTP streams. These FEC repair packets are sent in a redundancy RTP stream separate from the source RTP stream(s) that carries the source packets. RTP source packets that were lost in transmission can be reconstructed using the source and repair packets that were received. The non-interleaved and interleaved parity codes which are defined in this specification offer a good protection against random and bursty packet losses, respectively, at a cost of decent complexity. The RTP payload formats that are defined in this document address the scalability issues experienced with the earlier specifications including RFC 2733, RFC 5109 and SMPTE 2022-1, and offer several improvements. Due to these changes, the new payload formats are not backward compatible with the earlier specifications, but endpoints that do not implement this specification can still work by simply ignoring the FEC repair packets.
- A P-Served-User Header Field Parameter for Originating CDIV session case in Session Initiation Protocol (SIP) (draft-ietf-sipcore-originating-cdiv-parameter)
By Marianne Mohali, 2018-12-09 TXT HTML PDF
Abstract: The P-Served-User header field was defined based on a requirement from 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) in order to convey the identity of the served user, his/ her registration state and the session case that applies to this particular communication session and application invocation. A session case is metadata that captures the status of the session of a served user: whether the served user is registered or not, and whether the session originates or terminates with the served user. This document updates RFC5502 by defining a new P-Served-User header field parameter, "orig-cdiv". The parameter conveys the session case used by a proxy when handling an originating session after Call Diversion (CDIV) services have been invoked for the served user. This document also fixes the ABNF in RFC 5502 and provides more guidance for using the P-Served-User header field in IP networks.
- Push Notification with the Session Initiation Protocol (SIP) (draft-ietf-sipcore-sip-push)
By Christer Holmberg, Michael Arnold, 2018-12-07 TXT HTML PDF
Abstract: This document describes how a Push Notification Service (PNS) can be used to wake suspended Session Initiation Protocol (SIP) User Agents (UAs), using push notifications, for the UA to be able to send binding-refresh REGISTER requests and to receive receive incoming SIP requests. The document defines new SIP URI parameters and new feature-capability indicators that can be used in SIP messages to indicate support of the mechanism defined in this document, to exchange PNS information between the SIP User Agent (UA) and the SIP entity that will request push notifications towards the UA, and to trigger such push notification requests.
- Segment Routing with MPLS data plane (draft-ietf-spring-segment-routing-mpls)
By Ahmed Bashandy, Clarence Filsfils, Stefano Previdi, Bruno Decraene, Stephane Litkowski, Rob Shakir, 2018-12-09 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. In the MPLS dataplane, the SR header is instantiated through a label stack. This document specifies the forwarding behavior to allow instantiating SR over the MPLS dataplane.
- EVPN Multicast Synchronization Enhancement (draft-liu-bess-evpn-mcast-synch-enhance)
By Yisong Liu, Donald Eastlake, 2018-06-09 TXT HTML PDF
Abstract: Ethernet Virtual Private Network (EVPN, RFC7432) solutions is becoming prevalent in Data Centers, Data Center Interconnect (DCI) and Service Provider VPN applications. In the scenario of multi-homing from a CE to multiple PEs with links used in a single-active or all-active redundancy mode, IGMP & MLD Join/Leave and PIM Join/RPT-Prune synchronization procedures have been provided. This document specifies an enhancement for IGMP/PIM signaling synchronization when using different Ethernet tag encapsulation mode.
- OAuth 2.0 for Browser-Based Apps (draft-parecki-oauth-browser-based-apps)
By Aaron Parecki, David Waite, 2018-12-08 TXT HTML PDF
Abstract: OAuth 2.0 authorization requests from apps running entirely in a browser are unable to use a Client Secret during the process, since they have no way to keep a secret confidential. This specification details the security considerations that must be taken into account when developing browser-based applications, as well as best practices for how they can securely implement OAuth 2.0.
Expired Drafts
- Traffic Accounting in Segment Routing Networks (draft-ali-spring-sr-traffic-accounting)
By Zafar Ali, Clarence Filsfils, Ketan Talaulikar, Siva Sivabalan, Martin Horneffer, Robert Raszuk, Stephane Litkowski, daniel.voyer@bell.ca, 2018-06-07 TXT HTML PDF
Abstract: Capacity planning is the continuous art of forecasting traffic load and failures to evolve the network topology, its capacity, and its routing to meet a defined Service-Level Agreement (SLA). This document takes a holistic view of network capacity planning and identifies the role of traffic accounting in network operation and capacity planning, without creating any additional states in the SR fabric.
- vObject Internationalization (draft-calconnect-vobject-i18n)
By Ronald Tse, Peter Tam, Michael Douglass, 2018-06-07 TXT HTML PDF
Abstract: This document specifies mechanisms for the internationalization of vObject content and its realization in vFormat.
- The vObject Model and vFormat Syntax (draft-calconnect-vobject-vformat)
By Ronald Tse, Peter Tam, Ken Murchison, Michael Douglass, 2018-06-07 TXT HTML PDF
Abstract: This document specifies the vObject data model and its corresponding syntax vFormat.
- Request for Comments (draft-carpenter-request-for-comments)
By Brian Carpenter, 2018-06-05 TXT HTML PDF
Abstract: This document discusses the Internet technical community's common document series.
- NEAT Sockets API (draft-dreibholz-taps-neat-socketapi)
By Thomas Dreibholz, 2018-06-07 TXT HTML PDF
Abstract: This document describes a BSD Sockets-like API on top of the callback-based NEAT User API. This facilitates porting existing applications to use a subset of NEAT's functionality.
- Segment Routing Traffic Accounting Counters (draft-filsfils-spring-sr-traffic-counters)
By Clarence Filsfils, Zafar Ali, Martin Horneffer, daniel.voyer@bell.ca, Muhammad Durrani, Robert Raszuk, 2018-06-07 TXT HTML PDF
Abstract: Segment Routing (SR) allows a headend node to steer a packet flow along any path. Intermediate per-flow states are eliminated thanks to source routing. Traffic accounting plays a critical role in network operation. A traffic account solution is required for SR networks that provides the necessary functionality without creating any additional per SR path states in the fabric.
- IPv6 Performance Measurement with Alternate Marking Method (draft-fioccola-v6ops-ipv6-alt-mark)
By Giuseppe Fioccola, Gunter Van de Velde, Mauro Cociglio, Praveen Muley, 2018-06-05 TXT HTML PDF
Abstract: This document describes how the alternate marking method in [RFC8321] can be used as the passive performance measurement method in an IPv6 domain, and will discuss the strengths and the weaknesses of the implementation options available to network operations. It proposes how to extend [RFC7837] to apply alternate marking technique.
- Flowspec Indirection-id Redirect (draft-ietf-idr-flowspec-path-redirect)
By Gunter Van de Velde, Keyur Patel, Zhenbin Li, 2018-06-05 TXT HTML PDF
Abstract: This document defines a new extended community known as "FlowSpec Redirect to indirection-id Extended Community". This extended community triggers advanced redirection capabilities to flowspec clients. When activated, this flowspec extended community is used by a flowspec client to retrieve the corresponding next-hop and encoding information within a localised indirection-id mapping table.
- Use Cases for SF Aware Topology Models (draft-ietf-teas-use-cases-sf-aware-topo-model)
By Igor Bryskin, Xufeng Liu, Jim Guichard, Young Lee, Luis Contreras, Daniele Ceccarelli, Jeff Tantsura, 2018-06-05 TXT HTML PDF
Abstract: This document describes some use cases that benefit from the network topology models that are service and network function aware.
- Applying GREASE to TLS Extensibility (draft-ietf-tls-grease)
By David Benjamin, 2018-06-06 TXT HTML PDF
Abstract: This document describes GREASE (Generate Random Extensions And Sustain Extensibility), a mechanism to prevent extensibility failures in the TLS ecosystem. It reserves a set of TLS protocol values that may be advertised to ensure peers correctly handle unknown values.
- Trustchain protocol (draft-pouwelse-trustchain)
By Johan Pouwelse, 2018-06-05 TXT HTML PDF
Abstract: Trustchain is a protocol for a networked datastructure, designed to act as a trust ledger. This protocol acts as a decentralized alternative to platforms like eBay, Airbnb, and Uber. It is specifically designed to record transactions among strangers without central control, support high transaction volumes, be application neutral, and avoid vendor lock-in. The protocol defines recording transactions in an ordered list using an append-only datastructure, a new communication overlay, and a horizontally scalable consensus protocol based on checkpoint consensus, called CHECO. Trustchain has resistance to traditional blockchain attacks, such as the 51 percent majority attack. This is achieved by using a graph-based append-only datastructure combined with a personal blockchain for each participant with their own genesis block.
- The Archive and Package (arcp) URI scheme (draft-soilandreyes-arcp)
By Stian Soiland-Reyes, Marcos Caceres, 2018-02-05 TXT HTML PDF
Abstract: This specification define the Archive and Package URI scheme "arcp".
- Problem Statement for Secure End to End Privacy Enabled Mapping System (draft-xyz-atick-ps)
By Dirk Hugo, Behcet Sarikaya, Luigi Iannone, Tom Herbert, 2018-06-07 TXT HTML PDF
Abstract: Problem Statement for Secure End to End Privacy Enabled Mapping System for Identifier Locator separation systems is presented. Since identifiers are often carried in packet headers in clear, and mapping systems are often designed to be accessible by any entity, to preserve identifier's privacy, lookups to the mapping system should be allowed only by authorized entities. In mapping systems, in addition to privacy, security also requires special attention because of the caches introduced into the data path. Any denial of service attacks on the cache should not allow the communication to come to an end.
- Gap and Solution Space Analysis for End to End Privacy Enabled Mapping System (draft-xyzy-atick-gaps)
By Dirk Hugo, Behcet Sarikaya, Tom Herbert, Luigi Iannone, 2018-06-07 TXT HTML PDF
Abstract: This document presents a gap and solution analysis for end-to-end privacy enabled mapping systems. Each of the identifier locator separation system has its own approach to mapping identifiers to the locators. We analyse all these approaches and identify the gaps in each of them and do a solution space analysis in an attempt to identify a mapping system that can be end to end privacy enabled.
|
Drafts Sent to IESG
IESG Progress
- Packet Delivery Deadline time in 6LoWPAN Routing Header (draft-ietf-6lo-deadline-time): AD Evaluation » Last Call Requested
By Lijo Thomas, Satish Anamalamudi, S.V.R Anand, Malati Hegde, Charles Perkins, 2018-10-15 TXT HTML PDF
Abstract: This document specifies a new type for the 6LoWPAN routing header containing the delivery deadline time for data packets. The deadline time enables forwarding and scheduling decisions for time critical IoT M2M applications that need deterministic delay guarantees over constrained networks and operate within time-synchronized networks.
- Transmission of IPv6 Packets over Near Field Communication (draft-ietf-6lo-nfc): AD Evaluation » Last Call Requested
By Younghwan Choi, Yong-Geun Hong, Joo-Sang Youn, Dongkyun Kim, JinHyeock Choi, 2018-11-05 TXT HTML PDF
Abstract: Near field communication (NFC) is a set of standards for smartphones and portable devices to establish radio communication with each other by touching them together or bringing them into proximity, usually no more than 10 cm. NFC standards cover communications protocols and data exchange formats, and are based on existing radio-frequency identification (RFID) standards including ISO/IEC 14443 and FeliCa. The standards include ISO/IEC 18092 and those defined by the NFC Forum. The NFC technology has been widely implemented and available in mobile phones, laptop computers, and many other devices. This document describes how IPv6 is transmitted over NFC using 6LowPAN techniques.
- Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams (draft-ietf-bfcpbis-rfc4583bis): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Gonzalo Camarillo, Tom Kristensen, Christer Holmberg, 2018-12-08 TXT HTML PDF
Abstract: This document defines the Session Description Protocol (SDP) offer/ answer procedures for negotiating and establishing Binary Floor Control Protocol (BFCP) streams.
- Expect-CT Extension for HTTP (draft-ietf-httpbis-expect-ct): IESG Evaluation::Revised I-D Needed » ::AD Followup
By estark@google.com, 2018-12-09 TXT HTML PDF
Abstract: This document defines a new HTTP header field named Expect-CT, which allows web host operators to instruct user agents to expect valid Signed Certificate Timestamps (SCTs) to be served on connections to these hosts. Expect-CT allows web host operators to discover misconfigurations in their Certificate Transparency deployments. Further, web host operaters can use Expect-CT to ensure that, if a UA which supports Expect-CT accepts a misissued certificate, that certificate will be discoverable in Certificate Transparency logs.
- A P-Served-User Header Field Parameter for Originating CDIV session case in Session Initiation Protocol (SIP) (draft-ietf-sipcore-originating-cdiv-parameter): Approved-announcement to be sent::Revised I-D Needed » ::AD Followup
By Marianne Mohali, 2018-12-09 TXT HTML PDF
Abstract: The P-Served-User header field was defined based on a requirement from 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) in order to convey the identity of the served user, his/ her registration state and the session case that applies to this particular communication session and application invocation. A session case is metadata that captures the status of the session of a served user: whether the served user is registered or not, and whether the session originates or terminates with the served user. This document updates RFC5502 by defining a new P-Served-User header field parameter, "orig-cdiv". The parameter conveys the session case used by a proxy when handling an originating session after Call Diversion (CDIV) services have been invoked for the served user. This document also fixes the ABNF in RFC 5502 and provides more guidance for using the P-Served-User header field in IP networks.
- Push Notification with the Session Initiation Protocol (SIP) (draft-ietf-sipcore-sip-push): AD Evaluation::Revised I-D Needed » In Last Call
By Christer Holmberg, Michael Arnold, 2018-12-07 TXT HTML PDF
Abstract: This document describes how a Push Notification Service (PNS) can be used to wake suspended Session Initiation Protocol (SIP) User Agents (UAs), using push notifications, for the UA to be able to send binding-refresh REGISTER requests and to receive receive incoming SIP requests. The document defines new SIP URI parameters and new feature-capability indicators that can be used in SIP messages to indicate support of the mechanism defined in this document, to exchange PNS information between the SIP User Agent (UA) and the SIP entity that will request push notifications towards the UA, and to trigger such push notification requests.
Drafts Sent to RFC Editor
- DNS Stateful Operations (draft-ietf-dnsop-session-signal): IESG Evaluation::AD Followup » RFC Ed Queue
By Ray Bellis, Stuart Cheshire, John Dickinson, Sara Dickinson, Ted Lemon, Tom Pusateri, 2018-12-06 TXT HTML PDF
Abstract: This document defines a new DNS OPCODE for DNS Stateful Operations (DSO). DSO messages communicate operations within persistent stateful sessions, using type-length-value (TLV) syntax. Three TLVs are defined that manage session timeouts, termination, and encryption padding, and a framework is defined for extensions to enable new stateful operations. This document updates RFC 1035 by adding a new DNS header opcode which has different message semantics, and a new result code. This document updates RFC 7766 by redefining a session, providing new guidance on connection re-use, and providing a new mechanism for handling session idle timeouts.
Other Status Changes
- Level 1 Area Abstraction for IS-IS (draft-li-area-abstraction): Active » Replaced by draft-li-lsr-isis-area-abstraction
By Tony Li, 2018-06-29 TXT HTML PDF
Abstract: Link state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies, leading to scale issues.
- Hierarchical IS-IS (draft-li-hierarchical-isis): Active » Replaced by draft-li-lsr-isis-hierarchical-isis
By Tony Li, 2018-06-29 TXT HTML PDF
Abstract: The IS-IS routing protocol was originally defined with a two level hierarchical structure. This was adequate for the networks at the time. As we continue to expand the scale of our networks, it is apparent that additional hierarchy would be a welcome degree of flexibility in network design.
- Revision to Registration Procedures for Multiple BMP Registries (draft-scudder-grow-bmp-registries-change): Active » Replaced by draft-ietf-grow-bmp-registries-change
By John Scudder, 2018-09-20 TXT HTML PDF
Abstract: This document updates RFC 7854, BGP Monitoring Protocol (BMP) by making a change to the registration procedures for several registries. Specifically, any BMP registry with a range of 32768-65530 designated "Specification Required" has that range re- designated as "First Come First Served".
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
