[DNSOP] Éric Vyncke's Yes on draft-ietf-dnsop-glue-is-not-optional-08: (with COMMENT)

2023-06-06 Thread Éric Vyncke via Datatracker
Éric Vyncke has entered the following ballot position for
draft-ietf-dnsop-glue-is-not-optional-08: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to 
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-glue-is-not-optional/



--
COMMENT:
--

Thank you for the work put into this document. As a side note, I think it is
the first I-D that I read that uses the RFC 6761 'test.' ;-)

No specific comments but I wanted to thank two people in addition to the
authors.

Special thanks to Suzanne Woolf for the shepherd's detailed write-up including
the WG consensus and the justification of the intended status.

Other thanks to Tim Winters, the Internet directorate reviewer (at my request),
please consider this int-dir review:
https://datatracker.ietf.org/doc/review-ietf-dnsop-glue-is-not-optional-08-intdir-telechat-winters-2023-05-31/

Regards,

-éric



___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop


[DNSOP] dnsop - Update to a Meeting Session Request for IETF 117

2023-06-06 Thread IETF Meeting Session Request Tool



An update to a meeting session request has just been submitted by Tim
Wicinski, a Chair of the DNSOP Working Group.


-
Working Group Name: Domain Name System Operations
Area Name: Operations and Management Area
Session Requester: Tim Wicinski


Number of Sessions: 1
Length of Session(s): 2 Hours
Number of Attendees: 160
Conflicts to Avoid: 
 Chair conflict: dance add dprive dkim dbound2
 Technology overlap: quic dinrg lamps maprg 6man dhc regext intarea dnssd dmarc 
mimi

   


Participants who must be present:

Resources Requested:

Special Requests:
  
-


___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop


[DNSOP] Fwd: NomCom 2023 Call for Volunteers

2023-06-06 Thread Tim Wicinski
DNSOP/DPRIVE

Martin Thompson is chairing this year's version of the IETF Nominating
Committee. It's a good thing to volunteer, and I can speak strongly on the
fact that 10+ years of volunteering, and I have not been selected(*).

tim

(8) Now that I've said that

-- Forwarded message -
From: NomCom Chair 2023 
Date: Mon, Jun 5, 2023 at 7:50 PM
Subject: NomCom 2023 Call for Volunteers
To: IETF Announcement List 


The IETF Nominating Committee (NomCom) appoints people to fill the open
slots on the IETF LLC, IETF Trust, the IAB, and the IESG.  Ten voting
members for the NomCom are selected from a pool of volunteers.  A large
pool of volunteers helps make the process work better.

CLICK HERE TO VOLUNTEER: https://datatracker.ietf.org/nomcom/volunteer

NomCom activity is expected to start in July and run through to November.
The goal is to do the bulk of the work at IETF 117 and 118, with
supplemental conference calls between those times.  Remote participation
will be supported.

The NomCom activities involve collecting requirements from the community,
reviewing candidate responses, reviewing feedback from community members
about candidates, interviewing candidates, and nominating a slate of
candidates.

RFC 8713 details the NomCom process.  With the recent publication of RFC
9389, this is the first year of new qualification criteria, after a few
years of trials.  People qualify for NomCom participation in one of three
ways: attendance at IETF meetings (online or virtual), service as a working
group chair or secretary, or publication of IETF RFCs.

https://datatracker.ietf.org/accounts/profile/ lists your eligibility, but
you can still volunteer even if that says "No".  You can also volunteer by
sending me an email.

Within the next week or two, I will add more details on the timeline and
the selection process.

Thank you!
Martin Thomson
nomcom-chair-2...@ietf.org

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


[DNSOP] Domain Name System Operations (dnsop) WG Virtual Meeting: 2023-06-20

2023-06-06 Thread IESG Secretary
The Domain Name System Operations (dnsop) WG will hold a virtual interim
meeting on 2023-06-20 from 20:00 to 21:00 Europe/Amsterdam (18:00 to 19:00
UTC).

Agenda:
## Agenda

### Administrivia

* Agenda Bashing, Blue Sheets, etc,  5 min


### Current Working Group Business

*   DNS Terminology and definition "lame delegation"
- https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8499bis/
- WG Chairs, Paul Hoffman and Kazunori Fujiwara, 55 min
- Chairs Action:


Information about remote participation:
https://meetings.conf.meetecho.com/interim/?short=7e86a1ea-71f7-40c0-8c34-eb16a1a57a6e



--
A calendar subscription for all dnsop meetings is available at
https://datatracker.ietf.org/meeting/upcoming.ics?show=dnsop

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop


Re: [DNSOP] DNSOP WG Interim June 2023 planning: draft-ietf-dnsop rfc8499bis and lame delegation

2023-06-06 Thread Benno Overeinder

Dear WG,

From the Doodle poll, we have selected the following day and time:

Tuesday June 20, 18:00-19:00 UTC.

We will post the interim meetecho details to the mailing list later today.

Best regards,

Suzanne, Tim and Benno


On 30/05/2023 17:31, Benno Overeinder wrote:

Hi WG,

Gentle reminder to fill in the doodle to schedule the interim in June.

Will extend the poll until Thursday, June 1!


-- Benno


On 24/05/2023 16:11, Benno Overeinder wrote:

Dear WG,

As mentioned earlier on the mailing list, the chairs are planning an 
interim meeting in June to discuss the three options on how to proceed 
with draft-ietf-dnsop-rfc8499bis wrt. lame delegation:


1) Stick with the current text in the document – the original 
definition from RFC8499 plus a note that "These early definitions do 
not match the current use of the term "lame delegation", but there is 
no consensus on what a lame delegation is."
A possible follow-up to this is for someone to start a WG consensus 
document on "lame", which can update 8499bis.
2) We still find a rough consensus on the definition proposed in the 
"Meaning of lame delegation" email thread, and the WG can agree that 
this is a definition useful to DNS engineers/operators.
3) Withdraw the document from WGLC so we can add definitions.  Do not 
propose any new terms and definitions at this stage if we choose this 
option.



Please fill in the Doodle poll to settle on a day and time:

- https://doodle.com/meeting/participate/id/az7Z5AOb

The options for the time slots are a compromise for 
CEST/EDT/PDT/AEST/JST.


We will close the Doodle poll at the end of Tuesday 30 May.

Best regards,

Suzanne, Tim and Benno

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop


___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop


--
Benno J. Overeinder
NLnet Labs
https://www.nlnetlabs.nl/

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop