f



[rfc-dist] RFC 5417 on Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5417

        Title:      Control And Provisioning of Wireless 
                    Access Points (CAPWAP) Access Controller DHCP 
                    Option 
        Author:     P. Calhoun
        Status:     Standards Track
        Date:       March 2009
        Mailbox:    pcalhoun@cisco.com
        Pages:      6
        Characters: 11551
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-capwap-dhc-ac-option-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5417.txt

The Control And Provisioning of Wireless Access Points Protocol
allows a Wireless Termination Point to use DHCP to discover the
Access Controllers to which it is to connect.  This document
describes the DHCP options to be used by the CAPWAP Protocol.
[STANDARDS TRACK]

This document is a product of the Control And Provisioning of Wireless
Access Points Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
0
rfc
3/6/2009 12:55:29 AM
comp.std.announce 2062 articles. 0 followers. rfc-editor (206) is leader. Post Follow

0 Replies
793 Views

Similar Articles

[PageSpeed] 7

Reply:

Similar Artilces:

[rfc-dist] RFC 5415 on Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
A new Request for Comments is now available in online RFC libraries. RFC 5415 Title: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification Author: P. Calhoun, Ed., M. Montemurro, Ed., D. Stanley, Ed. Status: Standards Track Date: March 2009 Mailbox: pcalhoun@cisco.com, mmontemurro@rim.com, dstanley@arubanetworks.com Pages: 155 Characters: 345381 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-capwap-protocol-specification-15.txt URL: http://www.rfc-editor.org/rfc/rfc5415.txt This specification defines the Control And Provisioning of Wireless Access Points (CAPWAP) Protocol, meeting the objectives defined by the CAPWAP Working Group in RFC 4564. The CAPWAP protocol is designed to be flexible, allowing it to be used for a variety of wireless technologies. This document describes the base CAPWAP protocol, while separate binding extensions will enable its use with additional wireless technologies. [STANDARDS TRACK] This document is a product of the Control And Provisioning of Wireless Access Points Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet com...

[rfc-dist] RFC 5416 on Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11
A new Request for Comments is now available in online RFC libraries. RFC 5416 Title: Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11 Author: P. Calhoun, Ed., M. Montemurro, Ed., D. Stanley, Ed. Status: Standards Track Date: March 2009 Mailbox: pcalhoun@cisco.com, mmontemurro@rim.com, dstanley@arubanetworks.com Pages: 76 Characters: 175870 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-capwap-protocol-binding-ieee80211-12.txt URL: http://www.rfc-editor.org/rfc/rfc5416.txt Wireless LAN product architectures have evolved from single autonomous access points to systems consisting of a centralized Access Controller (AC) and Wireless Termination Points (WTPs). The general goal of centralized control architectures is to move access control, including user authentication and authorization, mobility management, and radio management from the single access point to a centralized controller. This specification defines the Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Binding Specification for use with the IEEE 802.11 Wireless Local Area Network protocol. [STANDARDS TRACK] This document is a product of the Control ...

[rfc-dist] RFC 5418 on Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 Deployments
A new Request for Comments is now available in online RFC libraries. RFC 5418 Title: Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 Deployments Author: S. Kelly, T. Clancy Status: Informational Date: March 2009 Mailbox: scott@hyperthought.com, clancy@LTSnet.net Pages: 34 Characters: 74169 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-capwap-threat-analysis-04.txt URL: http://www.rfc-editor.org/rfc/rfc5418.txt Early Wireless Local Area Network (WLAN) deployments feature a "fat" Access Point (AP), which serves as a %stand-alone interface between the wired and wireless network segments. However, this model raises scaling, mobility, and manageability issues, and the Control and Provisioning of Wireless Access Points (CAPWAP) protocol is meant to address these issues. CAPWAP effectively splits the fat AP functionality into two network elements, and the communication channel between these components may traverse potentially hostile hops. This document analyzes the security exposure resulting from the introduction of CAPWAP and summarizes the associated security considerations for IEEE 802.11-based CAPWAP implementations and deployments. This memo provides information for the Internet...

[rfc-dist] RFC 6065 on Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group Mappings
A new Request for Comments is now available in online RFC libraries. RFC 6065 Title: Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group Mappings Author: K. Narayan, D. Nelson, R. Presuhn, Ed. Status: Standards Track Stream: IETF Date: December 2010 Mailbox: kaushik_narayan@yahoo.com, d.b.nelson@comcast.net, ...

[rfc-dist] RFC 6320 on Protocol for Access Node Control Mechanism in Broadband Networks
A new Request for Comments is now available in online RFC libraries. RFC 6320 Title: Protocol for Access Node Control Mechanism in Broadband Networks Author: S. Wadhwa, J. Moisand, T. Haag, N. Voigt, T. Taylor, Ed. Status: Standards Track Stream: IETF Date: October 2011 Mailbox: sanjay.wadhwa@alcatel-lucent.com, jmoisand@juniper.net, haagt@telekom.de, norbert.voigt@nsn.com, tom111.taylor@bell.net Pages: 82 Characters: 178446 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ancp-protocol-17.txt URL: http://www.rfc-editor.org/rfc/rfc6320.txt This document describes the Access Node Control Protocol (ANCP). ANCP operates between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in a multi-service reference architecture in order to perform operations related to Quality of Service, service, and subscribers. Use cases for ANCP are documented in RFC 5851. As well as describing the base ANCP protocol, this document specifies capabilities for Digital Subscriber Line (DSL) topology discovery, line configuration, and remote line connectivity testing. The design of ANCP allows for protocol extensions in other docum...

[rfc-dist] RFC 6536 on Network Configuration Protocol (NETCONF) Access Control Model
A new Request for Comments is now available in online RFC libraries. RFC 6536 Title: Network Configuration Protocol (NETCONF) Access Control Model Author: A. Bierman, M. Bjorklund Status: Standards Track Stream: IETF Date: March 2012 Mailbox: andy@yumaworks.com, mbj@tail-f.com Pages: 49 Characters: 90803 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netconf-access-control-07.txt URL: http://www.rfc-editor.org/rfc/rfc6536.txt The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) 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 protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK] This document is a product of the Network Configuration Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Intern...

[rfc-dist] RFC 5713 on Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)
A new Request for Comments is now available in online RFC libraries. RFC 5713 Title: Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) Author: H. Moustafa, H. Tschofenig, S. De Cnodder Status: Informational Date: January 2010 Mailbox: hassnaa.moustafa@orange-ftgroup.com, Hannes.Tschofenig@gmx.net, stefaan.de_cnodder@alcatel-lucent.com Pages: 18 Characters: 39600 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ancp-security-threats-08.txt URL: http://www.rfc-editor.org/rfc/rfc5713.txt The Access Node Control Protocol (ANCP) aims to communicate Quality of Service (QoS)-related, service-related, and subscriber-related configurations and operations between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)). The main goal of this protocol is to allow the NAS to configure, manage, and control access equipment, including the ability for the Access Nodes to report information to the NAS. This present document investigates security threats that all ANCP nodes could encounter. This document develops a threat model for ANCP security, with the aim of deciding which security functions are required. Based on th...

[rfc-dist] RFC 5192 on DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents
A new Request for Comments is now available in online RFC libraries. RFC 5192 Title: DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents Author: L. Morand, A. Yegin, S. Kumar, S. Madanapalli Status: Standards Track Date: May 2008 Mailbox: lionel.morand@orange-ftgroup.com, a.yegin@partner.samsung.com, surajk@techmahindra.com, syam@samsung.com Pages: 8 Characters: 14986 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-paa-option-05.txt URL: http://www.rfc-editor.org/rfc/rfc5192.txt This document defines new DHCPv4 and DHCPv6 options that contain a list of IP addresses to locate one or more PANA (Protocol for carrying Authentication for Network Access) Authentication Agents (PAAs). This is one of the methods that a PANA Client (PaC) can use to locate PAAs. [STANDARDS TRACK] This document is a product of the Dynamic Host Configuration Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Offi...

[rfc-dist] RFC 6171 on The Lightweight Directory Access Protocol (LDAP) Don't Use Copy Control
A new Request for Comments is now available in online RFC libraries. RFC 6171 Title: The Lightweight Directory Access Protocol (LDAP) Don't Use Copy Control Author: K. Zeilenga Status: Standards Track Stream: IETF Date: March 2011 Mailbox: Kurt.Zeilenga@Isode.COM Pages: 6 Characters: 11124 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-zeilenga-ldap-dontusecopy-09.txt URL: http://www.rfc-editor.org/...

[rfc-dist] RFC 6505 on A Mixer Control Package for the Media Control Channel Framework
A new Request for Comments is now available in online RFC libraries. RFC 6505 Title: A Mixer Control Package for the Media Control Channel Framework Author: S. McGlashan, T. Melanchuk, C. Boulton Status: Standards Track Stream: IETF Date: March 2012 Mailbox: smcg.stds01@mcglashan.org, timm@rainwillow.com, chris@ns-technologies.com Pages: 89 Characters: 187038 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mediactrl-mixer-control-package-14.txt URL: http://www.rfc-editor.org/rfc/rfc6505.txt This document defines a Media Control Channel Framework Package for managing mixers for media conferences and connections. The package defines request elements for managing conference mixers, managing mixers between conferences and/or connections, as well as associated responses and notifications. The package also defines elements for auditing package capabilities and mixers [STANDARDS-TRACK] This document is a product of the Media Server Control Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current editi...

[rfc-dist] RFC 5414 on Wireless LAN Control Protocol (WiCoP)
A new Request for Comments is now available in online RFC libraries. RFC 5414 Title: Wireless LAN Control Protocol (WiCoP) Author: S. Iino, S. Govindan, M. Sugiura, H. Cheng Status: Informational Date: February 2010 Mailbox: iino.satoshi@jp.panasonic.com, saravanan.govindan@sg.panasonic.com, sugiura.mikihito@jp.panasonic.com, hong.cheng@sg.panasonic.com Pages: 54 Characters: 118969 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iino-capwap-wicop-02.txt URL: http://www.rfc-editor.org/rfc/rfc5414.txt The popularity of wireless local area networks (WLANs) has led to widespread deployments across different establishments. It has also translated into an increasing scale of the WLANs. Large-scale deployments made of large numbers of wireless termination points (WTPs) and covering substantial areas are increasingly common. The Wireless LAN Control Protocol (WiCoP) described in this document allows for the control and provisioning of large-scale WLANs. It enables central management of these networks and realizes the objectives set forth for the Control And Provisioning of Wireless Access Points (CAPWAP). This document defines a Historic Document for the Internet community. INFORMATIONAL: This memo provides informa...

[rfc-dist] RFC 5593 on Internet Message Access Protocol (IMAP) - URL Access Identifier Extension
A new Request for Comments is now available in online RFC libraries. RFC 5593 Title: Internet Message Access Protocol (IMAP) - URL Access Identifier Extension Author: N. Cook Status: Standards Track Date: June 2009 Mailbox: neil.cook@noware.co.uk Pages: 10 Characters: 18149 Updates: RFC5092 I-D Tag: draft-ncook-urlauth-accessid-02.txt URL: http://www.rfc-editor.org/rfc/rfc5593.txt The existing IMAP URL specification (RFC 5092) lists several <access> identifiers and <access> identifier prefixes that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new <access> identifiers as well as an IANA mechanism to register new <access> identifiers for future applications. This document updates RFC 5092. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is se...

[rfc-dist] RFC 6231 on An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework
A new Request for Comments is now available in online RFC libraries. RFC 6231 Title: An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework Author: S. McGlashan, T. Melanchuk, C. Boulton Status: Standards Track Stream: IETF Date: May 2011 Mailbox: smcg.stds01@mcglashan.org, timm@rainwillow.com, chris@ns-technologies.com Pages: 134 Characters: 286771 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mediactrl-ivr-control-package-11.txt URL: http://www.rfc-editor.org/rfc/rfc6231.txt This document defines a Media Control Channel Framework Package for Interactive Voice Response (IVR) dialog interaction on media connections and conferences. The package defines dialog management request elements for preparing, starting, and terminating dialog interactions, as well as associated responses and notifications. Dialog interactions are specified in a dialog language. This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, Dual-Tone Multi-Frequency (DTMF) collection, and media recording) and allows other dialog languages to be used. The package also defines elements for auditing package capabilities and IVR dialog...

[rfc-dist] RFC 6323 on Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP)
A new Request for Comments is now available in online RFC libraries. RFC 6323 Title: Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP) Author: G. Renker, G. Fairhurst Status: Standards Track Stream: IETF Date: July 2011 Mailbox: gerrit@erg.abdn.ac.uk, gorry@erg.abdn.ac.uk Pages: 13 Characters: 27434 Updates: RFC4342, RFC5622 I-D Tag: draft-ietf-dccp-tfrc-rtt-option-06.txt URL: http://www.rfc-editor.org/rfc/rfc6323.txt This document specifies an update to the round-trip time (RTT) estimation algorithm used for TFRC (TCP-Friendly Rate Control) congestion control by the Datagram Congestion Control Protocol (DCCP). It updates specifications for the CCID-3 and CCID-4 Congestion Control IDs of DCCP. The update addresses parameter-estimation problems occurring with TFRC-based DCCP congestion control. It uses a recommendation made in the original TFRC specification to avoid the inherent problems of receiver-based RTT sampling, by utilising higher-accuracy RTT samples already available at the sender. It is integrated into the feature set of DCCP as an end-to-end negotiable extension. [STANDARDS-TRACK] This document is a product of the Datagram Congestion Control Protocol Working Group of the IETF. This is now a Prop...

[rfc-dist] RFC 6431 on Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP)
A new Request for Comments is now available in online RFC libraries. RFC 6431 Title: Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP) Author: M. Boucadair, P. Levis, G. Bajko, T. Savolainen, T. Tsou Status: Informational Stream: Independent Date: November 2011 Mailbox: mohamed.boucadair@orange.com, pierre.levis@orange.com, gabor.bajko@nokia.com, teemu.savolainen@nokia.com, tina.tsou.zouting@huawei.com Pages: 16 Characters: 33981 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-boucadair-pppext-portrange-option-09.txt URL: http://www.rfc-editor.org/rfc/rfc6431.txt This document defines two Huawei IPCP (IP Control Protocol) options used to convey a set of ports. These options can be used in the context of port range-based solutions or NAT-based solutions for port delegation and forwarding purposes. This document is not an Internet Standards Track specification; it is published for informational purposes. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce an...

[rfc-dist] RFC 6153 on DHCPv4 and DHCPv6 Options for Access Network Discovery and Selection Function (ANDSF) Discovery
A new Request for Comments is now available in online RFC libraries. RFC 6153 Title: DHCPv4 and DHCPv6 Options for Access Network Discovery and Selection Function (ANDSF) Discovery Author: S. Das, G. Bajko Status: Standards Track Stream: IETF Date: February 2011 Mailbox: subir@research.Telcordia.com, gabor.bajko@nokia.com Pages: 7 Characters: 13420 Updates/Obsoletes/SeeAlso: None ...

Access Controls in Access
How on access can you set access controls to your users? If they log in with one username and password they can just read information and if they log in with another username and password they can read and write? I have no idea how to do this, is it even possible?? Thank you Try playing with the access security tool, you can add users, groups, passwords, read/write allowances etc. to your database using that. Its under the 'Tools' menu of Access. Brian wrote: > Try playing with the access security tool, you can add users, groups, > passwords, read/write allowances etc. to you...

[rfc-dist] RFC 5622 on Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)
A new Request for Comments is now available in online RFC libraries. RFC 5622 Title: Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP) Author: S. Floyd, E. Kohler Status: Experimental Date: August 2009 Mailbox: floyd@icir.org, kohler@cs.ucla.edu Pages: 19 Characters: 45394 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dccp-ccid4-05.txt URL: http://www.rfc-editor.org/rfc/rfc5622.txt This document specifies a profile for Congestion Control Identifier 4, the small-packet variant of TCP-Friendly Rate Control (TFRC), in the Datagram Congestion Control Protocol (DCCP). CCID 4 is for experimental use, and uses TFRC-SP (RFC 4828), a variant of TFRC designed for applications that send small packets. CCID 4 is considered experimental because TFRC-SP is itself experimental, and is not proposed for widespread deployment in the global Internet at this time. The goal for TFRC-SP is to achieve roughly the same bandwidth in bits per second (bps) as a TCP flow using packets of up to 1500 bytes but experiencing the same level of congestion. CCID 4 is for use for senders that send small packets and would like a TCP- friendly sending rate, possibly with Explicit Congestion No...

[rfc-dist] Corrected Announcement: RFC 5287 on Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks
A new Request for Comments is now available in online RFC libraries. RFC 5287 Title: Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks Author: A. Vainshtein, Y(J). Stein Status: Standards Track Date: August 2008 Mailbox: Alexander.Vainshtein@ecitele.com, yaakov_s@rad.com Pages: 16 Characters: 33070 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-tdm-control-protocol-extensi-07.txt URL: http://www.rfc-editor.org/rfc/rfc5287.txt This document defines extension to the Pseudowire Emulation Edge-to-Edge (PWE3) control protocol RFC 4447 and PWE3 IANA allocations RFC 4446 required for the setup of Time-Division Multiplexing (TDM) pseudowires in MPLS networks. [STANDARDS TRACK] This document is a product of the Pseudo Wire Emulation Edge to Edge Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcemen...

class-based access control VS instance-based access control
Why C++ (as well as Java) adopts class-based access control instead of instance-based access control? I had never paid attention to whether an access-control is class-based or instance-based but only intuitively thought that the latter was the one being used. Since it does not seem to make sense to let an instance "a1" of Class "A" to have access to the private data of instance "a2" of the same Class A, does it? xz wrote: > Why C++ (as well as Java) adopts class-based access control instead of > instance-based access control? Mostly because of the differ...

[rfc-dist] RFC 5681 on TCP Congestion Control
A new Request for Comments is now available in online RFC libraries. RFC 5681 Title: TCP Congestion Control Author: M. Allman, V. Paxson, E. Blanton Status: Standards Track Date: September 2009 Mailbox: mallman@icir.org, vern@icir.org, eblanton@cs.purdue.edu Pages: 18 Characters: 44339 Obsoletes: RFC2581 I-D Tag: draft-ietf-tcpm-rfc2581bis-07.txt URL: http://www.rfc-editor.org/rfc/rfc5681.txt This document defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. In addition, the document specifies how TCP should begin transmission after a relatively long idle period, as well as discussing various acknowledgment generation methods. This document obsoletes RFC 2581. [STANDARDS TRACK] This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF. This is now a Draft Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unli...

[rfc-dist] RFC 4833 on Timezone Options for DHCP
A new Request for Comments is now available in online RFC libraries. RFC 4833 Title: Timezone Options for DHCP Author: E. Lear, P. Eggert Status: Standards Track Date: April 2007 Mailbox: lear@cisco.com, eggert@cs.ucla.edu Pages: 10 Characters: 19573 Updates: RFC2132 See-Also: I-D Tag: draft-ietf-dhc-timezone-option-05.txt URL: http://www.rfc-editor.org/rfc/rfc4833.txt Two common ways to communicate timezone information are POSIX 1003.1 timezone strings and timezone database names. This memo specifies DHCP options for each of those methods. The DHCPv4 time offset option is deprecated. [STANDARDS TRACK] This document is a product of the Dynamic Host Configuration Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests...

[rfc-dist] RFC 6230 on Media Control Channel Framework
A new Request for Comments is now available in online RFC libraries. RFC 6230 Title: Media Control Channel Framework Author: C. Boulton, T. Melanchuk, S. McGlashan Status: Standards Track Stream: IETF Date: May 2011 Mailbox: chris@ns-technologies.com, timm@rainwillow.com, smcg.stds01@mcglashan.org Pages: 49 Characters: 112479 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mediactrl-sip-control-framework-12.txt URL: http://www.rfc-editor.org/rfc/rfc6230.txt This document describes a framework and protocol for application deployment where the application programming logic and media processing are distributed. This implies that application programming logic can seamlessly gain access to appropriate resources that are not co-located on the same physical network entity. The framework uses the Session Initiation Protocol (SIP) to establish an application-level control mechanism between application servers and associated external servers such as media servers. The motivation for the creation of this framework is to provide an interface suitable to meet the requirements of a centralized conference system, where the conference system can be distributed, as defined by the XCON working group in the IETF. It is not, however, limit...

[rfc-dist] RFC 6422 on Relay-Supplied DHCP Options
A new Request for Comments is now available in online RFC libraries. RFC 6422 Title: Relay-Supplied DHCP Options Author: T. Lemon, Q. Wu Status: Standards Track Stream: IETF Date: December 2011 Mailbox: mellon@nominum.com, sunseawq@huawei.com Pages: 8 Characters: 16056 Updates: RFC3315 I-D Tag: draft-ietf-dhc-dhcpv6-relay-supplied-options-09.txt URL: http://www.rfc-editor.org/rfc/rfc6422.txt DHCPv6 relay agents cannot communicate with DHCPv6 clients directly. However, in some cases, the relay agent possesses some information that would be useful to the DHCPv6 client. This document describes a mechanism whereby the DHCPv6 relay agent can provide such information to the DHCPv6 server, which can, in turn, pass this information on to the DHCP client. This document updates RFC 3315 (DHCPv6) by making explicit the implicit requirement that relay agents not modify the content of encapsulation payloads as they are relayed back toward clients. [STANDARDS-TRACK] This document is a product of the Dynamic Host Configuration Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to...

Web resources about - [rfc-dist] RFC 5417 on Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option - comp.std.announce

Resources last updated: 3/3/2016 2:16:10 AM