IETF 81 - Early Bird Cut-off Friday, 15 July 2011
81st IETF Meeting Quebec City, Canada July 24 - 29, 2011 Host: Research In Motion (RIM) Register online at: http://www.ietf.org/meetings/81/ Registration - Early Bird Cut-off is July 15, 2011 Early-Bird: $650 USD, if paid in full prior to 1700 PDT July 15. Late: $800 USD if paid after Early-Bird cutoff date and time. Register online at: http://www.ietf.org/meetings/81/ Only 11 days until the Quebec City IETF! ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'Design Considerations for Session Initiation Protocol (SIP) Overload Control' to Informational RFC (draft-ietf-soc-overload-design-08.txt)
The IESG has approved the following document: - 'Design Considerations for Session Initiation Protocol (SIP) Overload Control' (draft-ietf-soc-overload-design-08.txt) as an Informational RFC This document is the product of the SIP Overload Control Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-soc-overload-design/ Technical Summary Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload control mechanism. Working Group Summary This document was originally started by an ad-hoc Design Team within the SIPPING wg. The document was then adopted by the SIP Overload Control WG once it has been created. Document Quality The draft is a design considerations document and therefore there are no implementations. There are implementations of drafts that are based on the design considerations draft. The document was reviewed in an early stage by the transport area. Version 04 of the draft has also received a second review by Pasi Lassila, an expert on control theory at Aalto university (in Finland) identified by Lars Eggert. Personnel Salvatore Loreto is the Document Shepherd Robert Sparks is the Responsible RAI AD ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC Series Editor Search Announcement
The Internet Engineering Task Force is seeking an RFC Series Editor (RSE). The RSE has overall responsibility for the quality, continuity, and evolution of the Request for Comments (RFC) Series, the Internet's seminal technical standards and publications series. The position has operational and policy development responsibilities. The overall leadership and supervision of RFC Editor function is the responsibility of the RFC Series Editor. The RSE is a senior professional who must be skilled in leading, managing and enhancing a critical, multi-vendor, global information service. The following qualifications are desired: 1. Leadership and management experience. In particular, demonstrated experience in strategic planning and the management of entire operations. Experience that can be applied to fulfill the tasks and responsibilities described in RFC Editor Model (version 2) http://www.ietf.org/id/draft-iab-rfc-editor-model-v2-02.txt. 2. Excellent written and verbal communication skills in English and technical terminology related to the Internet a must; additional languages a plus. 3. Experience with editorial processes. 4. Familiar with a wide range of Internet technologies. 5. An ability to develop a solid understanding of the IETF, its culture and RFC process. 6. Ability to work independently, via email and teleconf, with strong time management skills. 7. Willingness and ability to travel as required. 8. Capable of effectively functioning in a multi-actor and matrixed environment with divided authority and responsibility; ability to work with clarity and flexibility with different constituencies. 9. Experience as an RFC author desired. More information about the position can be found at http://www.rfc-editor.org/rse/RSE-position.html. The RSE reports to the RFC Series Oversight Committee (RSOC). Expressions of interest in the position, CV (including employment history), compensation requirements, and references should be sent to the RSOC search committee at rse-sea...@iab.org Applications will be kept confidential. The application period is open until the position is filled. Questions are to be addressed to rse-sea...@iab.org. The RSOC will interview interested parties at the IETF meeting in Quebec City that begins July 24, 2011. Fred Baker Chair RFC Series Oversight Committee ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6131 on Sieve Vacation Extension: Seconds Parameter
A new Request for Comments is now available in online RFC libraries. RFC 6131 Title: Sieve Vacation Extension: Seconds Parameter Author: R. George, B. Leiba Status: Standards Track Stream: IETF Date: July 2011 Mailbox:robin...@gmail.com, barryle...@computer.org Pages: 5 Characters: 9407 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sieve-vacation-seconds-03.txt URL:http://www.rfc-editor.org/rfc/rfc6131.txt This document describes a further extension to the Sieve Vacation extension, allowing multiple auto-replies to the same sender in a single day by adding a :seconds parameter. [STANDARDS-TRACK] This document is a product of the Sieve Mail Filtering Language 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6132 on Sieve Notification Using Presence Information
A new Request for Comments is now available in online RFC libraries. RFC 6132 Title: Sieve Notification Using Presence Information Author: R. George, B. Leiba Status: Standards Track Stream: IETF Date: July 2011 Mailbox:robin...@gmail.com, barryle...@computer.org Pages: 8 Characters: 17677 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sieve-notify-presence-04.txt URL:http://www.rfc-editor.org/rfc/rfc6132.txt This is a further extension to the Sieve mail filtering language Notification extension, defining presence information that may be checked through the notify_method_capability feature. [STANDARDS-TRACK] This document is a product of the Sieve Mail Filtering Language 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6133 on Sieve Email Filtering: Use of Presence Information with Auto-Responder Functionality
A new Request for Comments is now available in online RFC libraries. RFC 6133 Title: Sieve Email Filtering: Use of Presence Information with Auto-Responder Functionality Author: R. George, B. Leiba, A. Melnikov Status: Informational Stream: IETF Date: July 2011 Mailbox:robin...@gmail.com, barryle...@computer.org, alexey.melni...@isode.com Pages: 9 Characters: 17652 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sieve-autoreply-04.txt URL:http://www.rfc-editor.org/rfc/rfc6133.txt This document describes how the Sieve email filtering language, along with some extensions, can be used to create automatic replies to incoming electronic mail messages based on the address book and presence information of the recipient. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Sieve Mail Filtering Language Working Group of the IETF. 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 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6134 on Sieve Extension: Externally Stored Lists
A new Request for Comments is now available in online RFC libraries. RFC 6134 Title: Sieve Extension: Externally Stored Lists Author: A. Melnikov, B. Leiba Status: Standards Track Stream: IETF Date: July 2011 Mailbox:alexey.melni...@isode.com, barryle...@computer.org Pages: 18 Characters: 37379 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sieve-external-lists-10.txt URL:http://www.rfc-editor.org/rfc/rfc6134.txt The Sieve email filtering language can be used to implement email whitelisting, blacklisting, personal distribution lists, and other sorts of list matching. Currently, this requires that all members of such lists be hard-coded in the script itself. Whenever a member of a list is added or deleted, the script needs to be updated and possibly uploaded to a mail server. This document defines a Sieve extension for accessing externally stored lists -- lists whose members are stored externally to the script, such as using the Lightweight Directory Access Protocol (LDAP), the Application Configuration Access Protocol (ACAP), vCard Extensions to WebDAV (CardDAV), or relational databases. [STANDARDS-TRACK] This document is a product of the Sieve Mail Filtering Language 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
BCP 163, RFC 6303 on Locally Served DNS Zones
A new Request for Comments is now available in online RFC libraries. BCP 163 RFC 6303 Title: Locally Served DNS Zones Author: M. Andrews Status: Best Current Practice Stream: IETF Date: July 2011 Mailbox:ma...@isc.org Pages: 10 Characters: 22503 See Also: BCP0163 I-D Tag:draft-ietf-dnsop-default-local-zones-15.txt URL:http://www.rfc-editor.org/rfc/rfc6303.txt Experience with the Domain Name System (DNS) has shown that there are a number of DNS zones that all iterative resolvers and recursive nameservers should automatically serve, unless configured otherwise. RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This document extends the practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space and other well-known zones with similar characteristics. This memo documents an Internet Best Current Practice. This document is a product of the Domain Name System Operations Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6304 on AS112 Nameserver Operations
A new Request for Comments is now available in online RFC libraries. RFC 6304 Title: AS112 Nameserver Operations Author: J. Abley, W. Maton Status: Informational Stream: IETF Date: July 2011 Mailbox:joe.ab...@icann.org, wma...@ryouko.imsb.nrc.ca Pages: 18 Characters: 34002 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-dnsop-as112-ops-09.txt URL:http://www.rfc-editor.org/rfc/rfc6304.txt Many sites connected to the Internet make use of IPv4 addresses that are not globally unique. Examples are the addresses designated in RFC 1918 for private use within individual sites. Devices in such environments may occasionally originate Domain Name System (DNS) queries (so-called reverse lookups) corresponding to those private-use addresses. Since the addresses concerned have only local significance, it is good practice for site administrators to ensure that such queries are answered locally. However, it is not uncommon for such queries to follow the normal delegation path in the public DNS instead of being answered within the site. It is not possible for public DNS servers to give useful answers to such queries. In addition, due to the wide deployment of private-use addresses and the continuing growth of the Internet, the volume of such queries is large and growing. The AS112 project aims to provide a distributed sink for such queries in order to reduce the load on the IN-ADDR.ARPA authoritative servers. The AS112 project is named after the Autonomous System Number (ASN) that was assigned to it. This document describes the steps required to install a new AS112 node and offers advice relating to such a node's operation. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Domain Name System Operations Working Group of the IETF. 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 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6305 on I'm Being Attacked by PRISONER.IANA.ORG!
A new Request for Comments is now available in online RFC libraries. RFC 6305 Title: I'm Being Attacked by PRISONER.IANA.ORG! Author: J. Abley, W. Maton Status: Informational Stream: IETF Date: July 2011 Mailbox:joe.ab...@icann.org, wma...@ryouko.imsb.nrc.ca Pages: 8 Characters: 15287 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-dnsop-as112-under-attack-help-help-06.txt URL:http://www.rfc-editor.org/rfc/rfc6305.txt Many sites connected to the Internet make use of IPv4 addresses that are not globally unique. Examples are the addresses designated in RFC 1918 for private use within individual sites. Hosts should never normally send DNS reverse-mapping queries for those addresses on the public Internet. However, such queries are frequently observed. Authoritative servers are deployed to provide authoritative answers to such queries as part of a loosely coordinated effort known as the AS112 project. Since queries sent to AS112 servers are usually not intentional, the replies received back from those servers are typically unexpected. Unexpected inbound traffic can trigger alarms on intrusion detection systems and firewalls, and operators of such systems often mistakenly believe that they are being attacked. This document provides background information and technical advice to those firewall operators. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Domain Name System Operations Working Group of the IETF. 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 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6311 on Protocol Support for High Availability of IKEv2/IPsec
A new Request for Comments is now available in online RFC libraries. RFC 6311 Title: Protocol Support for High Availability of IKEv2/IPsec Author: R. Singh, Ed., G. Kalyani, Y. Nir, Y. Sheffer, D. Zhang Status: Standards Track Stream: IETF Date: July 2011 Mailbox:r...@cisco.com, kagar...@cisco.com, y...@checkpoint.com, yaronf.i...@gmail.com, zhangdach...@huawei.com Pages: 26 Characters: 58672 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ipsecme-ipsecha-protocol-06.txt URL:http://www.rfc-editor.org/rfc/rfc6311.txt The IPsec protocol suite is widely used for business-critical network traffic. In order to make IPsec deployments highly available, more scalable, and failure-resistant, they are often implemented as IPsec High Availability (HA) clusters. However, there are many issues in IPsec HA clustering, and in particular in Internet Key Exchange Protocol version 2 (IKEv2) clustering. An earlier document, IPsec Cluster Problem Statement, enumerates the issues encountered in the IKEv2/IPsec HA cluster environment. This document resolves these issues with the least possible change to the protocol. This document defines an extension to the IKEv2 protocol to solve the main issues of IPsec Cluster Problem Statement in the commonly deployed hot standby cluster, and provides implementation advice for other issues. The main issues solved are the synchronization of IKEv2 Message ID counters, and of IPsec replay counters. [STANDARDS-TRACK] This document is a product of the IP Security Maintenance and Extensions 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6276 on DHCPv6 Prefix Delegation for Network Mobility (NEMO)
A new Request for Comments is now available in online RFC libraries. RFC 6276 Title: DHCPv6 Prefix Delegation for Network Mobility (NEMO) Author: R. Droms, P. Thubert, F. Dupont, W. Haddad, C. Bernardos Status: Standards Track Stream: IETF Date: July 2011 Mailbox:rdr...@cisco.com, pthub...@cisco.com, fdup...@isc.org, wassim.had...@ericsson.com, c...@it.uc3m.es Pages: 14 Characters: 30430 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mext-nemo-pd-07.txt URL:http://www.rfc-editor.org/rfc/rfc6276.txt One aspect of network mobility support is the assignment of a prefix or prefixes to a mobile router for use on the links in the mobile network. This document specifies how DHCPv6 prefix delegation can be used for this configuration task. The mobile router plays the role of requesting router, while the home agent assumes the role of delegating router. When the mobile router is outside its home network, the mobile router also assumes the role of DHCPv6 relay agent, co-located with the requesting router function. [STANDARDS-TRACK] This document is a product of the Mobility EXTensions for IPv6 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 6322 on Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams
A new Request for Comments is now available in online RFC libraries. RFC 6322 Title: Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams Author: P. Hoffman Status: Informational Stream: IETF Date: July 2011 Mailbox:paul.hoff...@vpnc.org Pages: 11 Characters: 24153 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-hoffman-alt-streams-tracker-15.txt URL:http://www.rfc-editor.org/rfc/rfc6322.txt This document describes extending the IETF Datatracker to capture and display the progression of Internet-Drafts that are intended to be published as RFCs by the IAB, IRTF, or Independent Submissions Editor. The states and annotations that are to be added to the Datatracker will be applied to Internet-Drafts as soon as any of these streams identify the Internet-Draft as a potential eventual RFC, and will continue through the lifetime of the Internet-Draft. The goal of adding this information to the Datatracker is to give the whole Internet community more information about the status of these Internet-Drafts and the streams from which they originate. 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 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-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC Editor Office Hours at IETF 81
Greetings All, Please note that the RFC Editor will be hosting office hours at IETF 81. The RFC Editor desk will be located in the IETF registration area and will be staffed as follows: RFC Production Center Monday - Wednesday 9:00 - 4:30 Independent Submissions Editor (ISE) -- Nevil Brownlee Monday 1:00 - 3:00 Tuesday 9:00 - 11:30 In addition, RFC Editor staff will be participating in the following tutorial session: Tools for Creating Internet-Drafts Presented by: Alice Hagens and Stefan Santesson Sunday, July 24, 2011 - 3:00 - 4:50 Room: 206 B For more information, please see: http://www.ietf.org/meeting/81/tutorials/creating-internet-drafts.html We look forward to speaking with you. RFC Editor Team ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
