[regext] Alexey Melnikov's No Objection on draft-ietf-regext-org-11: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 24 October 2018 12:42 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 338B9128C65; Wed, 24 Oct 2018 05:42:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-regext-org@ietf.org, Pieter Vandepitte <pieter.vandepitte@dnsbelgium.be>, regext-chairs@ietf.org, pieter.vandepitte@dnsbelgium.be, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154038495219.6871.12749859323071546693.idtracker@ietfa.amsl.com>
Date: Wed, 24 Oct 2018 05:42:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/k72Su1bhRug3l6TMfVcNder-6xc>
Subject: [regext] Alexey Melnikov's No Objection on draft-ietf-regext-org-11: (with COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2018 12:42:32 -0000

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 https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-regext-org/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This is a well written document, but I am concerned about missing references
for various syntactic elements that you use. Having proper references will save
developers time and will improve interoperability. The same issue in at least 3
places in the document, I am mentioning the first one below.

In 4.1.1:

   o  An OPTIONAL <org:reason> element that may be provided when an
      object cannot be provisioned.  If present, this element contains
      server-specific text to help explain why the object cannot be
      provisioned.  This text MUST be represented in the response
      language previously negotiated with the client; an OPTIONAL "lang"

Please either point to the Language tag RFC 5646/BCP 47 or point to another RFC
which defines the "lang" attribute.

      attribute MAY be present to identify the language if the
      negotiated value is something other than the default value of
      "en"(English).

4.1.2.  EPP <info> Command

   o  Zero to two <org:postalInfo> elements that contain postal-address
      information.  Two elements are provided so that address
      information can be provided in both internationalized and
      localized forms; a "type" attribute is used to identify the two
      forms.  If an internationalized form (type="int") is provided,
      element content MUST be represented in a subset of Unicode in the
      range U+0020 - U+007E.  If a localized form (type="loc") is
      provided, element content MAY be represented in unrestricted UTF-
      8.  The <org:postalInfo> element contains the following child
      elements:

 [snip]

         +  An <org:cc> element that contains the organization's country
            code.

Please add the correct reference for country codes. I believe you want to
reference alpha-2 country codes from ISO 3166. (There are also alpha-3 country
codes.)

Alternative you can just reference a section from RFC 5733.

   o  An OPTIONAL <org:email> element that contains the organization's
      email address.

Please point to specific format for email addresses (there is RFC 5321 format
and RFC 5322 format. They are not identical.) Alternative you can just
reference a section from RFC 5733.

   o  An OPTIONAL <org:url> element that contains the URL to the website
      of the organization.

Please add a reference to RFC 3986 or to one of HTTP RFCs if you want to
restrict this to https: or http:

One possible way of addressing all of the above is to add a few sentences with
references to the "Conventions Used in This Document" section.