Dear WG participants,
ART ADs were discussing workload and a possible swap or change who
manages which WGs. Apparently I have the biggest number of WGs per ART
AD. So Alissa has agreed to become the Responsible AD for RegExt. I
don't think this would make much practical difference, as I will still
Hi Gustavo,
> On 5 Oct 2016, at 02:21, Gustavo Lozano wrote:
>
> This I-D is included in
> draft-ietf-regext-launchphase (standards track) as a normative reference,
> and is
> my understanding that is possible to include an informational RFC as a
> normative reference in an standards track docum
To followup on my previous reply:
On 5 Oct 2016, at 08:16, Patrik Fältström wrote:
>> Based on your comments, it appears that this
>> I-D should be an informational document, and I have no objections for making
>> this I-D an informational document. This I-D is included in
>> draft-ietf-regext-l
Hi,
On Thu, Nov 10, 2016, at 07:44 AM, Rik Ribbers wrote:
> First of all thanks Antoin for your excellent reply. lots of +1
> in there.
>
>> On 9 Nov 2016, at 19:47, Antoin Verschuren wrote:
>>
>> Jim has asked for this before, with little to no response to call
>> consensus to have this draft p
Alexey Melnikov has entered the following ballot position for
draft-ietf-regext-launchphase-06: No Objection
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
Alexey Melnikov has entered the following ballot position for
draft-ietf-regext-rdap-object-tag-04: Discuss
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
Hi Scott,
On Mon, Jul 30, 2018, at 1:33 PM, Hollenbeck, Scott wrote:
> > -Original Message-
(snip)
> >
> > This is a fine document, but I have one possible issue that I would like
> > to quickly discuss before recommending approval of this document:
> >
> > Looking at the example in Secti
On Mon, Jul 30, 2018, at 5:24 PM, Hollenbeck, Scott wrote:
> > -Original Message-
> > From: Alexey Melnikov
> > Sent: Monday, July 30, 2018 12:21 PM
> > To: Hollenbeck, Scott ; i...@ietf.org
> > Cc: draft-ietf-regext-rdap-object-...@ietf.org; Gould, Jame
On Mon, Jul 30, 2018, at 11:03 PM, Andy Newton wrote:
> On Mon, 2018-07-30 at 17:34 +0100, Alexey Melnikov wrote:
> > On Mon, Jul 30, 2018, at 5:24 PM, Hollenbeck, Scott wrote:
> > >
> > > >
> > > > -Original Message-
> > > > From: A
Alexey Melnikov has entered the following ballot position for
draft-ietf-regext-org-11: No Objection
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
. Please see my
> feedbacks inline with [Linlin].
>
> Regards,
> Linlin
> Linlin Zhou
>
> From: Alexey Melnikov
> Date: 2018-10-24 20:42
> To: The IESG
> CC: regext-chairs; pieter.vandepitte; draft-ietf-regext-org; regext
> Subject: [regext] Alexey Melnikov'
Hi,
On Tue, Mar 26, 2019, at 5:11 PM, Mario Loffredo wrote:
> >
> > 3. JSContact - based on the DISPATCH meeting on Monday, it is unclear
> > if JSContact will be moving forward in the IETF.
Speaking as an ART AD, I think I am happy to move quickly on this work if
enough interest is expressed in
Hi James,
Just replying to 1 point below:
> On 23 Jan 2020, at 21:29, Gould, James wrote:
>
>2) In the same section:
>
> : OPTIONAL plain text password that is case sensitive,
> has a minimum length of 6 characters, and has a maximum length
> that is up to server
Hi James,
On Mon, Jan 27, 2020, at 1:12 PM, Gould, James wrote:
> Roman,
>
> In thinking about a little bit more, I believe the ABNF for the
> element value needs to be simplified and made more consistent
> with the other ABNF with:
>
> app = name SP version
> name = 1*VCHAR
> version =
Hi James,
On Thu, Jan 23, 2020, at 9:29 PM, Gould, James wrote:
> Alexey,
[snip]
>
> Thank you for this document. I have several small comments similar
> to what was
> raised by Roman and Ben:
>
> 1) In 4.1:
>
>: OPTIONAL client user agent that identifies th
jgo...@verisign.com
>
>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> Verisign.com <http://verisigninc.com/>
>
> On 1/27/20, 9:02 AM, "Alexey Melnikov" wrote:
>
> Hi James,
>
> On Thu, Jan 23, 2020, at 9:29 PM,
Hi David,
Sorry for the delay with reviewing this.
On 02/05/2025 18:35, David Dong via RT wrote:
Dear Alexey Melnikov, Darrel Miller (cc: regext WG),
Following up on this; as the designated experts for the Structured Syntax
Suffixes registry, can you review the proposed registration in
Best regards,
David Dong
IANA Services Sr. Specialist
On Wed May 07 13:50:30 2025, jasd...@arin.net wrote:
Hi Alexey,
Thank you for your review. Please see our comments below.
Regards,
Jasdip & Tom
From: Alexey Melnikov
Date: Tuesday, May 6, 2025 at 9:44 AM
To: drafts-expert-re
Alexey Melnikov has entered the following ballot position for
draft-ietf-regext-login-security-07: Discuss
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
Alexey Melnikov has entered the following ballot position for
draft-ietf-regext-login-security-08: No Objection
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
20 matches
Mail list logo
