IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Constrained Application Protocol (CoAP) Hop Limit Option (draft-boucadair-core-hop-limit)
By Mohamed Boucadair, Tirumaleswar Reddy, Jon Shallow, 2018-08-16 TXT HTML PDF
Abstract: The presence of Constrained Application Protocol (CoAP) proxies may lead to infinite forwarding loops, which is undesirable. To prevent and detect such loops, this document specifies the Hop-Limit CoAP option.
- Updates to Destination Options Processing (draft-herbert-ipv6-update-dest-ops)
By Tom Herbert, 2018-08-17 TXT HTML PDF
Abstract: This document updates the requirements for processing Destination Options in IPv6 in two ways. First, the requirement that all intermediate destinations in a Routing header must process options in a Destination header appearing before the Routing header is relaxed. Secondly, the processing of a Destination Option marked as changeable is clarified.
- Babel Cryptographic Authentification (draft-ietf-babel-hmac)
By Clara Do, Weronika Kolodziejak, Juliusz Chroboczek, 2018-08-16 TXT HTML PDF
Abstract: This document describes a cryptographic authentication mechanism for the Babel routing protocol that has provisions for replay avoidance. This document updates RFC 6126bis and obsoletes RFC 7298.
- CDN Loop Prevention (draft-ietf-httpbis-cdn-loop)
By Stephen Ludin, Mark Nottingham, Nick Sullivan, 2018-08-16 TXT HTML PDF
Abstract: This specification defines the CDN-Loop request header field for HTTP.
- Multicast Considerations over IEEE 802 Wireless Media (draft-ietf-mboned-ieee802-mcast-problems)
By Charles Perkins, Mike McBride, Dorothy Stanley, Warren Kumari, Juan Zuniga, 2018-08-17 TXT HTML PDF
Abstract: Well-known issues with multicast have prevented the deployment of multicast in 802.11 [dot11], [mc-props], [mc-prob-stmt], and other local-area wireless environments. IETF multicast experts have been meeting together to discuss these issues and provide IEEE updates. The mboned working group is chartered to receive regular reports on the current state of the deployment of multicast technology, create "practice and experience" documents that capture the experience of those who have deployed and are deploying various multicast technologies, and provide feedback to other relevant working groups. This document offers guidance on known limitations and problems with wireless multicast. Also described are various multicast enhancement features that have been specified at IETF and IEEE 802 for wireless media, as well as some operational chioces that can be taken to improve the performace of the network. Finally, some recommendations are provided about the usage and combination of these features and operational choices.
- The secret-token URI Scheme (draft-nottingham-how-did-that-get-into-the-repo)
By Mark Nottingham, 2018-08-15 TXT HTML PDF
Abstract: This document registers the "secret-token" URI scheme, to aid in the identification of authentication tokens.
Updated Drafts
- RIB YANG Data Model (draft-acee-rtgwg-yang-rib-extend)
By Acee Lindem, Yingzhen Qu, 2018-08-16 TXT HTML PDF
Abstract: The Routing Information Base (RIB) is a list of routes and their corresponding administrative data and operational state.
- Registry Mapping for the Extensible Provisioning Protocol (EPP) (draft-gould-carney-regext-registry)
By James Gould, Lin Jia, rcarney@godaddy.com, Jody Kolker, 2018-08-17 TXT HTML PDF
Abstract: This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning registry zones (e.g. top-level domains) in a Domain Name Registry. The attributes of a registry zone include the features and policies of the registry zone.
- Launch Phase Policy Extensions Mapping for the Extensible Provisioning Protocol (EPP) (draft-gould-regext-launch-policy)
By James Gould, 2018-08-17 TXT HTML PDF
Abstract: This document describes an Extensible Provisioning Protocol (EPP) extension of the Registry Mapping to define the server policy of the Launch Phase EPP extension. The server policy of the Launch Phase EPP extension includes the MAYs, SHOULDs, and options implemented by the server.
- Login Security Extension for the Extensible Provisioning Protocol (EPP) (draft-gould-regext-login-security)
By James Gould, Matthew Pozun, 2018-08-17 TXT HTML PDF
Abstract: The Extensible Provisioning Protocol (EPP) includes a client authentication scheme that is based on a user identifier and password. The structure of the password field is defined by an XML Schema data type that specifies minimum and maximum password length values, but there are no other provisions for password management other than changing the password. This document describes an EPP extension that allows longer passwords to be created and adds additional security features to the EPP login command and response.
- TLS 1.3 Extension for Certificate-based Authentication with an External Pre-Shared Key (draft-housley-tls-tls13-cert-with-extern-psk)
By Russ Housley, 2018-08-16 TXT HTML PDF
Abstract: This document specifies a TLS 1.3 extension that allows a server to authenticate with a certificate while providing an external pre- shared key (PSK) as an input to the key schedule.
- ACME TLS ALPN Challenge Extension (draft-ietf-acme-tls-alpn)
By Roland Shoemaker, 2018-08-17 TXT HTML PDF
Abstract: This document specifies a new challenge for the Automated Certificate Management Environment (ACME) protocol which allows for domain control validation using TLS.
- Updated processing of control flags for BGP VPLS (draft-ietf-bess-bgp-vpls-control-flags)
By Ravi Singh, Kireeti Kompella, Senad Palislamovic, 2018-08-17 TXT HTML PDF
Abstract: This document updates the meaning of the "control flags" fields inside the "layer2 info extended community" used for BGP-VPLS NLRI as defined in RFC4761. If approved, this document updates RFC4761.
- Service Function Chaining using Virtual Networks with BGP VPNs (draft-ietf-bess-service-chaining)
By Rex Fernando, Stuart Mackie, Dhananjaya Rao, Bruno Rijsman, Maria Napierala, Thomas Morin, 2018-08-16 TXT HTML PDF
Abstract: This document describes how service function chains (SFC) can be applied to traffic flows using routing in a virtual (overlay) network to steer traffic between service nodes. Chains can include services running in routers, on physical appliances or in virtual machines. Service chains have applicability at the subscriber edge, business edge and in multi-tenant datacenters. The routing function into SFCs and between service functions within an SFC can be performed by physical devices (routers), be virtualized inside hypervisors, or run as part of a host OS.
- BFD for VXLAN (draft-ietf-bfd-vxlan)
By Juniper Networks, Sudarsan Paragiri, Vengada Govindan, Mallik Mudigonda, Gregory Mirsky, 2018-08-18 TXT HTML PDF
Abstract: This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol in Virtual eXtensible Local Area Network (VXLAN) overlay networks.
- DNS Queries over HTTPS (DoH) (draft-ietf-doh-dns-over-https)
By Paul Hoffman, Patrick McManus, 2018-08-16 TXT HTML PDF
Abstract: This document defines a protocol for sending DNS queries and getting DNS responses over HTTPS. Each DNS query-response pair is mapped into an HTTP exchange.
- Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification (draft-ietf-dots-signal-channel)
By Tirumaleswar Reddy, Mohamed Boucadair, Prashanth Patil, Andrew Mortensen, Nik Teague, 2018-08-17 TXT HTML PDF
Abstract: This document specifies the DOTS signal channel, a protocol for signaling the need for protection against Distributed Denial-of- Service (DDoS) attacks to a server capable of enabling network traffic mitigation on behalf of the requesting client.
- LISP Generic Protocol Extension (draft-ietf-lisp-gpe)
By Fabio Maino, John Lemon, Puneet Agarwal, Darrel Lewis, Michael Smith, 2018-08-15 TXT HTML PDF
Abstract: This document describes extentions to the Locator/ID Separation Protocol (LISP) Data-Plane, via changes to the LISP header, to support multi-protocol encapsulation.
- Extensions to the Path Computation Element Communication Protocol for Enhanced Errors and Notifications (draft-ietf-pce-enhanced-errors)
By Helia Poullyau, Remi Theillaud, Julien Meuric, zhenghaomian@huawei.com, Xian Zhang, 2018-08-17 TXT HTML PDF
Abstract: This document defines new error and notification TLVs for the PCE Communication Protocol (PCEP) [RFC5440]. It identifies the possible PCEP behaviors in case of error or notification. Thus, this draft defines types of errors and how they are disclosed to other PCEs in order to support predefined PCEP behaviors.
- Dynamic Authorization Proxying in Remote Authorization Dial-In User Service Protocol (RADIUS) (draft-ietf-radext-coa-proxy)
By Alan DeKok, Jouni Korhonen, 2018-08-16 TXT HTML PDF
Abstract: RFC 5176 defines Change of Authorization (CoA) and Disconnect Message (DM) behavior for RADIUS. That document suggests that proxying these messages is possible, but gives no guidance as to how it is done. This specification updates RFC 5176 to correct that omission for scenarios where networks use Realm-based proxying as defined in RFC 7542.
- Extensible Provisioning Protocol (EPP) Organization Mapping (draft-ietf-regext-org)
By Linlin Zhou, Ning Kong, Guiqing Zhou, Jiankang Yao, James Gould, 2018-08-19 TXT HTML PDF
Abstract: This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning and management of organization objects stored in a shared central repository. Specified in Extensible Markup Language (XML), this extended mapping is applied to provide additional features required for the provisioning of organizations.
- Organization Extension for the Extensible Provisioning Protocol (EPP) (draft-ietf-regext-org-ext)
By Linlin Zhou, Ning Kong, Junkai Wei, Jiankang Yao, James Gould, 2018-08-19 TXT HTML PDF
Abstract: This document describes an extension to EPP object mappings, which is designed to support assigning an organization to any existing object (domain, host, contact) as well as any future objects.
- Push Notification with the Session Initiation Protocol (SIP) (draft-ietf-sipcore-sip-push)
By Christer Holmberg, Michael Arnold, 2018-08-17 TXT HTML PDF
Abstract: This document describes how a Push Notification Service (PNS) can be used to awake 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.
- Delegated Credentials for TLS (draft-ietf-tls-subcerts)
By Richard Barnes, Subodh Iyengar, Nick Sullivan, Eric Rescorla, 2018-08-17 TXT HTML PDF
Abstract: The organizational separation between the operator of a TLS server and the certification authority can create limitations. For example, the lifetime of certificates, how they may be used, and the algorithms they support are ultimately determined by the certification authority. This document describes a mechanism by which operators may delegate their own credentials for use in TLS, without breaking compatibility with clients that do not support this specification.
- Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity as-a-Service (draft-ietf-v6ops-transition-ipv4aas)
By Jordi Palet, Hans Liu, Masanobu Kawashima, 2018-08-16 TXT HTML PDF
Abstract: This document specifies the IPv4 service continuity requirements for an IPv6 Customer Edge (CE) router, either provided by the service provider or thru the retail market.
- Re-keying Mechanisms for Symmetric Keys (draft-irtf-cfrg-re-keying)
By Stanislav Smyshlyaev, 2018-08-17 TXT HTML PDF
Abstract: A certain maximum amount of data can be safely encrypted when encryption is performed under a single key. This amount is called "key lifetime". This specification describes a variety of methods to increase the lifetime of symmetric keys. It provides two types of re-keying mechanisms based on hash functions and on block ciphers, that can be used with modes of operations such as CTR, GCM, CBC, CFB and OMAC.
- SOCKS Protocol Version 6 (draft-olteanu-intarea-socks-6)
By Vladimir Olteanu, Dragos Niculescu, 2018-08-17 TXT HTML PDF
Abstract: The SOCKS protocol is used primarily to proxy TCP connections to arbitrary destinations via the use of a proxy server. Under the latest version of the protocol (version 5), it takes 2 RTTs (or 3, if authentication is used) before data can flow between the client and the server.
- Vectors of Trust (draft-richer-vectors-of-trust)
By Justin Richer, Leif Johansson, 2018-08-17 TXT HTML PDF
Abstract: This document defines a mechanism for describing and signaling several aspects of a digital identity transaction and its participants. These aspects are used to determine the amount of trust to be placed in that transaction.
- A Simple BGP-based Mobile Routing System for the Aeronautical Telecommunications Network (draft-templin-atn-bgp)
By Fred Templin, Greg Saccone, Gaurav Dawra, Acee Lindem, Victor Moreno, 2018-08-16 TXT HTML PDF
Abstract: The International Civil Aviation Organization (ICAO) is investigating mobile routing solutions for a worldwide Aeronautical Telecommunications Network with Internet Protocol Services (ATN/IPS). The ATN/IPS will eventually replace existing communication services with an IPv6-based service supporting pervasive Air Traffic Management (ATM) for Air Traffic Controllers (ATC), Airline Operations Controllers (AOC), and all commercial aircraft worldwide. This informational document describes a simple and extensible mobile routing service based on industry-standard BGP to address the ATN/IPS requirements.
- Use of BIER Entropy for Data Center CLOS Networks (draft-xie-bier-entropy-staged-dc-clos)
By Jingrong Xie, Xiaohu Xu, Gang Yan, Mike McBride, 2018-08-18 TXT HTML PDF
Abstract: Bit Index Explicit Replication (BIER) introduces a new multicast- specific BIER Header. BIER can be applied to the Multi Protocol Label Switching (MPLS) data plane or Non-MPLS data plane. Entropy is a technique used in BIER to support load-balancing. This document examines and describes how BIER Entropy is to be applied to Data Center CLOS networks for path selection.
Expired Drafts
- A YANG Data Model for MPLS Base (draft-ietf-mpls-base-yang)
By Tarek Saad, Kamran Raza, Rakesh Gandhi, Xufeng Liu, Vishnu Beeram, 2018-02-15 TXT HTML PDF
Abstract: This document contains a specification of the the MPLS base YANG model. The MPLS base YANG module serves as a base framework for configuring and managing an MPLS switching subsystem. It is expected that other MPLS technology YANG models (e.g. MPLS LSP Static, LDP or RSVP-TE models) will augment the MPLS base YANG model.
- A YANG Data Model for MPLS Static LSPs (draft-ietf-mpls-static-yang)
By Tarek Saad, Kamran Raza, Rakesh Gandhi, Xufeng Liu, Vishnu Beeram, 2018-02-15 TXT HTML PDF
Abstract: This document contains the specification for the MPLS Static Label Switched Paths (LSPs) YANG model. The model allows for the provisioning of static LSP(s) on LER(s) and LSR(s) devices along a LSP path without the dependency on any signaling protocol. The MPLS Static LSP model augments the MPLS base YANG model with specific data to configure and manage MPLS Static LSP(s).
- draft-ietf-sfc-nsh-dc-allocation
No title available; expired document? TXT HTML PDF
- draft-ietf-sipcore-reason-q850-loc
No title available; expired document? TXT HTML PDF
- draft-levine-dkim-conditional
No title available; expired document? TXT HTML PDF
- BFD for Multipoint Networks over Point-to-Multi-Point MPLS LSP (draft-mirsky-mpls-p2mp-bfd)
By Gregory Mirsky, 2018-02-15 TXT HTML PDF
Abstract: This document describes procedures for using Bidirectional Forwarding Detection (BFD) for multipoint networks to detect data plane failures in Multiprotocol Label Switching (MPLS) point-to-multipoint (p2mp) Label Switched Paths (LSPs). It also describes applicability of out- band solutions to bootstrap a BFD session in this environment.
- draft-wang-netmod-module-revision-management
No title available; expired document? TXT HTML PDF
- PCEP Extension for Native IP Network (draft-wang-pce-pcep-extension-native-ip)
By Aijun Wang, Boris Khasanov, Sudhir Cheruathur, Chun Zhu, 2018-02-13 TXT HTML PDF
Abstract: This document defines the PCEP extension for CCDR application in Native IP network. The scenario and architecture of CCDR in native IP is described in [draft-ietf-teas-native-ip-scenarios] and [draft- ietf-teas-pce-native-ip]. This draft describes the key information that is transferred between PCE and PCC to accomplish the end2end traffic assurance in Native IP network under central control mode.
- BIER Algorithms (draft-zzhang-bier-algorithm)
By Zhaohui Zhang, Andrew Dolganow, Tony Przygienda, 2018-02-15 TXT HTML PDF
Abstract: This document specifies signaling and procedures for non-SPF BIER tree computation covering several practical use cases discussed in deployment scenarios.
|
Drafts Sent to IESG
IESG Progress
- Framework for EVPN Designated Forwarder Election Extensibility (draft-ietf-bess-evpn-df-election-framework): AD Evaluation » ::Revised I-D Needed
By Jorge Rabadan, satyamoh@cisco.com, Ali Sajassi, John Drake, Kiran Nagaraj, Senthil Sathappan, 2018-05-24 TXT HTML PDF
Abstract: The Designated Forwarder (DF) in EVPN networks is the PE responsible for sending broadcast, unknown unicast and multicast (BUM) traffic to a multi-homed CE, on a given VLAN on a particular Ethernet Segment (ES). The DF is selected out of a list of candidate PEs that advertise the same Ethernet Segment Identifier (ESI) to the EVPN network. By default, EVPN uses a DF Election algorithm referred to as "Service Carving" and it is based on a modulus function (V mod N) that takes the number of PEs in the ES (N) and the VLAN value (V) as input. This default DF Election algorithm has some inefficiencies that this document addresses by defining a new DF Election algorithm and a capability to influence the DF Election result for a VLAN, depending on the state of the associated Attachment Circuit (AC). In addition, this document creates a registry with IANA, for future DF Election Algorithms and Capabilities. It also presents a formal definition and clarification of the DF Election Finite State Machine.
- (PBB-)EVPN Seamless Integration with (PBB-)VPLS (draft-ietf-bess-evpn-vpls-seamless-integ): AD Evaluation » ::Revised I-D Needed
By Ali Sajassi, Samer Salam, Nick Regno, Jorge Rabadan, 2018-04-25 TXT HTML PDF
Abstract: This draft specifies procedures for backward compatibility of the (PBB-)EVPN solution with (PBB-)VPLS and provides mechanisms for seamless integration of the two technologies in the same MPLS/IP network on a per-VPN-instance basis. Implementation of this draft enables service providers to introduce (PBB-)EVPN PEs in their brown- field deployments of (PBB-)VPLS networks.
- L2L3 VPN Multicast MIB (draft-ietf-bess-l2l3-vpn-mcast-mib): Publication Requested » Last Call Requested
By Zhaohui Zhang, Hiroshi Tsunoda, 2018-08-10 TXT HTML PDF
Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes two MIB modules which will be used by other MIB modules for monitoring and/or configuring Layer 2 and Layer 3 Virtual Private Networks that support multicast.
- BGP/MPLS Layer 3 VPN Multicast Management Information Base (draft-ietf-bess-mvpn-mib): Publication Requested » Last Call Requested
By Hiroshi Tsunoda, 2018-08-10 TXT HTML PDF
Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor Multicast communication over IP Virtual Private Networks (VPNs) supported by MultiProtocol Label Switching/Border Gateway Protcol (MPLS/BGP) on a Provider Edge router.
- Too Many Requests Response Code for the Constrained Application Protocol (draft-ietf-core-too-many-reqs): AD Evaluation » ::External Party
By Ari Keranen, 2018-07-24 TXT HTML PDF
Abstract: A Constrained Application Protocol (CoAP) server can experience temporary overload because one or more clients are sending requests to the server at a higher rate than the server is capable or willing to handle. This document defines a new CoAP Response Code for a server to indicate that a client should reduce the rate of requests.
- DNS Queries over HTTPS (DoH) (draft-ietf-doh-dns-over-https): IESG Evaluation » Approved-announcement to be sent
By Paul Hoffman, Patrick McManus, 2018-08-16 TXT HTML PDF
Abstract: This document defines a protocol for sending DNS queries and getting DNS responses over HTTPS. Each DNS query-response pair is mapped into an HTTP exchange.
- Internet Message Access Protocol (IMAP) - SAVEDATE Extension (draft-ietf-extra-imap-savedate): Publication Requested » In Last Call
By Stephan Bosch, 2018-05-04 TXT HTML PDF
Abstract: This document adds a new capability called "SAVEDATE" to the Internet Message Access Protocol (IMAP). It defines a new IMAP message attribute called 'save date' that, unlike the existing 'internal date' attribute, always indicates the moment at which the message was saved in its current mailbox. The SAVEDATE capability extends the FETCH command with the means to retrieve the save date attribute and it extends the SEARCH command to allow using that attribute in searching criteria.
- Marking SIP Messages to be Logged (draft-ietf-insipid-logme-marking): IESG Evaluation » ::Revised I-D Needed
By Peter Dawes, Chidambaram Arunachalam, 2018-07-17 TXT HTML PDF
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.
- Locator/ID Separation Protocol (LISP) Control-Plane (draft-ietf-lisp-rfc6833bis): Publication Requested » In Last Call
By Vince Fuller, Dino Farinacci, Albert Cabellos-Aparicio, 2018-07-26 TXT HTML PDF
Abstract: This document describes the Control-Plane and Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two new types of LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provides a simplified "front end" for one or more Endpoint ID to Routing Locator mapping databases.
- Dynamic Authorization Proxying in Remote Authorization Dial-In User Service Protocol (RADIUS) (draft-ietf-radext-coa-proxy): IESG Evaluation » ::AD Followup
By Alan DeKok, Jouni Korhonen, 2018-08-16 TXT HTML PDF
Abstract: RFC 5176 defines Change of Authorization (CoA) and Disconnect Message (DM) behavior for RADIUS. That document suggests that proxying these messages is possible, but gives no guidance as to how it is done. This specification updates RFC 5176 to correct that omission for scenarios where networks use Realm-based proxying as defined in RFC 7542.
- Allocation Token Extension for the Extensible Provisioning Protocol (EPP) (draft-ietf-regext-allocation-token): IESG Evaluation » ::Revised I-D Needed
By James Gould, Kal Feher, 2018-08-03 TXT HTML PDF
Abstract: This document describes an Extensible Provisioning Protocol (EPP) extension for including an Allocation Token in "query" and "transform" commands. The Allocation Token is used as a credential that authorizes a client to request the allocation of a specific object from the server, using one of the EPP transform commands including create and transfer.
- Extensible Provisioning Protocol (EPP) Organization Mapping (draft-ietf-regext-org): AD Evaluation::Revised I-D Needed » ::AD Followup
By Linlin Zhou, Ning Kong, Guiqing Zhou, Jiankang Yao, James Gould, 2018-08-19 TXT HTML PDF
Abstract: This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning and management of organization objects stored in a shared central repository. Specified in Extensible Markup Language (XML), this extended mapping is applied to provide additional features required for the provisioning of organizations.
- Organization Extension for the Extensible Provisioning Protocol (EPP) (draft-ietf-regext-org-ext): AD Evaluation::Revised I-D Needed » ::AD Followup
By Linlin Zhou, Ning Kong, Junkai Wei, Jiankang Yao, James Gould, 2018-08-19 TXT HTML PDF
Abstract: This document describes an extension to EPP object mappings, which is designed to support assigning an organization to any existing object (domain, host, contact) as well as any future objects.
- BGP RPKI-Based Origin Validation Clarifications (draft-ietf-sidrops-ov-clarify): IESG Evaluation » Approved-announcement to be sent
By Randy Bush, 2018-08-10 TXT HTML PDF
Abstract: Deployment of Resource Public Key Infrastructure (RPKI) based BGP origin validation is hampered by, among other things, vendor mis- implementations in two critical areas: which routes are validated and whether policy is applied when not specified by configuration. This document is meant to clarify possible misunderstandings causing those mis-implementations; and thus updates RFC6811 by clarifying that all prefixes should have their validation state set, and that policy must not be applied without operator configuration.
- Vectors of Trust (draft-richer-vectors-of-trust): IESG Evaluation::AD Followup » Approved-announcement sent
By Justin Richer, Leif Johansson, 2018-08-17 TXT HTML PDF
Abstract: This document defines a mechanism for describing and signaling several aspects of a digital identity transaction and its participants. These aspects are used to determine the amount of trust to be placed in that transaction.
Drafts Sent to RFC Editor
- Registration Extensions for 6LoWPAN Neighbor Discovery (draft-ietf-6lo-rfc6775-update): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Pascal Thubert, Erik Nordmark, Samita Chakrabarti, Charles Perkins, 2018-06-19 TXT HTML PDF
Abstract: This specification updates RFC 6775 - 6LoWPAN Neighbor Discovery, to clarify the role of the protocol as a registration technique, simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the registration capabilities and mobility detection for different network topologies including the Routing Registrars performing routing for host routes and/or proxy Neighbor Discovery in a low power network.
- IPv6 Node Requirements (draft-ietf-6man-rfc6434-bis): IESG Evaluation::AD Followup » RFC Ed Queue
By Tim Chown, John Loughney, Timothy Winters, 2018-07-16 TXT HTML PDF
Abstract: This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments.
- 6TiSCH Operation Sublayer Protocol (6P) (draft-ietf-6tisch-6top-protocol): IESG Evaluation::AD Followup » RFC Ed Queue
By Qin Wang, Xavier Vilajosana, Thomas Watteyne, 2018-06-20 TXT HTML PDF
Abstract: This document defines the IPv6 over the TSCH mode of IEEE 802.15.4e (6TiSCH) Operation Sublayer (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 layer terminates the 6top Protocol defined in this document, and runs one or more 6top Scheduling Function(s). A 6top Scheduling Function (SF) decides when to add/delete cells, and triggers 6P Transactions. This document lists the requirements for an SF, but leaves the definition of SFs out of scope.
Other Status Changes
- draft-cdn-loop-prevention: Active » Replaced by draft-ietf-httpbis-cdn-loop
No title available; expired document? TXT HTML PDF
- draft-do-babel-hmac: Active » Replaced by draft-ietf-babel-hmac
No title available; expired document? TXT HTML PDF
RFC Editor Status Changes
- Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis (draft-ietf-dhc-rfc3315bis): » AUTH48
By Tomek Mrugalski, Marcin Siodelski, Bernie Volz, Andrew Yourtchenko, Michael Richardson, Sheng Jiang, Ted Lemon, Timothy Winters, 2018-04-07 TXT HTML PDF
Abstract: This document describes the Dynamic Host Configuration Protocol for IPv6 (DHCPv6): an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly, or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 prefixes. DHCPv6 can operate either in place of or in addition to stateless address autoconfiguration (SLAAC).
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
