Registration policies (was: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc))

S Moonesamy <sm+ietf@elandsys.com> Thu, 17 July 2014 20:05 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BBD1B27CC for <ietf@ietfa.amsl.com>; Thu, 17 Jul 2014 13:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kxhhpQYPqvVI for <ietf@ietfa.amsl.com>; Thu, 17 Jul 2014 13:05:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5621B27C6 for <ietf@ietf.org>; Thu, 17 Jul 2014 13:05:05 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.134.51]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s6HK4kUn012704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Jul 2014 13:04:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1405627499; x=1405713899; bh=Fr8t5F3gX4nePWiGrfPjRc4IRDUv6uPHSgfFDNsxqx8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=igHHGpktN9n3IHv7Ju2rrupRBhYH1FSJTFUnezvoldn8o3kdtcFJ0CN3vvac3KA8R s0Q0ktV5o2N5SGF6av2XYrwDfmKu1IDAVXE+d58egnTabIjdT5EYk6+qRi4b8X0eXN tvWysp+FcohfukffbehiKX9o93CfX6xymEMez4ZI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1405627499; x=1405713899; i=@elandsys.com; bh=Fr8t5F3gX4nePWiGrfPjRc4IRDUv6uPHSgfFDNsxqx8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1lEVW5CP+d3T/kgN+7+Qf0+BDiDS01PLiW7NNOCA7xpPJ91B2mrkpai8VWXfs5cu9 VwOqmKzJoRkbzl80rJtrARjBiJrrWVXv8LA7j22DBpu76FEomPoUk8pQoKyqeKyb22 8XBPPcawyP4Gbevi7pXwZ56YK8B12G9Ba+JHLhRQ=
Message-Id: <6.2.5.6.2.20140717120908.0ddd9a80@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Jul 2014 12:58:19 -0700
To: Barry Leiba <barryleiba@computer.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Registration policies (was: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc))
In-Reply-To: <CALaySJ+_R=kxdf3E94kA=+S2gHaht9vSrkPQYdREnsqdWLJGkw@mail.g mail.com>
References: <20140714164212.22974.20340.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140716100922.0ceba268@resistor.net> <53C70443.8020709@dcrocker.net> <6.2.5.6.2.20140716161255.0ac7a6f0@elandnews.com> <53C71991.3040909@bbiw.net> <6.2.5.6.2.20140716200958.0cb6d4c8@elandnews.com> <CAC4RtVB895qQam48dqpG7CX+YCxPp0-5Er8j_=NR-YexTQRtmA@mail.gmail.com> <6.2.5.6.2.20140717072736.0ddb14c0@elandnews.com> <CALaySJ+_R=kxdf3E94kA=+S2gHaht9vSrkPQYdREnsqdWLJGkw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qaDk04COPcMOeiLesKCQTE53CwA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2014 20:05:08 -0000

Hi Barry,

I changed the subject line as this is not related to the proposed charter.

At 11:59 17-07-2014, Barry Leiba wrote:
>It has, and there's no problem.  The IESG has objected to Independent
>Stream documents creating registries with policies of Expert Review or
>Specification required, because those commit the IESG to appointing a
>Designated Expert, with all the management necessary for that.
>
>But other registration policies don't commit anyone to anything, and
>an Independent Stream document creating a registry that requires IETF
>Stream RFCs in oder to register in it... is perfectly fine.  Yes, the
>IESG has discussed this in relation to other Independent Stream
>documents.

Section 4 of RFC 5226 is about creating a registry.  My assumption 
would be that it would require some IETF action or IESG approval as 
it is committing the IETF to do some work in future.  My experience 
of an IETF Review is that it is a higher barrier than going through a 
review in the Independent Stream:

   (i)  I would have to find an Area Director to sponsor the draft; or

   (ii) Get a working group to adopt the draft, and go through the 
IETF process.

It does not seem fair to me to create and populate a registry and ask 
other people to put in much more effort than I would have to put in 
when requesting an assignment.

I'll respect the decision of the IESG.

Regards,
S. Moonesamy