Re: [regext] milestones for recently adopted documents

Patrick Mevzek <> Mon, 04 May 2020 15:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 112953A0A09 for <>; Mon, 4 May 2020 08:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=XJgHJ6JE; dkim=pass (2048-bit key) header.b=i7KI3gRa
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id z6VFmtyEASwc for <>; Mon, 4 May 2020 08:03:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 933BA3A0A08 for <>; Mon, 4 May 2020 08:03:21 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id E0173560 for <>; Mon, 4 May 2020 11:03:20 -0400 (EDT)
Received: from imap22 ([]) by compute3.internal (MEProxy); Mon, 04 May 2020 11:03:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=s18Y8SjVYDapCgydKPMyKxCMHKBVeMt j4An2x09FBgE=; b=XJgHJ6JEjAfacRWCDDgqd0PZrCPrFECHNlAmDdzfH73r5m2 PPz1r8gTzne8WzviX6i9MAzN1bh1FSAoMk/sgWvG91dY31HKTvIC9l7zSDFHCDV9 mPTNJscDSBRklHL2yNUTE7YC9cBtZkkYTk9XlWqDPqNLkQb5lhggECd1+JPdAtIh 48t6ukI6KNkgPpAkbZrsFmjuH8m16Yw7MjAMuj3np2it1M8tU/kIkKmSZCNCiauO 0y6MWuqF+c1O3n9fcm96c+j5PnBUeQSR4WuLtUYCg+H6kj/fRGtmXkji8HquVC6z W4Duq+GgHYcPhU60o6cZ3x2D5MCwCnailKlW+Bg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=s18Y8S jVYDapCgydKPMyKxCMHKBVeMtj4An2x09FBgE=; b=i7KI3gRavngDM/KIiqrrxi EYG7Bc5UZJ8OqapiXz/YyiV/Aom/mfTB77BGrsGU5bFzbRaBx/J9kAHgkmQgYK1O 7oTW6cQuB1DfL6+RUWiOropo2Ck4LyAWCkVHlVbmjyITmNE3j8uwZGJ021W4idcO 8yl6sPpjdz+WaM9IKBGu/OUQwqfYmBDBtPrv1VTwC0ea5GfmujZ6iKM09w5gUFa/ cm1Bw3cSQEEZrj3k0AB6p1oQJaS9nnI5R0eoNedC7rBew7rRlefpVocLH4DI8fe5 a2YOK4Z5SVUR5n8wjd2cx7YfShniEdBP2a3xcbQvPImAlvoLrv9F+1cjudTXLKQA ==
X-ME-Sender: <xms:uC6wXtNgl-R74pGjQaEF6IKor9YuBzSduRg3S94bQR5m7gitp53HV95ziFk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrjeeggdejiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdfrrghtrhhitghkucfovghviigvkhdfuceophhmseguohht rghnuggtohdrtghomheqnecuggftrfgrthhtvghrnhepteekgfevjedttdffgefhieehhf dtgefhleeltdevveetleevvdevjeduieetgeevnecuffhomhgrihhnpehivghtfhdrohhr ghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpmh esughothgrnhgutghordgtohhm
X-ME-Proxy: <xmx:uC6wXkPBGjPbHnTopZ-CKrPgr4-xJ-3keGrfsN1Z3jwkrxzRyLc2BQ> <xmx:uC6wXnRoddE2i2dBWFBStZ1TKP5-zX7TZnN_ohJC_WECmwXcHWp4eQ> <xmx:uC6wXuC6xJy27gxDPAD8Rg6SlhUdHL-8XiC7GkSukuIU1yCjjf608w> <xmx:uC6wXl35L64t0eRSbI-PhySvs60gBpBRpqFw3JyqYmJyc7gV5Jm35w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id F01526680073; Mon, 4 May 2020 11:03:19 -0400 (EDT)
X-Mailer: Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-351-g9981f4f-fmstable-20200421v1
Mime-Version: 1.0
Message-Id: <>
In-Reply-To: <>
References: <> <> <>
Date: Mon, 04 May 2020 10:02:59 -0500
From: Patrick Mevzek <>
Content-Type: text/plain
Archived-At: <>
Subject: Re: [regext] milestones for recently adopted documents
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 May 2020 15:03:27 -0000


On Mon, May 4, 2020, at 08:04, Roger D Carney wrote:
>  Good Morning,
>  Thanks for your review and comments Patrick.
>  For the questions you brought up:

If possible, please also see the points I raised earlier in:

>  DDOS/SRS down - This draft is not intended to support emergency notifications.

Ok but then the draft says:

       MUST be present and contains the reason behind the maintenance;
       values SHOULD either be 'planned' or 'emergency'.

emergency is listed as a value...

>  <maint:description> - Draft will be updated to match text to schema. 
> Simply, we limited size to restrict someone from writing a book, is 
> there an alternative size people would suggest?

I see no reason to limit it at the protocol level.
And even if you do limit it, I do not think that "MUST NOT exceed 1024 bit." is the adequate description for a string of characters.

  Patrick Mevzek