New policy on fee waivers for IETF 108

[IETF Executive Director]

First, a reminder that IETF 108 is switching to a fully online meeting over 5 
days with an agenda structure similar to that of an in-person meeting.  IETF 
108 is hosted by Ericsson and runs 27-31 July 2020 with the IETF 108 Hackathon 
the week before. Registration is now open at:

https://registration.ietf.org  


Second, following a recent consultation [1] the IETF Administration LLC is 
pleased to announce the following changes to fee waivers for IETF 108:

* The number of fee waivers available for IETF 108 is now unlimited 
* Fee waivers are now available at any time until the end of IETF 108.

If the registration fee for IETF 108 presents a barrier to your participation 
you can apply for a fee waiver for IETF 108 by filling out this form and you 
will be provided with a free registration:

https://www.ietf.org/how/meetings/108/108-registration-fee-waiver/

Fee waivers are offered on an honour system with no check on eligibility. 

If you have already paid the fee and now require a fee waiver then you can 
contact regist...@ietf.org for a full refund.


Please note that it will be a little while before the website and fee waiver 
form are updated to reflect these changes.


Feel free to contact me directly if you have any questions.

[1]  
https://mailarchive.ietf.org/arch/msg/ietf-announce/fVsDPW9hbgx5mflHpt7C39uFD0s/

-- 
Jay Daley
IETF Executive Director
exec-direc...@ietf.org

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Nomcom 2020-2021 Final Call For Volunteers

[NomCom Chair 2020]

Hi IETFers,
We're down to the last week of accepting NomCom volunteers. And I need more! 
Lots more!

I have 64. I'd really like to get another 100 names. Hopefully, some of you are 
checking the volunteer box on IETF 108 registration. But I don't have anything 
from canceled IETF 107 registration, and the NomCom question wasn't asked on 
IETF 106. So I need a flood of volunteers to come in over the next week.
Barbara
=
The IETF NomCom appoints people to fill the open slots on the LLC, IETF Trust, 
the IAB, and the IESG.

Ten voting members for the NomCom are selected in a verifiably random way from 
a pool of volunteers. The more volunteers, the better chance we have of 
choosing a random yet representative cross section of the IETF population.

The details of the operation of the NomCom can be found in BCP 10 (RFC 8713). 
RFC 3797 details the selection algorithm.

Special for this year (and only this year), we also have RFC 8788 (one-off 
update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer:

  Members of the IETF community must have attended at least three of
  the last five in-person IETF meetings in order to volunteer.

  The five meetings are the five most recent in-person meetings that
  ended prior to the date on which the solicitation for NomCom
  volunteers was submitted for distribution to the IETF community.
  Because no IETF 107 in-person meeting was held, for the 2020-2021
  Nominating Committee those five meetings are IETFs
102 [Montreal, Canada; July 2018],
103 [Bangkok, Thailand; November 2018],
104 [Prague, Czech Republic; March 2019],
105 [Montreal, Canada; July 2019], and 
106 [Singapore; November 2019].

Keep in mind that eligibility is based on in-person attendance at the five 
listed meetings. You can check your eligibility at: 
https://www.ietf.org/registration/nomcom.py.

If you qualify, please volunteer. Before you decide to volunteer, please 
remember that anyone appointed to this NomCom will not be considered as a 
candidate for any of the positions that the 2020 - 2021 NomCom is responsible 
for filling.

People commonly volunteer by ticking the box on IETF registration forms. The 
IETF 106 form did not ask whether people were willing to volunteer. IETF 107 
did ask, but all those registrations were canceled. I have asked the 
Secretariat if it is possible to get the list if volunteers from canceled IETF 
107 registrations. If that list is available, I will contact all who are 
verified as eligible. But given the uncertainty of this process, I would 
encourage people to volunteer directly (see the bottom of this email for 
instructions). Thank you for volunteering!

The list of people and posts whose terms end with the March 2021 IETF meeting, 
and thus the positions for which this NomCom is responsible, are

IETF Trust:
Joel Halpern

LLC:
Maja Andjelkovic

IAB:
Jari Arkko
Jeff Tantsura
Mark Nottingham
Stephen Farrell
Wes Hardaker
Zhenbin Li

IESG:
Alissa Cooper, IETF Chair/GEN AD
Alvaro Retana, RTG AD
Barry Leiba, ART AD
Deborah Brungard, RTG AD
Éric Vyncke, INT AD
Magnus Westerlund, TSV AD
Roman Danyliw, SEC AD
Warren Kumari, OPS AD

All appointments are for 2 years. The Routing area has 3 ADs and the General 
area has 1; all other areas have 2 ADs. Thus, all areas (that have more than 
one AD) have at least one continuing AD.

The primary activity for this NomCom will begin in July 2020 and should be 
completed in January 2021.  The NomCom will have regularly scheduled conference 
calls to ensure progress. There will be activities to collect requirements from 
the community, review candidate questionnaires, review feedback from community 
members about candidates, and talk to candidates.

While being a NomCom member does require some time commitment it is also a very 
rewarding experience.

As a member of the NomCom it is very important that you be willing and able to 
attend either videoconference or in-person meetings (which may not happen) 
during 14-20 November (IETF 109 - Bangkok) to conduct interviews. 
Videoconference attendance will be supported whether or not there are in-person 
meetings. Orientation and setting of the NomCom schedule will be done by 
videoconference during the week 20-24 July (exact time and date to be 
determined after NomCom membership is finalized on July 12), the week prior to 
IETF 108.  Being at IETF 110 (Prague) is not essential.

Please volunteer by sending me an email before 23:59 UTC June 24, 2020, as 
follows:

To: nomcom-chair-2...@ietf.org
Subject: NomCom 2020-21 Volunteer

Please include the following information in the email body:

Your Full Name: 
// as you write it on the IETF registration form

Current Primary Affiliation:
// Typically what goes in the Company field
// in the IETF Registration Form

Emails: 
   // All email 

RFC 8806 on Running a Root Server Local to a Resolver

[rfc-editor]

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


RFC 8806

Title:  Running a Root Server Local 
to a Resolver 
Author: W. Kumari,
P. Hoffman
Status: Informational
Stream: IETF
Date:   June 2020
Mailbox:war...@kumari.net, 
paul.hoff...@icann.org
Pages:  12
Obsoletes:  RFC 7706

I-D Tag:draft-ietf-dnsop-7706bis-12.txt

URL:https://www.rfc-editor.org/info/rfc8806

DOI:10.17487/RFC8806

Some DNS recursive resolvers have longer-than-desired round-trip
times to the closest DNS root server; those resolvers may have
difficulty getting responses from the root servers, such as during a
network attack. Some DNS recursive resolver operators want to prevent
snooping by third parties of requests sent to DNS root servers. In
both cases, resolvers can greatly decrease the round-trip time and
prevent observation of requests by serving a copy of the full root
zone on the same server, such as on a loopback address or in the
resolver software. This document shows how to start and maintain such
a copy of the root zone that does not cause problems for other users
of the DNS, at the cost of adding some operational fragility for the
operator.

This document obsoletes RFC 7706.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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

IAB Reappoints Tim Wicinski to the Community Coordination Group

[IAB Executive Administrative Manager]

The IAB has reappointed Tim Wicinski to the Community Coordination Group 
for the 2020-2022 term. The IAB thanks him for his willingness to serve 
the community in this capacity.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: (IPv6-Only-Preferred Option for DHCPv4) to Proposed Standard

[The IESG]

The IESG has received a request from the Dynamic Host Configuration WG (dhc)
to consider the following document: - 'IPv6-Only-Preferred Option for DHCPv4'
   as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2020-07-02. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document specifies a DHCPv4 option to indicate that a host
   supports an IPv6-only mode and willing to forgo obtaining an IPv4
   address if the network provides IPv6 connectivity.  It also updates
   RFC2563 to specify the DHCPv4 server behavior when the server
   receives a DHCPDISCOVER not containing the Auto-Configure option.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dhc-v6only/



No IPR declarations have been submitted directly on this I-D.





___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Formal IESG Teleconference WebEx and Dial-in Information: 25 June 2020

[IESG Secretary]

As previously announced [1], all members of the community are welcome to  
attend 
formal IESG telechats as observers. Observers are not invited to participate in 
the discussion.

The next formal IESG telechat will be held on Thursday,  June 25, 
2020 at 07:00 PT (14:00 UTC).  WebEx and Dial-in information is at the bottom 
of this message.

The agenda for the upcoming telechat can be found at


A calendar of upcoming public telechats can be downloaded or subscribed 
to at: 
https://calendar.google.com/calendar/ical/ietf.org_egdabaf39ch5v8a13dt39mvee4%40group.calendar.google.com/public/basic.ics


Topic: IESG Formal Telechat
Date: June 25, 2020
Time: 07:00 PT (San Francisco, UTC-07:00)
09:00 CT
10:00 ET
14:00 UTC
15:00 United Kingdom (GMT)
16:00 Germany, France, Belgium, Switzerland (CET)
17:00 Finland (EET)
00:00 (next day) (Queensland) Australia (AEST)
  
--- 
JOIN WEBEX MEETING
https://ietf.webex.com/ietf/j.php?MTID=m38beb3706c7e5a24dd749a50d7e87dfd
Meeting number: 642 944 708
Meeting password: 1234


JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 642 987 400 
--- 
To join the audio conference using Skype 
--- 
1.  Bring up your Skype application.
2.  Bring up your browser, and go to the WebEx URL.
3.  Enter your name and email address.
4.  Close the WebEx window prompting for a phone number.
5.  Select the "info" tab at the top of the WebEx browser page.
6.  Go to Skype, and dial the U.S. Toll-Free number from the meeting 
announcement.
7.  Click on the DialPad tab on the Skype window.
8.  Use the virtual keypad to enter the meeting number followed by #.
9.  Use the virtual keypad to enter your attendee ID followed by #.

The playback of UCF (Universal Communications Format) rich media files
requires appropriate players. To view this type of rich media files in
the meeting, please check whether you have the players installed on your
computer by going to https://workgreen.webex.com/workgreen/
systemdiagnosis.php.

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+14087926300x960506070#

IMPORTANT NOTICE: This WebEx service includes a feature that allows
audio and any documents and other materials exchanged or viewed during
the session to be recorded. By joining this session, you automatically
consent to such recordings. If you do not consent to the recording,
discuss your concerns with the meeting host prior to the start of the
recording or do not join the session. Please note that any such
recordings may be subject to discovery in the event of litigation.

[1] 
https://mailarchive.ietf.org/arch/msg/ietf-announce/Eackc8-MgJw8IbdquLuPlcoDZpo

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce