https://tools.ietf.org/html/ New Current Internet Drafts (All Categories) en Tue, 03 Jan 2017 14:21:52 GMT 1 hourly 1970-01-01T00:30+00:00 60 henrik@levkowetz.com http://www.interglacial.com/rss/about.html https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-10 2017-01-03, rev -10: This document defines an abstract (generic) YANG data model for network/service topologies and inventories. The model serves as a base model which is augmented with technology-specific details in other, more specific topology and inventory models. https://tools.ietf.org/html/draft-ietf-i2rs-yang-l3-topology-07 2017-01-03, rev -07: This document defines a YANG data model for layer 3 network topologies. https://tools.ietf.org/html/draft-ietf-clue-protocol-11 2017-01-02, rev -11: The CLUE protocol is an application protocol conceived for the description and negotiation of a telepresence session. The design of the CLUE protocol takes into account the requirements and the framework defined within the IETF CLUE working group. A companion document delves into CLUE signaling details, as well as on the SIP/ SDP session establishment phase. CLUE messages flow over the CLUE data channel, based on reliable and ordered SCTP over DTLS transport. Message details, together with the behavior of CLUE Participants acting as Media Providers and/or Media Consumers, are herein discussed. https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-09 2017-01-02, rev -09: This document specifies how to establish secure connection-oriented media transport sessions over the Transport Layer Security (TLS) protocol using the Session Description Protocol (SDP). It defines a new SDP protocol identifier, 'TCP/TLS'. It also defines the syntax and semantics for an SDP 'fingerprint' attribute that identifies the certificate that will be presented for the TLS session. This mechanism allows media transport over TLS connections to be established securely, so long as the integrity of session descriptions is assured. https://tools.ietf.org/html/draft-ietf-tls-iana-registry-updates-00 2017-01-02, rev -00: This document changes the IANA registry policy for a number of registries related to DTLS and TLS, renames some of the registries for consistency, and adds notes to many of the registries. As a result, this document updates many RFCs (see updates header). https://tools.ietf.org/html/draft-ietf-spring-sr-oam-requirement-03 2017-01-02, rev -03: This document describes a list of functional requirement for OAM in Segment Routing (SR) based network. https://tools.ietf.org/html/draft-ietf-openpgp-rfc4880bis-01 2017-01-02, rev -01: { Work in progress to update the OpenPGP specification from RFC4880 } https://tools.ietf.org/html/draft-harkins-pkex-03 2017-01-02, rev -03: This memo describes a password-authenticated protocol to allow two devices to exchange "raw" (uncertified) public keys and establish trust that the keys belong to their respective identities. https://tools.ietf.org/html/draft-ietf-savi-mix-15 2017-01-02, rev -15: In networks that use multiple techniques for address assignment, the spoofing of addresses assigned by each technique can be prevented using the appropriate Source Address Validation Improvement (SAVI) methods. This document reviews how multiple SAVI methods can coexist in a single SAVI device and collisions are resolved when the same binding entry is discovered by two or more methods. https://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-19 2017-01-02, rev -19: DHCPv6 includes no deployable security mechanism that can protect end-to-end communication between DHCP clients and servers. This document describes a mechanism for using public key cryptography to provide such security. The mechanism provides encryption in all cases, and can be used for authentication based on pre-sharing of authorized certificates. https://tools.ietf.org/html/draft-ietf-pce-pceps-11 2017-01-02, rev -11: The Path Computation Element Communication Protocol (PCEP) defines the mechanisms for the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or among PCEs. This document describe the usage of Transport Layer Security (TLS) to enhance PCEP security, hence the PCEPS acronym proposed for it. The additional security mechanisms are provided by the transport protocol supporting PCEP, and therefore they do not affect the flexibility and extensibility of PCEP. https://tools.ietf.org/html/draft-aranda-sfc-dp-mobile-03 2017-01-02, rev -03: The evolution of the network towards 5G implies a challenge for the infrastructure. The targeted services and the full deployment of virtualization in all segments of the network will be possible and necessary to provide some traffic-specific services near the next generation base stations where the radio is processed. Thus, service function chains that currently reside in the infrastructure of the Network operator (like, e.g. the Expeded Packet Gateway(EPG)) will be extended to the radio access network (RAN). https://tools.ietf.org/html/draft-xu-mptcp-congestion-control-05 2017-01-01, rev -05: This document describes the mechanism of wVegas (weighted Vegas), which is a delay-based congestion control for MPTCP. The current congestion control algorithm of MPTCP, LIA, achieves only course- grained load balancing, since it is based on packet loss event. On the contrary, wVegas adopts packet queuing delay as congestion signals, thus achieving fine-grained load balancing. Compared with loss-based algorithms, wVegas is more sensitive to the changes of network congestion and thus achieves more timely traffic shifting and quicker convergence. WVegas has been implemented in the Linux Kernel and is part of the UCLouvain's MPTCP implementation now. https://tools.ietf.org/html/draft-wilde-json-seq-suffix-03 2016-12-31, rev -03: Structured Syntax Suffixes for media types allow other media types to build on them and make it explicit that they are built on an existing media type as their foundation. This specification defines and registers "+json-seq" as a structured syntax suffix for JSON Text Sequences. https://tools.ietf.org/html/draft-wu-opsawg-service-model-explained-04 2016-12-31, rev -04: The IETF has produced a considerable number of data models in the YANG modelling language. The majority of these are used to model devices and they allow access for configuration and to read operational status. https://tools.ietf.org/html/draft-ietf-urnbis-rfc2141bis-urn-19 2016-12-31, rev -19: A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier. With regard to URN syntax, this document defines the canonical syntax for URNs (in a way that is consistent with URI syntax), specifies methods for determining URN- equivalence, and discusses URI conformance. With regard to URN namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and describes procedures for registering namespace identifiers with the Internet Assigned Numbers Authority (IANA). This document obsoletes both RFC 2141 and RFC 3406. https://tools.ietf.org/html/draft-jones-cose-rsa-01 2016-12-31, rev -01: The CBOR Object Signing and Encryption (COSE) specification defines cryptographic message encodings using Concise Binary Object Representation (CBOR). This specification defines algorithm encodings and representations enabling RSA algorithms to be used for COSE messages. https://tools.ietf.org/html/draft-ietf-sidr-bgpsec-pki-profiles-19 2016-12-30, rev -19: This document defines a standard profile for X.509 certificates used to enable validation of Autonomous System (AS) paths in the Border Gateway Protocol (BGP), as part of an extension to that protocol known as BGPsec. BGP is the standard for inter-domain routing in the Internet; it is the "glue" that holds the Internet together. BGPsec is being developed as one component of a solution that addresses the requirement to provide security for BGP. The goal of BGPsec is to provide full AS path validation based on the use of strong cryptographic primitives. The end-entity (EE) certificates specified by this profile are issued (to routers within an Autonomous System). Each of these certificates is issued under a Resource Public Key Infrastructure (RPKI) Certification Authority (CA) certificate. These CA certificates and EE certificates both contain the AS Identifier Delegation extension. An EE certificate of this type asserts that the router(s) holding the corresponding private key are authorized to emit secure route advertisements on behalf of the AS(es) specified in the certificate. This document also profiles the format of certification requests, and specifies Relying Party (RP) certificate path validation procedures for these EE certificates. This document extends the RPKI; therefore, this documents updates the RPKI Resource Certificates Profile (RFC 6487). https://tools.ietf.org/html/draft-ietf-bmwg-dcbench-methodology-03 2016-12-30, rev -03: The purpose of this informational document is to establish test and evaluation methodology and measurement techniques for physical network equipment in the data center. https://tools.ietf.org/html/draft-ietf-bmwg-dcbench-terminology-06 2016-12-30, rev -06: The purpose of this informational document is to establish definitions, discussion and measurement techniques for data center benchmarking. Also, it is to introduce new terminologies applicable to data center performance evaluations. The purpose of this document is not to define the test methodology, but rather establish the important concepts when one is interested in benchmarking network switches and routers in the data center. https://tools.ietf.org/html/draft-turner-est-extensions-07 2016-12-30, rev -07: The EST (Enrollment over Secure Transport) protocol defined a Well- Known URI (Uniform Resource Identifier): /.well-known/est. EST also defined several path components that clients use for PKI (Public Key Infrastructure) services, namely certificate enrollment (e.g., /simpleenroll). In some sense, the services provided by the path components can be thought of as PKI management-related packages. There are additional PKI-related packages a client might need as well as other security-related packages, such as firmware, trust anchors, and symmetric, asymmetric, and encrypted keys. This document also specifies the PAL (Package Availability List), which is an XML (Extensible Markup Language) file or JSON (Javascript Object Notation) object that clients use to retrieve packages available and authorized for them. This document extends the EST server path components to provide these additional services. https://tools.ietf.org/html/draft-krishnan-opsawg-in-band-pro-sla-03 2016-12-30, rev -03: The goal of in-band telemetry is to drive per packet, per hop real- time monitoring for the infrastructure towards achieving a programmable proactive SLA monitoring framework. Some of the key aspects from a switch/NIC perspective are - ingress/egress timestamp (latency), queue depth, bandwidth etc. Some of the key aspects from a server perspective are - cache/memory statistics etc. This document summarizes the current work in the industry in this area and identifies key requirements for a comprehensive solution. Towards addressing the requirements, this document describes uses cases and defines reusable monitoring packet formats across all layers in the OAM hierarchy. https://tools.ietf.org/html/draft-winterbottom-dispatch-locparam-02 2016-12-30, rev -02: There are some circumstances where a geolocation header field may contain more than one location value. Knowing the identity of the node adding the location value allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the location values. https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-20 2016-12-30, rev -20: The Stream Control Transmission Protocol (SCTP) is a transport protocol used to establish associations between two endpoints. draft-ietf-tsvwg-sctp-dtls-encaps-09 specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol, referred to as SCTP-over-DTLS. https://tools.ietf.org/html/draft-fan-yang-mac-00 2016-12-29, rev -00: This memo proposes a yang model for MAC management. https://tools.ietf.org/html/draft-iab-ccg-appoint-process-02 2016-12-29, rev -02: This document outlines the procedures by which the IETF makes appointments to the Community Coordination Group (CCG), which provides advice and guidance to the IETF Trust in matters related to the IANA Trademarks and the IANA domain names. https://tools.ietf.org/html/draft-ietf-trill-centralized-replication-08 2016-12-29, rev -08: In TRILL active-active access, an RPF check failure issue may occur when using the pseudo-nickname mechanism specified in RFC 7781. This draft describes a solution to resolve this RPF check failure issue through centralized replication. All ingress RBridges send BUM (Broadcast, Unknown unicast and Mutlicast) traffic to a centralized node with unicast TRILL encapsulation. When the centralized node receives the BUM traffic, it decapsulates the packets and forwards them to their destination RBridges using a distribution tree established as per TRILL base protocol RFC 6325. To avoid RPF check failure on a RBridge sitting between the ingress RBridge and the centralized replication node, some change in the RPF calculation algorithm is required. RPF checks on each RBridge should be calculated as if the centralized node was the ingress RBridge, instead of being calculated using the actual ingress RBridge. https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-24 2016-12-29, rev -24: This document describes version 2.0 of the Certificate Transparency (CT) protocol for publicly logging the existence of Transport Layer Security (TLS) server certificates as they are issued or observed, in a manner that allows anyone to audit certification authority (CA) activity and notice the issuance of suspect certificates as well as to audit the certificate logs themselves. The intent is that eventually clients would refuse to honor certificates that do not appear in a log, effectively forcing CAs to add all issued certificates to the logs. https://tools.ietf.org/html/draft-ietf-idr-deprecate-30-31-129-02 2016-12-29, rev -02: This document requests IANA to mark BGP path attribute values 30, 31, 129, 241, 242, and 243 as "deprecated". https://tools.ietf.org/html/draft-ietf-idr-flowspec-l2vpn-05 2016-12-29, rev -05: This document defines BGP flow-spec extension for Ethernet traffic filtering in L2 VPN network. SAFI=134 in [RFC5575] is redefined for dissemination traffic filtering information in an L2VPN environment. A new subset of component types and extended community also are defined. https://tools.ietf.org/html/draft-chen-teas-rsvp-tts-01 2016-12-29, rev -01: This document specifies extensions to RSVP-TE for creating and maintaining a Traffic Engineering (TE) Label Switched Path (LSP) in a time interval or a sequence of time intervals. https://tools.ietf.org/html/draft-chen-ospf-tts-01 2016-12-29, rev -01: This document specifies extensions to OSPF for distributing Traffic Engineering (TE) information on a link in a sequence of time intervals. https://tools.ietf.org/html/draft-chen-pce-tts-05 2016-12-29, rev -05: For existing MPLS LSP tunnel services, it is hard for LSP tunnels to be booked in advance. In addition, once an LSP tunnel is set up, it is assumed to consume a certain amount of resources such as link bandwidth forever. https://tools.ietf.org/html/draft-ietf-mtgvenue-iaoc-venue-selection-process-04 2016-12-29, rev -04: The IAOC has responsibility for arranging IETF plenary meeting Venue selection and operation. This document details the IETF's Meeting Venue Selection Process from the perspective of its goals, criteria and thought processes. It points to additional process documents on the IAOC Web Site that go into further detail and are subject to change with experience. https://tools.ietf.org/html/draft-ietf-idr-bgp-ipv6-rt-constrain-10 2016-12-29, rev -10: The current route target distribution specification as described in [RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes. The IPv6 specific Route Target extended community is defined in [RFC 5701] as length of 20 bytes. Since the current specification only supports prefixes of maximum length of 12 bytes, the lack of an IPv6 specific Route Target reachability information may be a problem when an operator wants to use this application in a pure IPv6 environment. This document defines an extension that allows BGP to exchange longer length IPv6 Route Target prefixes. https://tools.ietf.org/html/draft-xu-pce-sr-sfc-04 2016-12-29, rev -04: Source Packet Routing in Networking (SPRING) WG is developing an MPLS source routing mechanism. This MPLS source routing mechanism can be leveraged to realize the service path layer functionality of the service function chaining (i.e., steering the selected traffic through a particular service function path) by encoding the service function path information as an MPLS label stack. This document describes extensions to the Path Computation Element Protocol (PCEP) that allow a PCE to compute and instantiate service function paths in the MPLS source routing based service function chaining context. The extensions specified in this document are applicable to both the stateless PCE model and the stateful PCE model. https://tools.ietf.org/html/draft-cuellar-ace-pat-priv-enhanced-authz-tokens-04 2016-12-29, rev -04: This specification defines PAT, "Privacy-Enhanced-Authorization- Tokens" or "Pseudonym-based Authorization Tokens", a protocol and a token construction procedure for client authorization in a constrained environment. https://tools.ietf.org/html/draft-ietf-rtgwg-rlfa-node-protection-10 2016-12-29, rev -10: The loop-free alternates computed following the current Remote-LFA specification guarantees only link-protection. The resulting Remote- LFA nexthops (also called PQ-nodes), may not guarantee node- protection for all destinations being protected by it. https://tools.ietf.org/html/draft-ietf-sidrops-lta-use-cases-00 2016-12-29, rev -00: There are a number of critical circumstances where a localized routing domain needs to augment or modify its view of the Global RPKI. This document attempts to outline a few of them. https://tools.ietf.org/html/draft-freytag-lager-variant-rules-02 2016-12-29, rev -02: This document gives guidance on designing well-behaved Label Generation Rulesets (LGRs) that support variant labels. Typical examples of labels and LGRs are IDNs and zone registration policies defining permissible IDN labels. Variant labels are labels that are either visually or semantically indistinguishable from an applied for label and are typically delegated together with the applied-for label, or permanently reserved. While [RFC7940] defines the syntactical requirements for specifying the label generation rules for variant labels, additional considerations apply that ensure that the label generation rules are consistent and well-behaved in the presence of variants. https://tools.ietf.org/html/draft-fan-bess-pm-bgp-00 2016-12-28, rev -00: This document describes a new VT address family in BGP to exchange information required for apply performance monitoring in MPLS/BGP VPN, as described in [I-D.dong-l3vpn-pm-framework]. https://tools.ietf.org/html/draft-ietf-trill-directory-assisted-encap-04 2016-12-28, rev -04: This draft describes how data center networks can benefit from non- RBridge nodes performing TRILL encapsulation with assistance from a directory service. https://tools.ietf.org/html/draft-yang-sidr-fra-01 2016-12-28, rev -01: This draft proposes Fast Route Attestation (FRA), an efficient mechanism for securing AS paths and preventing prefix hijacking by signing critical AS path segments (i.e., adjacent AS triples). FRA can achieve similar level of security as S-BGP/BGPSec, but with much higher efficiency. https://tools.ietf.org/html/draft-wang-core-opcua-transmition-requirements-00 2016-12-28, rev -00: Industrial Internet of Things is an attractive application area for Constrained Application Protocol (CoAP). OPC Unified Architecture (OPC UA) defines a semantic-based information model for industrial control system that can satisfy the requirements of Industry 4.0 based on semantic information exchange. This document analyses requirements for OPC UA transmission over CoAP. https://tools.ietf.org/html/draft-eastlake-trill-group-keying-01 2016-12-28, rev -01: This document specifies a general group keying protocol. It also provides use profiles for the application of this group keying protocol to multi-destination TRILL Extended RBridge Channel message security and TRILL over IP packet security. https://tools.ietf.org/html/draft-qin-teas-sl-rsvp-00 2016-12-27, rev -00: RSVP takes a "soft state" scheme to manage the reservation states in routers and hosts, the soft states are created and periodically refreshed by Path and Resv messages. Soft state scheme gives a simple way to maintain the state synchonization between neighbors, but also introduces scalability issue. This document provides a framework that describes and discusses the architecture for stateless RSVP (SL-RSVP), which disabled the soft-state scheme to improve the protocol scalability and the other processes of RSVP are kept. This document does not describe specific protocols or protocol extensions needed to realize this architecture. https://tools.ietf.org/html/draft-nishizuka-dots-inter-domain-mechanism-02 2016-12-27, rev -02: As DDoS attacks evolve rapidly in the aspect of volume and sophistication, cooperation among operators has become very necessary because it gives us quicker and more sophisticated protection to cope with the varius DDoS attacks. This document describes possible mechanisms which implement the cooperative inter-organization DDoS protection by DOTS protocol. The described data models are intended to cover intra-organization and inter-organization solutions. https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-05 2016-12-27, rev -05: This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name and Issuer Alternate Name extension that allows a certificate subject to be associated with an Internationalized Email Address. https://tools.ietf.org/html/draft-song-mptcp-owl-01 2016-12-27, rev -01: This document discusses the One Way Latency (OWL) utilization for enhancing multipath TCP (MPTCP) transmission, which is a potential and beneficial technology in MPTCP Working Group (WG). Several representative usages of OWL, such as retransmission policy, crucial data scheduling, are analyzed. Two kind s of OWL measurement approaches are also provided and compared. We believe that more explorations related with OWL will be important for MPTCP. https://tools.ietf.org/html/draft-dhody-pce-stateful-pce-lspdb-realtime-sync-01 2016-12-27, rev -01: The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. https://tools.ietf.org/html/draft-ietf-dmarc-arc-usage-01 2016-12-27, rev -01: The Authentication Received Chain (ARC) provides a means to preserve email authentication results and verify the identity of email message handlers, each of which participates by inserting certain header fields before passing the message on. But the specification does not indicate how intermediaries and receivers should interpret or utilize ARC. This document will provide guidance in these areas. https://tools.ietf.org/html/draft-sheffer-ietf-rfc-annotations-01 2016-12-27, rev -01: RFCs were initially intended as, literally, requests for comments. Since then, they have turned into standards documents, with a peculiar process to report errors and a highly onerous process to actually have the RFC modified/republished. Non-IETF participants are typically unaware of any way to provide feedback to published RFCs, other than direct email to the listed authors. This is very different from the way many web specifications are developed today and arguably leads to the value of published RFCs diminishing over time. This document proposes an experiment to remedy this situation through the deployment of web annotations. https://tools.ietf.org/html/draft-ietf-sacm-requirements-15 2016-12-27, rev -15: This document defines the scope and set of requirements for the Secure Automation and Continuous Monitoring (SACM) architecture, data model and transport protocols. The requirements and scope are based on the agreed upon use cases. https://tools.ietf.org/html/draft-dhody-pce-stateful-pce-interdomain-03 2016-12-27, rev -03: A stateful Path Computation Element (PCE) maintains information about Label Switched Path (LSP) characteristics and resource usage within a network in order to provide traffic engineering path calculations for its associated Path Computation Clients (PCCs). Furthermore, PCEs are used to compute shortest constrained Traffic Engineering Label Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks across multiple domains. https://tools.ietf.org/html/draft-meyer-lisp-mn-16 2016-12-26, rev -16: This document describes how a lightweight version of LISP's ITR/ETR functionality can be used to provide seamless mobility to a mobile node. The LISP Mobile Node design described in this document uses standard LISP functionality to provide scalable mobility for LISP mobile nodes. https://tools.ietf.org/html/draft-xu-mpls-payload-protocol-identifier-02 2016-12-26, rev -02: The MPLS label stack has no explicit protocol identifier field to indicate the protocol type of the MPLS payload. This document proposes a mechanism for containing a protocol identifier field within the MPLS packet, which is useful for any new encapsulation header which may need to be encapsulated with an MPLS header. https://tools.ietf.org/html/draft-deng-chinese-names-05 2016-12-26, rev -05: This document gives general rules for how to pronounce Mandarin Chinese names in conversation, and how to determine which name is someone's surname. It also covers some other related topics about Chinese names. The intent is to allow IETF participants who are not familiar with Chinese to communicate better with Chinese participants. https://tools.ietf.org/html/draft-elie-nntp-tls-recommendations-03 2016-12-26, rev -03: This document provides recommendations for improving the security of the Network News Transfer Protocol (NNTP) when using Transport Layer Security (TLS). It modernizes the NNTP usage of TLS to be consistent with TLS best current practices. If approved, this document updates RFC 4642. https://tools.ietf.org/html/draft-chen-nvo3-vxlan-yang-04 2016-12-26, rev -04: This document defines a YANG data model for VxLAN protocol. https://tools.ietf.org/html/draft-mwdt-ccamp-mw-yang-01 2016-12-25, rev -01: This document defines a YANG data model in order to control and manage the radio link interfaces, and the connectivity to packet (typically Ethernet) interfaces in a microwave/millimeter wave node.