LLC Board Meeting Details - 9 September 2021

2021-09-02 Thread IETF Administration LLC Board of Directors Chair 
IETF LLC Board of Directors meetings are conducted via web/teleconference. 
Members of the community are welcome to attend certain portions of these 
meetings as observers. Regular meetings are divided into four sections:

1. Open (to Observers)
2. Board + Support Staff Only
3. Board + Executive Director Only
4. Executive Session (Board-Only)

The next meeting will be held on Thursday, 9 September 2021 at 12:00 PT (19:00 
UTC). WebEx and Dial-in information is at the bottom of this message and also 
at .

The agenda for the meeting can be found at 
.

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


--- 
JOIN WEBEX MEETING
https://ietf.webex.com/ietf/j.php?MTID=m5481867e37f4c98327c151d9a6a7cd78
Meeting number (access code):  178 797 1273
Meeting password: meetings


JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Access code:  178 797 1273



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.

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

RFC 9133 on Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel

2021-09-02 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9133

Title:  Controlling Filtering Rules Using Distributed 
Denial-of-Service Open Threat Signaling (DOTS) Signal 
Channel 
Author: K. Nishizuka,
M. Boucadair,
T. Reddy.K,
T. Nagata
Status: Standards Track
Stream: IETF
Date:   September 2021 
Mailbox:kan...@nttv6.jp,
mohamed.boucad...@orange.com,
kond...@gmail.com,
nag...@lepidum.co.jp
Pages:  26
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-dots-signal-filter-control-07.txt

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

DOI:10.17487/RFC9133

This document specifies an extension to the Distributed
Denial-of-Service Open Threat Signaling (DOTS) signal channel
protocol so that DOTS clients can control their filtering rules when
an attack mitigation is active.

Particularly, this extension allows a DOTS client to activate or
deactivate existing filtering rules during a Distributed
Denial-of-Service (DDoS) attack. The characterization of these
filtering rules is conveyed by a DOTS client during an 'idle' time
(i.e., no mitigation is active) by means of the DOTS data channel
protocol.

This document is a product of the DDoS Open Threat Signaling Working Group of 
the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  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

RFC 9132 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification

2021-09-02 Thread rfc-editor 
A new Request for Comments is now available in online RFC libraries.


RFC 9132

Title:  Distributed Denial-of-Service Open Threat Signaling 
(DOTS) Signal Channel Specification 
Author: M. Boucadair, Ed.,
J. Shallow,
T. Reddy.K
Status: Standards Track
Stream: IETF
Date:   September 2021 
Mailbox:mohamed.boucad...@orange.com,
supjps-i...@jpshallow.com,
kond...@gmail.com
Pages:  107
Obsoletes:  RFC 8782

I-D Tag:draft-ietf-dots-rfc8782-bis-08.txt

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

DOI:10.17487/RFC9132

This document specifies the Distributed Denial-of-Service Open Threat
Signaling (DOTS) signal channel, a protocol for signaling the need
for protection against Distributed Denial-of-Service (DDoS) attacks
to a server capable of enabling network traffic mitigation on behalf
of the requesting client.

A companion document defines the DOTS data channel, a separate
reliable communication layer for DOTS management and configuration
purposes.

This document obsoletes RFC 8782.

This document is a product of the DDoS Open Threat Signaling Working Group of 
the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  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

Last Call: (Revised IANA Considerations for DNSSEC) to Proposed Standard

2021-09-02 Thread The IESG 


The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document: - 'Revised IANA Considerations
for DNSSEC'
   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 2021-09-16. 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 changes the review requirements needed to get DNSSEC
   algorithms and resource records added to IANA registries.  It updates
   RFC 6014 to include hash algorithms for DS records and NSEC3
   parameters.  It also updates RFC 5155 and RFC 6014, which have
   requirements for DNSSEC algorithms, and updates RFC 8624 to say that
   algorithms that are described in RFCs that are not on standards track
   are only at the "MAY" level of implementation recommendation.  The
   rationale for these changes is to bring the requirements for DS
   records and for the hash algorithms used in NSEC3 in line with the
   requirements for all other DNSSEC algorithms.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-iana-cons/



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

Limited Additional Mechanisms for PKIX and SMIME (lamps) WG Virtual Meeting: 2021-09-13

2021-09-02 Thread IESG Secretary 
The Limited Additional Mechanisms for PKIX and SMIME (lamps) WG will hold
a virtual interim meeting on 2021-09-13 from 10:00 to 12:00 America/New_York 
(14:00 to 16:00 UTC).

Agenda:
LAMPS Discussion of PQC in certificates and S/MIME

Information about remote participation:
https://meetings.conf.meetecho.com/interim/?short=8955afa4-060b-4480-9986-07fe51113a0d

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

Last Call: (Update to the Object Identifier Registry for the PKIX Working Group) to Informational RFC

2021-09-02 Thread The IESG 


The IESG has received a request from the Limited Additional Mechanisms for
PKIX and SMIME WG (lamps) to consider the following document: - 'Update to
the Object Identifier Registry for the PKIX Working Group'
   as Informational RFC

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 2021-09-16. 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


   When the Public-Key Infrastructure using X.509 (PKIX) Working Group
   was chartered, an object identifier arc was allocated by IANA for use
   by that working group.  RFC 7299 describes the object identifiers
   that were assigned in that arc.  A small number of object identifiers
   that were assigned in RFC 4212 are not included in RFC 7299, and this
   document corrects that oversight.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc7299-update/



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

Request to Charter a New Working Group: DANE Authentication for Network Clients Everywhere (DANCE)

2021-09-02 Thread IESG Secretary 
The IESG has received a request to charter a new working group, DANE
Authentication for Network Clients Everywhere (DANCE). The proposed
charter, which is a work in progress, can be found here:



The charter will be discussed on the  mailing list,
which can be subscribed to here:



DANCE is the follow-on to the DANISH BOFs held at IETF 110 and 111. See:





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

Proposed Experiment for IETF 112: Moving the Plenary

2021-09-02 Thread IETF Chair 
Hi,

fully online meetings have a shorter length of day, which complicates
scheduling sessions to minimize conflicts, compared to an in-person
meeting with longer meeting days. The lack of travel arrangements also
reduces the pressure to hold all events in a single week. However,
scheduling all events in a single week both reduces the impact on
attendees' schedules and encourages cross-review of ideas. Past survey
data suggest both broad satisfaction with the current format and
concern about the number of scheduling conflicts.

The plenary offers a unique opportunity to maximize benefits and
minimize costs. This single event consumes an entire 2-3 hour slot of
the meeting week across all tracks. Moving the plenary outside the
meeting week thus opens up eight long slots that can be used to
schedule other meetings. The experiment will test the hypothesis that
the plenary is compelling enough to draw attendees independently of the
rest of the meeting.

*** Proposal

For IETF 112, the plenary will occur on the Wednesday before the meeting
week (3 November 2021), in the time slot of 13:30-15:00 UTC, or
14:30-16:00 Madrid time. At notable extremes, this begins at 05:30 in
San Francisco and ends at 02:00 in Sydney, with some of the less
popular hours over the Pacific.

*** Feedback

The IESG invites feedback to the IESG mailing list
(i...@ietf.org), especially if this proposal would change your ability
to attend the plenary. Such feedback would be most useful if received
within two weeks of the date of this email, as the IESG will then
finalize the decision whether to proceed with the experiment. Strong
feedback indicating the experiment would reduce the community’s ability
to attend the plenary might cause its cancellation.

*** Success Criteria

The IESG will evaluate the success of this experiment based on the
following criteria after its conclusion, in consultation with the
community.

* An improvement in survey responses reporting session conflicts
  compared to previous IETF online meetings

* Positive response to a new survey question about subjective
  satisfaction with the format change

* Elimination of a ninth track, and a reduction in formal conflicts in
  the final agenda compared to previous online meetings

* Little or no reduction in plenary attendance (< 15%) compared to other
  online plenaries in European time zones (i.e., IETF 108 and 110)

* The subjective experience of the IESG and Secretariat in attempting to
  minimize conflicts during IETF 112

This does not imply that all of these metrics must show
improvement for the experiment to be considered a success, or that
regression in any of them would indicate failure. The relative weights
of these considerations are a subject for IESG discussion and community
consultation.

Lars Eggert
IETF Chair, on behalf of the IESG


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

Formal IESG Teleconference WebEx and Dial-in Information: 9 September 2021

2021-09-02 Thread IESG Secretary 
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, September 9,
2021 at 07:00 US/Canada Pacific (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: September 9, 2021
Time: 07:00 US/Canada Pacific
  09:00 US/Canada Central
  10:00 US/Canada Eastern
  14:00 UTC
  15:00 United Kingdom
  16:00 Germany, France, Belgium
  17:00 Finland
  
---
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 944 708
---
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.

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

Reminder: IETF 112 Birds of a Feather (BOF) proposals due by 10 September

2021-09-02 Thread IETF Chair 
This is a friendly reminder that preliminary proposals for Birds-of-a-Feather 
(BOF) sessions during the upcoming IETF 112 meeting are due by 10 September.

If a proposal needs further work, the IESG and IAB will work with BOF 
proponents up until 24 September on revisions, but the initial proposal must be 
received by 10 September. 

IMPORTANT: BOF proposals are now made via the IETF Datatracker at 
https://datatracker.ietf.org/doc/bof-requests. Additional instructions for 
submitting a BOF proposal are available at https://ietf.org/how/bofs/.

Please also read https://www.rfc-editor.org/rfc/rfc5434, "Considerations for 
Having a Successful Birds-of-a-Feather Session", if you are not familiar with 
it.

BOFs are just one of a number of ways of bringing new work into the IETF. If 
you are considering a BOF request but you are unsure whether to submit it, 
please tell the IESG now by sending an email to i...@ietf.org, or speak to an 
individual Area Director (https://www.ietf.org/about/groups/iesg/members/) 
about your idea.

Thanks,
Lars Eggert
IETF Chair

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