Request For Comments storage

Documents by J. Halpern

1996, RFC1923: RIPv1 Applicability Statement for Historic Status

1998, RFC2225: Classical IP and ARP over ATM

1998, RFC2334: Server Cache Synchronization Protocol (SCSP)

2002, RFC3248: A Delay Bound alternative revision of RFC 2598

2008, RFC5377: Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents

2009, RFC5744: Procedures for Rights Handling in the RFC Independent Submission Stream

2010, RFC5810: Forwarding and Control Element Separation (ForCES) Protocol Specification

2010, RFC5812: Forwarding and Control Element Separation (ForCES) Forwarding Element Model

2012, RFC6635: RFC Editor Model (Version 2)

2012, RFC6730: Requirements for IETF Nominations Committee Tools

2013, RFC6956: Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) Library

2013, RFC6959: Source Address Validation Improvement (SAVI) Threat Scope

2014, RFC7409: Forwarding and Control Element Separation (ForCES) Packet Parallelization

2015, RFC7665: Service Function Chaining (SFC) Architecture

2016, RFC7841: RFC Streams, Headers, and Boilerplates

2016, RFC7921: An Architecture for the Interface to the Routing System

2017, RFC8074: Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods Scenario

2017, RFC8241: Interface to the Routing System (I2RS) Security-Related Requirements

2019, RFC8596: MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)

2020, RFC8721: Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents

2020, RFC8728: RFC Editor Model (Version 2)

2020, RFC8789: IETF Stream Documents Require IETF Rough Consensus

2022, RFC9296: ifStackTable for the Point-to-Point (P2P) Interface over a LAN Type: Definition and Examples