IETF Mentor Program
Hi all, This is a reminder that, based on discussions during IETF 86, we are trialing an IETF mentoring program. During this trial period, we would like to pair newcomers (people who have attended 3 or fewer meetings or have registered as students) with existing IETF participants. The goal is to provide a resource for the newcomer who can assist them with integrating into the IETF community. Mentors and newcomers will be paired prior to IETF 87. What we need is for people to volunteer to be mentors. As a mentor, we would ask that you be willing to assist your mentoring participant before, during, and (hopefully) after IETF 87. The actual level of interaction will be driven by an agreement between the mentor and the mentoring participant. Additionally, we would need a brief description of your areas of expertise, technical interests, and conversational languages. A description of the Mentor Program (including a FAQ describing how to volunteer to be a mentor) is available: http://www.ietf.org/resources/mentoring-program.html. Anyone interested in being a mentor should follow the sign-up instructions contained in the above URL. The more volunteers we have, the stronger the program will be! Regards, IETF Chair
Internet Draft Submission Cut-Off Today
This is a reminder that the Internet Draft Submission cut-off is today, Monday, July 15, 2013. All submissions are due by UTC 24:00. All drafts can be uploaded using the ID submission tool located here: https://datatracker.ietf.org/submit/ The Internet-Draft cutoff dates as well as other significant dates for IETF 87 can be found at: https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF87 Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-dra...@ietf.org.
Internet Draft Final Submission Cut-Off Today
This is a reminder that the Internet Draft Final Submission (version -01 and up) cut-off is today, Monday, February 25, 2013. All Final Version (-01 and up) submissions are due by UTC 24:00. All drafts can be uploaded using the ID submission tool located here: https://datatracker.ietf.org/submit/ The Internet-Draft cutoff dates as well as other significant dates for IETF 86 can be found at: https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF86 Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-dra...@ietf.org.
Nomcom 2009-10: Third Call for Volunteers
I'm still recruiting volunteers for the 2009-10 Nomcom - if you haven't volunteered yet, please consider doing so! The list of people and posts whose terms end with the March 2010 IETF meeting, and thus the positions for which the nominating committee is responsible, are summarized in the initial announcement: https://datatracker.ietf.org/ann/nomcom/1936/ The IETF nominating committee appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. The 10 nominating committee members are selected randomly from a pool of volunteers. The details of the operation of the nomcom can be found in RFC 3777. We've had a pretty good response over the past week adding 18 new volunteers to the pool, bringing our total to 54, with the following individuals currently in the pool: Marc Blanchet, Viag�nie John Drake, Boeing Satellite Systems Stephen Hanna, Juniper Networks Lixia Zhang, UCLA Sean Turner, IECA, Inc. Wassim Haddad, Ericsson David H. Crocker, Brandenburg InternetWorking David Meyer, Cisco/University of Oregon Kurt Zeilenga, Isode Limited Spencer Dawkins, Huawei Technologies (USA) Yi Zhao, Huawei USA Glen Zorn, Network Zen Christian Schmidt, Nokia Siemens Networks Jouni Korhonen, Nokia Siemens Networks Enrico Marocco, Telecom Italia Ingemar Johansson, Ericsson AB Christer Holmberg, LM Ericsson Theo Zourzouvillys, VoIP.co.uk Scott Brim, Cisco Bernie Hoeneisen, Swisscom Stephen Farrell, Trinity College Dublin/NewBay Software Simon Perreault, Viag�nie Teemu Savolainen, Nokia Suresh Krishnan, Ericsson David Sinicrope, Ericsson Stephen Kent, BBN Technologies Richard Barnes, BBN Technologies Pete Resnick, Qualcomm Incorporated Feng Hu, Huawei Salvatore Loreto, Ericsson Jan Melen, Ericsson Mehmet Ersue, Nokia Siemens Networks Yakov Rekhter, Juniper Networks Conny Jorgen Larsson, Ericsson AB Joe Abley, ICANN Shane Kerr, ISC <---New since last week---> Eliot Lear, Cisco Systems GmbH Larry J. Blunk, Merit Network Matt Lepinski, BBN Technologies Andrew Sullivan, Shinkuro, Inc. Stephan Wenger, No Affiliation Anwar Siddiqui, Avaya Inc. Randall J. Atkinson, Extreme Networks Dimitri Papadimitriou, Alcatel-Lucent Bell Kaushik Narayan, Cisco Systems Inc. Thomas Walsh, Juniper Networks Wojciech Dec, Cisco Fred L. Templin, Boeing Research & Technology Luca Martini, Cisco Kevin Yin, Cisco Ray Bellis, Nominet (UK) Erick Sasaki, NTT John Jason Brzozowski, COMCAST Tom Taylor, PT Taylor Consulting Inc./Huawei If you have volunteered and are not on the above list or have not heard from me otherwise, please contact me ASAP. However, we still need more volunteers - the more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. And, while you have until July 3rd to volunteer, volunteering early really improves the efficiency of the administrative process and ensures that we can quickly make the selection after the deadline. As a reminder, volunteers must have attended 3 of the past 5 IETF meetings - per RFC 3777, which means 3 of the following meetings: IETF-70, IETF-71, IETF-72, IETF-73 and IETF-74. If you qualify, and are willing to forgo appointment to any of the positions for which the nominating committee is responsible, please volunteer. The primary activity for this nomcom will begin just prior to IETF-75 in Stockholm and should be completed in early January 2010. The nomcom will be collecting requirements from the community, as well as talking to candidates and to community members about candidates. There will be weekly conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. While, there is no requirement in RFC 3777 that a participant attend IETF meetings while serving on nomcom, folks should consider that during the IETF meetings, folks that do not attend would be expected to remotely participate during the day in the timezones of the meeting locations - Stockholm the end of July and Hiroshima in November. If you are not yet sure you would like to volunteer, please consider that nomcom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing in that direction. Please volunteer by sending an email before 5:00 pm CDT July 3, 2009 as follows: To: mary.bar...@nortel.com Subject: Nomcom 2009-10 Volunteer Please include the following information in the body: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name // Please include all variations of names you might have used // as entered in the in the IETF Registration Form // May be used for confirmation if selected Please expect an email response from
Adding WAE Jabber Room at 12:00noon ET (1 minute downtime)
Adding WAE jabber room at 12:00noon ET (1 minute downtime) ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: IETF IPv6 platform configuration
All, Thank you for your feedback and request. By default, our practice is to disable these functions until there is a justified need/request. We have enabled ICMP echo, ICMP traceroute, and UDP traceroute. Once again, we encourage and look forward to your responses and requests. The IETF Secretariat. > > -Original Message- > From: Joe Touch [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 15, 2006 11:56 AM > To: Iljitsch van Beijnum > Cc: [EMAIL PROTECTED]; Mark Andrews; ietf@ietf.org > Subject: Re: IETF IPv6 platform configuration > > > > Iljitsch van Beijnum wrote: > > On 15-jun-2006, at 1:51, Mark Andrews wrote: > > > >> > >>> *Only HTTP, SMTP, FTP, and DNS traffic are permitted > through an IPv6 > >>> Native firewall (pings, traceroutes etc. are dropped) > > > >> Why? Shouldn't we be prompting good firewall practices? > > > >> Droping ICMP was a knee jerk reaction to ICMP echo to > >> directed broadcast addresses. Modern routers can be > >> configured to drop directed broadcast packets. > > > > And all of this doesn't even apply to IPv6, it doesn't even support > > broadcasts in general or anything resembling directed > broadcast. ICMP > > replies are also supposed to be rate limited in IPv6. > > IPv4 too. There are other reasons to drop them at firewalls (net > mapping, protecting other protocols), but I agree we ought to be an > example of the best the Internet can provide, not the most paranoid. > > Joe > > ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
IETF IPv6 platform configuration
All, As you’re all aware, on 06/06/06 NSS successfully launched IPv6 services for IETF Web, Mail, and FTP. Following the introduction, NSS received a few technical questions pertaining to IPv6 services. Below you will find technical information as it pertains to configuration and troubleshooting. In addition, NSS is in the process of providing statistics on IPv4 vs. IPv6 that will be posted on the IETF website. IETF IPv6 platform configuration * The IPv6 access to and from IETF is tunneled from a local edge router over IPv4 to a global Internet2 backbone. * All services run native IPv6 in a dual stack configuration. * Only HTTP, SMTP, FTP, and DNS traffic are permitted through an IPv6 Native firewall (pings, traceroutes etc. are dropped) * All services and devices are monitored and logged. * Interdomain IPv6 is dependant upon DNS caching (specifically the amount of time the global DNS is permitted to remember which IP addresses are assigned within any given domain. This is controlled with TTL values set on the authoritative DNS servers) * eMail service supports messaging between IPv4 and IPv6, and will prefer IPv6 if available. Note: All IPv6 addresses are temporary. New static addresses have been requested and will be implemented in the next few weeks. IETF IPv6 Platform Troubleshooting • Verify your local DNS client receives the following DNS answers from your local DNS server: ietf.org IN NS ns1.neustar.com. ns1.neustar.com IN 2001:503:c779:1a::9c9a:108a ietf.org IN MX 10 stiedprmail1.ietf.org. stiedprmail1.ietf.org IN 2001:503:c779:1a::9c9a:1096 www.ietf.org IN 2001:503:c779:b::d1ad:35b4 ftp.ietf.org IN 2001:503:c779:1a::9c9a:1095 * Verify connectivity as follows: telnet 2001:503:c779:b::d1ad:35b4 80 telnet 2001:503:c779:1a::9c9a:1096 25 ftp 2001:503:c779:1a::9c9a:1095 The IETF Secretariat. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Part 2 - Pre-IPV6 maintenance of one of the www.ietf.org servers - 2006/06/04 - 09:30pm EST
Hi All, Unfortunately due to a hardware problem we need to schedule another maintenance outage of one of the www.ietf.org web servers. Today Sunday June 4 at 09:30pm EST, we will be taking down 209.173.53.180 for more maintenance in preparation for supporting IPV6. The outage should be less than 1 hour. This system also serves as the primary site for... noc.ietf.org www.iab.org www.iesg.org so those sites will also be down. Mail and the mailing lists (and their archives) should not be affected. If after 10:30PM EST you experience any difficulties, or notice anything amiss with the sites, please send email to ietf-action at ietf.org, the IAD at iad at ietf.org, and copy ietf-admin at techsquare.com and rpelletier at isoc.org. In case of an emergency, please call the emergency number: +1 301-858-6268. Thank you for your patience. IETF Secretariat. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Pre-IPV6 maintenance of one of the www.ietf.org servers - 2006/06/03 - 12:00am EST
Hi All, Tomorrow Saturday June 3 at 12:00am EST, we will be taking down one of the round robin www servers for the IETF (209.173.53.180) for maintenance in preparation for supporting IPV6. The outage should be less than 1 hour. This system also serves as the primary site for... noc.ietf.org www.iab.org www.iesg.org so those sites will also be down. Mail and the mailing lists (and their archives) should no be affected. If after 01:00AM EST you experience any difficulties, or notice anything amiss with the sites, please send email to ietf-action at ietf.org, the IAD at iad at ietf.org, and copy ietf-admin at techsquare.com and rpelletier at isoc.org. In case of an emergency, please call the emergency number: +1 301-858-6268. Thank you for your patience. IETF Secretariat. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Personal Security Reminder
Please be sure you do not leave any of your belongs unattended anywhere in the meeting venue, including meeting rooms. Your belongs may be picked up by either security or someone else and you may not be able to retrieve them. Several people already have computer bags picked up and they may or maynot be lost. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. o Announcements of conferences, events, or activities that are sponsored or endorsed by the Internet Society or IETF. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]> For more information on the IETF Discussion list, please read the List Charter at http://www.ietf.org/rfc/rfc3005.txt
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. o Announcements of conferences, events, or activities that are sponsored or endorsed by the Internet Society or IETF. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]> For more information on the IETF Discussion list, please read the List Charter at http://www.ietf.org/rfc/rfc3005.txt
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may continue receiving messages for a short while after successfully unsubscribing from the list. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may receive some messages, but only for a relatively short time. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
IETF List maintenance
To remove yourself from the IETF discussion list, send a message to [EMAIL PROTECTED] Enter just the word unsubscribe in the body of the message. NOTE: List requests do not take effect until the next day, and there are always messages in the outbound queue. As such, you may receive some messages, but only for a relatively short time. The IETF discussion list serves two purposes. It furthers the development and specification of Internet technology through discussion of technical issues. It also hosts discussions of IETF direction, policy, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This list is meant for initial discussion only. Discussions that fall within the area of any working group or well established list should be moved to such more specific forum as soon as this is pointed out, unless the issue is one for which the working group needs wider input or direction. In addition to the topics noted above, appropriate postings include: o Last Call discussions of proposed protocol actions o Discussion of technical issues that are candidates for IETF work, but do not yet have an appropriate e-mail venue o Discussion of IETF administrative policies o Questions and clarifications concerning IETF meetings. Inappropriate postings include: o Unsolicited bulk e-mail o Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns o Unprofessional commentary, regardless of the general subject. The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person or of a thread as they deem appropriate to limit abuse. Complaints regarding their decisions should be referred to the IAB <[EMAIL PROTECTED]>
