[regext] Re: normative language and references in draft-ietf-regext-delete-bcp

> -Original Message- > From: Andrew Newton (andy) > Sent: Thursday, October 17, 2024 2:10 PM > To: James Galvin > Cc: regext@ietf.org > Subject: [EXTERNAL] [regext] Re: normative language and references in draft- > ietf-regext-delete-bcp > > Caution: This email originated from outside th

[regext] Re: I-D Action: draft-ietf-regext-rdap-geofeed-08.txt

Hi. This version incorporates Gavin’s shepherd feedback. Thanks, Jasdip From: internet-dra...@ietf.org Date: Friday, October 18, 2024 at 3:40 AM To: i-d-annou...@ietf.org Cc: regext@ietf.org Subject: [regext] I-D Action: draft-ietf-regext-rdap-geofeed-08.txt Internet-Draft draft-ietf-regext-r

[regext] Re: Question regarding client identifiers and password requirement of RFC-5730

Thank you Scott! Victor, CEO & founder of Namefi , tokenizing domain names for trading, DeFi and future Internet. https://namefi.io On Fri, Oct 18, 2024 at 5:18 AM Hollenbeck, Scott wrote: > RFC 8807 describes login improvements. There haven’t been ay other > attempts to ext

[regext] Re: Call for agenda items IETF 121

Greatly appreciated, James, for your detailed discussion. Yes, we are aware of RFC-9154 and are honored to have a response from you, the author of it, and expressed your interest. We are thinking about proposing two main things to further secure the transfer: 1. Using a cryptography public-key aut

[regext] Re: Question regarding client identifiers and password requirement of RFC-5730

RFC 8807 describes login improvements. There haven’t been ay other attempts to extend the protocol that I’m aware of. Scott From: Victor Zhou Sent: Thursday, October 17, 2024 5:37 PM To: regext@ietf.org Cc: Hollenbeck, Scott Subject: [EXTERNAL] Question regarding client identifiers and pas

[regext] Re: normative language and references in draft-ietf-regext-delete-bcp

On 10/18/24 08:15, Hollenbeck, Scott wrote: Would you please add something like "It was noted that RFC 2026 permits BCPs to describe what is believed to be the best way to perform some operations or IETF process function" to the end of the new text. Scott Good addition regarding the WG dis

[regext] Re: I-D Action: draft-ietf-regext-rdap-x-media-type-02.txt

On 10/17/24 08:05, Gould, James wrote: Andy, I'll provide a full review, but upon my initial review draft-ietf-regext-rdap-x-media-type-02 still doesn't support the Extension Version Identifier in draft-ietf-regext-rdap-versioning, following the ABNF: extension-version-identifier = identifie

[regext] Re: I-D Action: draft-ietf-regext-rdap-x-media-type-02.txt

Andy, I'll pull my prior feedback and recommendations to help with the updates make draft-ietf-regext-rdap-versioning work with draft-ietf-regext-rdap-x-media-type compatible. I believe we can really streamline the two drafts by working together to merge them. Expanding the meta-data in the v

[regext] I-D Action: draft-ietf-regext-rdap-geofeed-08.txt

Internet-Draft draft-ietf-regext-rdap-geofeed-08.txt is now available. It is a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF. Title: An RDAP Extension for Geofeed Data Authors: Jasdip Singh Tom Harrison Name:draft-ietf-regext-rdap-geofeed-08.