Skip to main content

RFC 4100–4199

98 RFCs from RFC 4100 to RFC 4199, listed by number.

  1. RFC 4101June 2005
  2. RFC 4102Registration of the text/red MIME Sub-Type
  3. RFC 4103RTP Payload for Text Conversation
  4. RFC 4104Policy Core Extension Lightweight Directory Access Protocol Schema (PCELS)
  5. RFC 4105Requirements for Inter-Area MPLS Traffic Engineering
  6. RFC 4106The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)
  7. RFC 4107BCP: 107 R. Housley
  8. RFC 4108Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages
  9. RFC 4109Algorithms for Internet Key Exchange version 1 (IKEv1)
  10. RFC 4110NTT Corporation
  11. RFC 4111Security Framework for
  12. RFC 4112Electronic Commerce Modeling Language (ECML) Version 2 Specification
  13. RFC 4113Management Information Base for the User Datagram Protocol (UDP)
  14. RFC 4114E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)
  15. RFC 4115July 2005
  16. RFC 4116Netnod Internet Exchange
  17. RFC 4117Brooktrout
  18. RFC 4118UCLA
  19. RFC 4119A Presence-based GEOPRIV Location Object Format
  20. RFC 4120The Kerberos Network Authentication Service (V5)
  21. RFC 4121The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2
  22. RFC 4122A Universally Unique IDentifier (UUID) URN Namespace
  23. RFC 4123July 2005
  24. RFC 4124Protocol Extensions for Support of
  25. RFC 4125Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
  26. RFC 4126Max Allocation with Reservation Bandwidth Constraints Model for
  27. RFC 4127Russian Dolls Bandwidth Constraints Model for
  28. RFC 4128Bandwidth Constraints Models for
  29. RFC 4129Cisco Systems
  30. RFC 4130MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)
  31. RFC 4131Toshiba
  32. RFC 4132NTT Software Corporation
  33. RFC 4133Entity MIB (Version 3)
  34. RFC 4134Examples of S/MIME Messages
  35. RFC 4135Goals of Detecting Network Attachment in IPv6
  36. RFC 4136OSPF Refresh and Flooding Reduction in Stable Topologies
  37. RFC 4137Nokia
  38. RFC 4138Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)
  39. RFC 4139Boeing
  40. RFC 4140INRIA
  41. RFC 4141Brandenburg
  42. RFC 4142Nine by Nine
  43. RFC 4143Brandenburg
  44. RFC 4144How to Gain Prominence and Influence in Standards Organizations
  45. RFC 4145Ericsson
  46. RFC 4146Simple New Mail Notification
  47. RFC 4147Proposed Changes to the Format of the IANA IPv6 Registry
  48. RFC 4148BCP: 108 August 2005
  49. RFC 4149JHU/APL
  50. RFC 4150JHU/APL
  51. RFC 4151World Wide Web Consortium
  52. RFC 4152August 2005
  53. RFC 4153NTT DoCoMo
  54. RFC 4154NTT
  55. RFC 4155The application/mbox Media Type
  56. RFC 4156The wais URI Scheme
  57. RFC 4157The prospero URI Scheme
  58. RFC 4158A&N Associates
  59. RFC 4159BCP: 109 August 2005
  60. RFC 4160Internet Fax Gateway Requirements
  61. RFC 4161Guidelines for Optional Services for Internet Fax Gateways
  62. RFC 4162KISA
  63. RFC 4163RObust Header Compression (ROHC):
  64. RFC 4164RObust Header Compression (ROHC):
  65. RFC 4165Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)
  66. RFC 4166Ericsson
  67. RFC 4167Graceful OSPF Restart Implementation Report
  68. RFC 4168The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)
  69. RFC 4169Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2
  70. RFC 4170BCP: 110 D. Wing
  71. RFC 4171McDATA Corporation
  72. RFC 4172McDATA
  73. RFC 4173Hewlett-Packard Company
  74. RFC 4174Riverbed Technology
  75. RFC 4175RTP Payload Format for Uncompressed Video
  76. RFC 4176Cisco
  77. RFC 4177Architectural Approaches to Multi-homing for IPv6
  78. RFC 4178The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation Mechanism
  79. RFC 4179Using Universal Content Identifier (UCI)
  80. RFC 4180Common Format and MIME Type for Comma-Separated Values (CSV) Files
  81. RFC 4181BCP: 111
  82. RFC 4182Removing a Restriction on the use of MPLS Explicit NULL
  83. RFC 4183A Suggested Scheme for DNS Resolution of Networks and Gateways
  84. RFC 4184RTP Payload Format for AC-3 Audio
  85. RFC 4185National and Local Characters for DNS Top Level Domain (TLD) Names
  86. RFC 4186Cisco Systems
  87. RFC 4187Nokia
  88. RFC 4188Definitions of Managed Objects for Bridges
  89. RFC 4189October 2005
  90. RFC 4190UCL
  91. RFC 4191November 2005
  92. RFC 4192Procedures for Renumbering an IPv6 Network without a Flag Day
  93. RFC 4193Unique Local IPv6 Unicast Addresses
  94. RFC 4194Lunds Tekniska Hogskola
  95. RFC 4195A Uniform Resource Name (URN) Namespace for the TV-Anytime Forum
  96. RFC 4196J.I. Lee
  97. RFC 4197Requirements for Edge-to-Edge Emulation of
  98. RFC 4198A Uniform Resource Name (URN) Namespace for Federated Content