IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Distributed-Denial-of-Service Open Threat Signaling (DOTS) Server Discovery (draft-boucadair-dots-server-discovery)
By Mohamed Boucadair, Tirumaleswar Reddy, Prashanth Patil, 2017-06-27 TXT HTML PDF
Abstract: It may not be possible for a network to determine the cause for an attack, but instead just realize that some resources seem to be under attack. To fill that gap, Distributed-Denial-of-Service Open Threat Signaling (DOTS) allows a network to inform a server that it is under a potential attack so that appropriate mitigation actions are undertaken.
- Recommendation for Compressing ALTO Path Vector (draft-gao-alto-routing-state-abstraction)
By Kai Gao, xinwang2014@hotmail.com, Chen Gu, Yang Yang, G.Robert Chen, 2017-06-27 TXT HTML PDF
Abstract: The path vector extension [I-D.ietf-alto-path-vector] has extended the original ALTO protocol [RFC7285] with the ability to represent not only end-to-end metrics but also information about shared link risk groups (SLRG).
- No-Path DAO modifications (draft-ietf-roll-efficient-npdao)
By JADHAV RAHUL, Rabi Sahoo, Zhen Cao, 2017-06-27 TXT HTML PDF
Abstract: This document describes the problems associated with the use of No- Path DAO messaging in RPL and a signaling changes to improve route invalidation efficiency.
- Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties (draft-madi-sidrops-rp)
By Di Ma, Stephen Kent, 2017-06-27 TXT HTML PDF
Abstract: This document provides a single reference point for requirements for Relying Party (RP) software for use in the Resource Public Key Infrastructure (RPKI). It cites requirements that appear in several RPKI RFCs, making it easier for implementers to become aware of these requirements that are segmented with orthogonal functionalities.
- Extended Mobility Procedures for EVPN-IRB (draft-malhotra-bess-evpn-irb-extended-mobility)
By Neeraj Malhotra, Ali Sajassi, Aparna Pattekar, Avinash Lingala, 2017-06-27 TXT HTML PDF
Abstract: Procedure to handle host mobility in a layer 2 Network with EVPN control plane is defined as part of RFC 7432. EVPN has since evolved to find wider applicability across various IRB use cases that include distributing both MAC and IP reachability via a common EVPN control plane. MAC Mobility procedures defined in RFC 7432 are extensible to IRB use cases if a fixed 1:1 mapping between VM IP and MAC is assumed across VM moves. Generic mobility support for IP and MAC that allows these bindings to change across moves is required to support a broader set of EVPN IRB use cases, and requires further consideration. EVPN-LAG based multi-homing further introduces scenarios that require additional consideration from mobility perspective. Intent of this draft is to enumerate a set of design considerations applicable to mobility across EVPN IRB use cases and define generic sequence number assignment procedures to address these IRB use cases.
- Guidelines for Defining Packet Timestamps (draft-mizrahi-intarea-packet-timestamps)
By Tal Mizrahi, Joachim Fabini, Al Morton, 2017-06-27 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.
- OWAMP and TWAMP Well-Known Port Assignments (draft-morton-ippm-port-twamp-test)
By Al Morton, 2017-06-27 TXT HTML PDF
Abstract: This memo describes new well-known port assignments for the OWAMP and TWAMP protocols for control and measurement, and clarifies the meaning and composition of these standards track protocol names for the industry.
- GPCOMP (draft-moskowitz-gpcomp)
By Robert Moskowitz, Susan Hares, Igor Faynberg, Huilan Lu, Pierpaolo Giacomin, 2017-06-27 TXT HTML PDF
Abstract: This document describes a protocol intended to provide lossless compression for use within any datagram. It is particularly intended for use in encrypted datagrams where lower-level compression is ineffective.
- Fast HIP Host Mobility (draft-moskowitz-hip-fast-mobility)
By Robert Moskowitz, Xiaohu Xu, 2017-06-27 TXT HTML PDF
Abstract: This document describes mobility scenarios and how to aggressively support them in HIP. The goal is minimum lag in the mobility event.
- Session Security Envelope (draft-moskowitz-sse)
By Robert Moskowitz, Igor Faynberg, Huilan Lu, Susan Hares, Pierpaolo Giacomin, 2017-06-27 TXT HTML PDF
Abstract: This memo specifies the details of the Session Security Envelope (SSE). SSE is a session protocol aiming to guarantee confidentiality, integrity and authentication completely independently by the underlying context, namely network and transport layers. A single session using the SEE protocol can include a single transport session or multiple transport sessions. This mean that SSE can survive the break-down in network and transport layers or to attacks carried against them. SSE is also applicable in networks lacking in classic inter-networking and transport protocols SSE relies on modern AEAD block cipher modes of operations, a class of block cipher modes which allows, at the same time, to authenticate the message while encrypting a part of it.
- Secure Session Layer Services KMP via HIP (draft-moskowitz-ssls-hip)
By Robert Moskowitz, Liang Xia, Igor Faynberg, Susan Hares, Pierpaolo Giacomin, 2017-06-27 TXT HTML PDF
Abstract: This memo specifies the details for establishing and maintaining a Secure Session Layer Services (SSLS) association between two applications using the Host Identity Protocol (HIP [RFC7401]). This is primarily achieved by adding SSLS specific HIP parameters for the HIP base exchange. The SSLS association state and security boundaries are also defined.
- <BGP Support for Fast Link Status Notification> (draft-sun-idr-bgp-ls-notification)
By Marcus Sun, Burjiz Pithawala, Feng Gao, 2017-06-27 TXT HTML PDF
Abstract: This document describes the use of Border Gateway Protocol (BGP) community. This optional transitive community will instruct router to monitor itself ports . With this community, controller only needs to send route update message once and will get the feedback only if link status changes. In particular this community can help controller get the link status changing notification much faster than current method.
- Communication Units Granularity Considerations for Multi-Path Aware Transport Selection (draft-tiesel-taps-communitgrany)
By Philipp Tiesel, Theresa Enghardt, 2017-06-27 TXT HTML PDF
Abstract: This document provides an abstract framework to reason about the composition of multi-path aware systems in a protocol-independent fashion. It discusses basic mechanisms that are used in multi-path systems and their applicability to different granularities of communication units. This document is targeted as consideration basis for automation of destination, path and transport protocol selection within the transport layer.
Updated Drafts
- Use of the Hash-based Merkle Tree Signature (MTS) Algorithm in the Cryptographic Message Syntax (CMS) (draft-housley-cms-mts-hash-sig)
By Russ Housley, 2017-06-27 TXT HTML PDF
Abstract: This document specifies the conventions for using the Merkle Tree Signatures (MTS) digital signature algorithm with the Cryptographic Message Syntax (CMS). The MTS algorithm is one form of hash-based digital signature.
- 6top Protocol (6P) (draft-ietf-6tisch-6top-protocol)
By Qin Wang, Xavier Vilajosana, Thomas Watteyne, 2017-06-27 TXT HTML PDF
Abstract: This document defines the 6top Protocol (6P), which enables distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes to add/delete TSCH cells to one another. 6P is part of the 6TiSCH Operation Sublayer (6top), the next higher layer to the IEEE Std 802.15.4 TSCH medium access control layer. The 6top Scheduling Function (SF) decides when to add/delete cells, and triggers 6P Transactions. Several SFs can be defined, each identified by a different 6top Scheduling Function Identifier (SFID). This document lists the requirements for an SF, but leaves the definition of the SF out of scope. SFs are expected to be defined in future companion specifications.
- Multicast VPN Using BIER (draft-ietf-bier-mvpn)
By Eric Rosen, Mahesh Sivakumar, Sam Aldrin, Andrew Dolganow, Tony Przygienda, 2017-06-27 TXT HTML PDF
Abstract: The Multicast Virtual Private Network (MVPN) specifications require the use of multicast tunnels ("P-tunnels") that traverse a Service Provider's backbone network. The P-tunnels are used for carrying multicast traffic across the backbone. A variety of P-tunnel types are supported. Bit Index Explicit Replication (BIER) is a new architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol. This document specifies the protocol and procedures that allow MVPN to use BIER as the method of carrying multicast traffic over an SP backbone network.
- Security Considerations for RFC5011 Publishers (draft-ietf-dnsop-rfc5011-security-considerations)
By Wesley Hardaker, Warren Kumari, 2017-06-27 TXT HTML PDF
Abstract: This document extends the RFC5011 rollover strategy with timing advice that must be followed in order to maintain security. Specifically, this document describes the math behind the minimum time-length that a DNS zone publisher must wait before signing with only recently added DNSKEYs. This document also describes the minimum time-length that a DNS zone publisher must wait after publishing a revoked DNSKEY before assuming that all active RFC5011 resolvers should have seen the revocation-marked key and removed it from their list of trust anchors.
- Special-Use Domain Names Problem Statement (draft-ietf-dnsop-sutld-ps)
By Ted Lemon, Ralph Droms, Warren Kumari, 2017-06-27 TXT HTML PDF
Abstract: The Special-Use Domain Names IANA registry policy defined in RFC 6761 has been shown through experience to present unanticipated challenges. This memo presents a list, intended to be comprehensive, of the problems that have been identified. In addition it reviews the history of Domain Names and summarizes current IETF publications and some publications from other organizations relating to Special- Use Domain Names.
- Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol (draft-ietf-ice-trickle)
By Emil Ivov, Eric Rescorla, Justin Uberti, Peter Saint-Andre, 2017-06-27 TXT HTML PDF
Abstract: This document describes "Trickle ICE", an extension to the Interactive Connectivity Establishment (ICE) protocol that enables ICE agents to send and receive candidates incrementally rather than exchanging complete lists. With such incremental provisioning, ICE agents can begin connectivity checks while they are still gathering candidates and considerably shorten the time necessary for ICE processing to complete.
- Network Configuration Protocol (NETCONF) Access Control Model (draft-ietf-netconf-rfc6536bis)
By Andy Bierman, Martin Bjorklund, 2017-06-27 TXT HTML PDF
Abstract: The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a pre-configured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.
- PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols (draft-ietf-precis-7564bis)
By Peter Saint-Andre, Marc Blanchet, 2017-06-27 TXT HTML PDF
Abstract: Application protocols using Unicode code points in protocol strings need to properly handle such strings in order to enforce internationalization rules for strings placed in various protocol slots (such as addresses and identifiers) and to perform valid comparison operations (e.g., for purposes of authentication or authorization). This document defines a framework enabling application protocols to perform the preparation, enforcement, and comparison of internationalized strings ("PRECIS") in a way that depends on the properties of Unicode code points and thus is more agile with respect to versions of Unicode. As a result, this framework provides a more sustainable approach to the handling of internationalized strings than the previous framework, known as Stringprep (RFC 3454). This document obsoletes RFC 7564.
- Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords (draft-ietf-precis-7613bis)
By Peter Saint-Andre, Alexey Melnikov, 2017-06-27 TXT HTML PDF
Abstract: This document describes updated methods for handling Unicode strings representing usernames and passwords. The previous approach was known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454). The methods specified in this document provide a more sustainable approach to the handling of internationalized usernames and passwords. This document obsoletes RFC 7613.
- Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames (draft-ietf-precis-7700bis)
By Peter Saint-Andre, 2017-06-27 TXT HTML PDF
Abstract: This document describes methods for handling Unicode strings representing memorable, human-friendly names (called "nicknames", "display names", or "petnames") for people, devices, accounts, websites, and other entities. This document obsoletes RFC 7700.
- Security Automation and Continuous Monitoring (SACM) Requirements (draft-ietf-sacm-requirements)
By Nancy Cam-Winget, Lisa Lorenzin, 2017-06-27 TXT HTML PDF
Abstract: This document defines the scope and set of requirements for the Secure Automation and Continuous Monitoring (SACM) architecture, data model and transfer protocols. The requirements and scope are based on the agreed upon use cases ([RFC7632]).
- Datacenter TCP (DCTCP): TCP Congestion Control for Datacenters (draft-ietf-tcpm-dctcp)
By Stephen Bensley, Dave Thaler, Praveen Balasubramanian, Lars Eggert, Glenn Judd, 2017-06-27 TXT HTML PDF
Abstract: This informational memo describes Datacenter TCP (DCTCP), a TCP congestion control scheme for datacenter traffic. DCTCP extends the Explicit Congestion Notification (ECN) processing to estimate the fraction of bytes that encounter congestion, rather than simply detecting that some congestion has occurred. DCTCP then scales the TCP congestion window based on this estimate. This method achieves high burst tolerance, low latency, and high throughput with shallow- buffered switches. This memo also discusses deployment issues related to the coexistence of DCTCP and conventional TCP, the lack of a negotiating mechanism between sender and receiver, and presents some possible mitigations. This memo documents DCTCP as currently implemented by several major operating systems. DCTCP as described in this draft is applicable to deployments in controlled environments like datacenters but it must not be deployed over the public Internet without additional measures.
- Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim (draft-ietf-tsvwg-rfc6040update-shim)
By Bob Briscoe, 2017-06-27 TXT HTML PDF
Abstract: RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of ECN consistent for all forms of IP in IP tunnel. This specification updates RFC 6040 to clarify that its scope includes tunnels where two IP headers are separated by at least one shim header that is not sufficient on its own for wide area packet forwarding. It surveys widely deployed IP tunnelling protocols separated by such shim header(s) and updates the specifications of those that do not mention ECN propagation (L2TPv2, L2TPv3, GRE and Teredo). This specification also updates RFC 6040 with configuration requirements needed to make any legacy tunnel ingress safe.
- Transport Options for UDP (draft-ietf-tsvwg-udp-options)
By Joseph Touch, 2017-06-27 TXT HTML PDF
Abstract: Transport protocols are extended through the use of transport header options. This document experimentally extends UDP by indicating the location, syntax, and semantics for UDP transport layer options.
- GMPLS Routing and Signaling Framework for Flexible Ethernet (FlexE) (draft-izh-ccamp-flexe-fwk)
By Iftekhar Hussain, Radha Valiveti, Qilei Wang, Loa Andersson, Mach Chen, zhenghaomian@huawei.com, 2017-06-27 TXT HTML PDF
Abstract: As different from earlier Ethernet data planes FlexE allows for decoupling of the Ethernet Physical layer (PHY) and Media Access Control layer (MAC) rates.
- A Yang Data Model for WSON Tunnel (draft-lee-ccamp-wson-tunnel-model)
By Young Lee, Dhruv Dhody, Victor Lopezalvarez, Daniel King, Bin-Yeong Yoon, Ricard Vilata, 2017-06-27 TXT HTML PDF
Abstract: This document provides a YANG data model for WSON TE tunnel.
- Hash-Based Signatures (draft-mcgrew-hash-sigs)
By David McGrew, Michael Curcio, Scott Fluhrer, 2017-06-26 TXT HTML PDF
Abstract: This note describes a digital signature system based on cryptographic hash functions, following the seminal work in this area of Lamport, Diffie, Winternitz, and Merkle, as adapted by Leighton and Micali in 1995. It specifies a one-time signature scheme and a general signature scheme. These systems provide asymmetric authentication without using large integer mathematics and can achieve a high security level. They are suitable for compact implementations, are relatively simple to implement, and naturally resist side-channel attacks. Unlike most other signature systems, hash-based signatures would still be secure even if it proves feasible for an attacker to build a quantum computer.
- Forward Error Correction (FEC) Framework Extension to Sliding Window Codes (draft-roca-tsvwg-fecframev2)
By Vincent Roca, Ali Begen, 2017-06-27 TXT HTML PDF
Abstract: RFC 6363 describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. However FECFRAME as per RFC 6363 is restricted to block FEC codes. The present document extends FECFRAME to support FEC Codes based on a sliding encoding window, in addition to Block FEC Codes, in a backward compatible way. During multicast/broadcast real-time content delivery, the use of sliding window codes significantly improves robustness in harsh environments, with less repair traffic and lower FEC-related added latency.
- The Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Scheme for FECFRAME (draft-roca-tsvwg-rlc-fec-scheme)
By Vincent Roca, 2017-06-27 TXT HTML PDF
Abstract: This document describes a fully-specified FEC scheme for the Sliding Window Random Linear Codes (RLC) over GF(2^^m), where m equals 1 (binary case), 4 or 8, that can be used to protect arbitrary media streams along the lines defined by FECFRAME extended to sliding window codes. These sliding window FEC codes rely on an encoding window that slides over the source symbols, generating new repair symbols whenever needed. Compared to block FEC codes, these sliding window FEC codes offer key advantages with real-time flows in terms of reduced FEC-related latency while often providing improved erasure recovery capabilities.
- On Scalability of In-situ OAM (draft-song-ippm-ioam-scalability)
By Haoyu Song, Tianran Zhou, 2017-06-27 TXT HTML PDF
Abstract: This document describes several potential scalability issues when implementing in-situ OAM based on the current in-situ OAM documents and proposes the corresponding solutions and modifications to the current in-situ OAM specification. Specifically, we extend in-situ OAM to support more standard tracing data than is currently defined and add new features to avoid limitations on MTU, bandwidth, forwarding path length, and node processing capability. We provide use cases to motivate our proposal and base the changes on the current in-situ OAM header format specification.
- Serving Stale Data to Improve DNS Resiliency (draft-tale-dnsop-serve-stale)
By David Lawrence, Warren Kumari, 2017-06-27 TXT HTML PDF
Abstract: This draft defines a method for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data.
- Resource Orchestration for Multi-Domain Data Analytics (draft-xiang-alto-exascale-network-optimization)
By Qiao Xiang, Harvey Newman, Greg Bernstein, Azher Mughal, Justas Balcas, J. Zhang, duhaizhou@gmail.com, Yang Yang, 2017-06-27 TXT HTML PDF
Abstract: Data-intensive analytics is entering the era of multi-domain, geographically-distributed, collaborative computing, where different organizations contribute various resources to collaboratively collect, share and analyze extremely large amounts of data. Examples of this paradigm include the Compact Muon Solenoid (CMS) and A Toroidal LHC ApparatuS (ATLAS) experiments of the Large Hadron Collider (LHC) program. Massive datasets continue to be acquired, simulated, processed and analyzed by globally distributed science networks in these collaborations, and the volume of this data is growing exponentially. Applications that manage and analyze such massive data volumes can benefit substantially from the information about networking, computing and storage resources from each member sites, and more directly from network-resident services that optimize and load balance resource usage among multiple data transfer and analytic requests, and achieve a better utilization of multi- resources in clusters. Hence this new paradigm calls for a framework to manage a large set of distributively owned heterogeneous resources, with the fundamental objective of efficient resource utilization, following the autonomy and privacy of resource owners.
Expired Drafts
|
Drafts Sent to IESG
- A YANG Data Model for Routing Information Protocol (RIP) (draft-ietf-rtgwg-yang-rip): Active » Publication Requested
By Xufeng Liu, Prateek Sarda, Vikram Choudhary, 2017-06-06 TXT HTML PDF
Abstract: This document describes a data model for the Routing Information Protocol (RIP). Both RIP version 2 and RIPng are covered.
- A YANG Data Model for Virtual Router Redundancy Protocol (VRRP) (draft-ietf-rtgwg-yang-vrrp): Active » Publication Requested
By Xufeng Liu, Athanasios Kyparlis, Ravi Parikh, Acee Lindem, Mingui Zhang, 2017-05-30 TXT HTML PDF
Abstract: This document describes a data model for Virtual Router Redundancy Protocol (VRRP). Both version 2 and version 3 of VRRP are covered.
- An Architecture for Use of PCE and PCEP in a Network with Central Control (draft-ietf-teas-pce-central-control): Active » Publication Requested
By Adrian Farrel, Quintin Zhao, Zhenbin Li, Chao Zhou, 2017-06-15 TXT HTML PDF
Abstract: The Path Computation Element (PCE) has become established as a core component of Software Defined Networking (SDN) systems. It can compute optimal paths for traffic across a network for any definition of "optimal" and can also monitor changes in resource availability and traffic demands to update the paths.
IESG Progress
- Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords (draft-ietf-precis-7613bis): In Last Call » IESG Evaluation
By Peter Saint-Andre, Alexey Melnikov, 2017-06-27 TXT HTML PDF
Abstract: This document describes updated methods for handling Unicode strings representing usernames and passwords. The previous approach was known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454). The methods specified in this document provide a more sustainable approach to the handling of internationalized usernames and passwords. This document obsoletes RFC 7613.
- Security Automation and Continuous Monitoring (SACM) Requirements (draft-ietf-sacm-requirements): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Nancy Cam-Winget, Lisa Lorenzin, 2017-06-27 TXT HTML PDF
Abstract: This document defines the scope and set of requirements for the Secure Automation and Continuous Monitoring (SACM) architecture, data model and transfer protocols. The requirements and scope are based on the agreed upon use cases ([RFC7632]).
- Content-ID header field in Session Initiation Protocol (SIP) (draft-ietf-sipcore-content-id): In Last Call » Waiting for AD Go-Ahead
By Christer Holmberg, Ivo Sedlacek, 2017-06-05 TXT HTML PDF
Abstract: This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). The document also updates RFC 5621, to enable a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields.
Drafts Sent to RFC Editor
Other Status Changes
- DHCP Options for Distributed-Denial-of-Service Open Threat Signaling (DOTS) (draft-boucadair-dots-dhcp): Active » Replaced by draft-boucadair-dots-server-discovery
By Mohamed Boucadair, 2017-04-12 TXT HTML PDF
Abstract: It may not be possible for a network to determine the cause for an attack, but instead just realize that some resources seem to be under attack. To fill that gap, Distributed-Denial-of-Service Open Threat Signaling (DOTS) allows a network to inform a server that it is under a potential attack so that appropriate mitigation actions are undertaken.
- No-Path DAO modifications (draft-jadhav-roll-efficient-npdao): Active » Replaced by draft-ietf-roll-efficient-npdao
By JADHAV RAHUL, Rabi Sahoo, Zhen Cao, 2017-05-13 TXT HTML PDF
Abstract: This document describes the problems associated with the use of No- Path DAO messaging in RPL and a signaling changes to improve route invalidation efficiency.
- PCEP Extensions for Stitching LSPs in Hierarchical Stateful PCE Model (draft-lee-pce-lsp-stitching): Active » Replaced by draft-lee-pce-lsp-stitching-hpce
By Young Lee, Dhruv Dhody, Daniele Ceccarelli, 2017-06-23 TXT HTML PDF
Abstract: This document extends the Path Communication Element Communication Protocol (PCEP) to coordinate an end-to-end inter-domain tunnel setup over a multi-domain networks in the context of Hierarchical Stateful PCE environments. This document uses Stitching Label (SL) to stich per-domain LSPs.
- draft-madi-sidr-rp: Expired » Replaced by draft-madi-sidrops-rp
No title available; expired document? TXT HTML PDF
RFC Editor Status Changes
- ISIS Auto-Configuration (draft-ietf-isis-auto-conf): » AUTH48
By Bing Liu, Les Ginsberg, Bruno Decraene, Ian Farrer, Mikael Abrahamsson, 2017-05-08 TXT HTML PDF
Abstract: This document specifies IS-IS auto-configuration mechanisms. The key components are IS-IS System ID self-generation, duplication detection and duplication resolution. These mechanisms provide limited IS-IS functions, and so are suitable for networks where plug-and-play configuration is expected.
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
