From nobody Sun Oct 2 15:18:34 2016 Return-Path: X-Original-To: architecture-discuss@ietfa.amsl.com Delivered-To: architecture-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0154D12B03D for ; Sun, 2 Oct 2016 15:18:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 JTotVKwb9Cvn for ; Sun, 2 Oct 2016 15:18:31 -0700 (PDT) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A6CE12B025 for ; Sun, 2 Oct 2016 15:18:31 -0700 (PDT) Received: by mail-qt0-x230.google.com with SMTP id m5so16798761qtb.3 for ; Sun, 02 Oct 2016 15:18:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=g8Mvp3UFC+tcYRbXGy30q7/GVFqK3Ru0/7bQ0HkUZDQ=; b=mngvNZp1jrvA8jXbqC8k3AvpcnkYjxaGXQnrO9vfn7ITxjdXARwsWSxP8zDeElvSgQ MOPsJucEnA7J3B7knbA//ZRrhf8HuTRc6viJo90dErbXHH+josC87kf5T2x0ydEz0FBh wvUNzOfi6rt0kIii1fByZ0xqk/zbq8FEKm/AIf3jhIB/lifzM8S6v2NEuEATHhMNGEXN zRU5xVXkIzo3g0eN8HPjjPUSMicfoRnbF3w+thIrAPPGWyZYWBHzhjRpq8/K4nHcqIQt XFj47tfLITPF/RVt9gfKoCkNK0f6ZfvyMrWEJW9QglPL9wtRybBdi6t75vxpweWvTMT/ 95Yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=g8Mvp3UFC+tcYRbXGy30q7/GVFqK3Ru0/7bQ0HkUZDQ=; b=m6Ch15xyCfk2AObCiGZo5Rs9W85uu0bdfXiWsufIAhdmSLa5h9ZgyWJwtm5JHyYsb/ ZeJGn+D1kd2PJwKqiyocpXBigKTbmebYCsC7PVom2J3DNgORE+7KaDhAadWkLLO+ttAg uiasGw4Kits3CdXb39zrWudwxVhnebDdMIB8qn3VA1Hnxdgf1O4DWpUX7n6Uu5pdawyP 7WBzgLG0IeSXHYNvWUBZMviVusDuw6OWkFyc8FncxwxryTzh8Kvq6nBMISN3lrzdDOKz 0PePGm8RFjJMZfV47MheqGHDdQvqQO0WdZ/y23K3Qdi8lcDTewJwpWeIFyTkU4YgQr99 payw== X-Gm-Message-State: AA6/9RmNLd8tDAR1MRaTIZGbcw/tOSXPYeSE2rkSZKWehODl/F7c99s6facT01o4itJ/nDaIDEzBhZ4RRp2Vog== X-Received: by 10.237.55.232 with SMTP id j95mr18303622qtb.131.1475446710123; Sun, 02 Oct 2016 15:18:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.104.37 with HTTP; Sun, 2 Oct 2016 15:18:29 -0700 (PDT) In-Reply-To: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com> References: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com> From: Abdussalam Baryun Date: Mon, 3 Oct 2016 00:18:29 +0200 Message-ID: To: architecture-discuss@ietf.org, IAB Content-Type: multipart/alternative; boundary=001a11447d2e0ac5e4053de93514 Archived-At: Subject: Re: [arch-d] Call for Comment: (IETF ICANN Root Zone Evolution Review Committee Appointment Procedures) X-BeenThere: architecture-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: open discussion forum for long/wide-range architectural issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 22:18:33 -0000 --001a11447d2e0ac5e4053de93514 Content-Type: text/plain; charset=UTF-8 I have a question, Has this been reviewed by few? it is good to know, I don't see only one author but not sure of the answer. If some reviewed, could I know about the number, however, if it is zero, I recommend that I don't review until some one either than the author reviews, AB On Wed, Sep 28, 2016 at 8:04 PM, IAB Executive Administrative Manager < execd@iab.org> wrote: > This is an announcement of an IETF-wide Call for Comment on > draft-iab-rzerc-01. > > The document is being considered for publication as an Informational RFC > within the IAB stream, and is available for inspection at: > https://datatracker.ietf.org/doc/draft-iab-rzerc/ > > The Call for Comment will last until 2016-10-26. Please send comments to > architecture-discuss@ietf.org and iab@iab.org. > > > Abstract > > This memo outlines the process by which the IETF makes an appointment > to the ICANN Root Zone Evolution Review Committee (RZERC). > > --001a11447d2e0ac5e4053de93514 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I have a question,

Has this been reviewed = by few? =C2=A0it is good to know, I don't see only one author but not s= ure of the answer. If some reviewed, could I know about the number, however= , if it is zero, I recommend that I don't review until some one either = than the author reviews,

On Wed, Sep 28, 2016 at 8:0= 4 PM, IAB Executive Administrative Manager <execd@iab.org> wrote= :

This is an announcement of an IETF-wide= Call for Comment on
draft-iab-rzerc-01.

The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection at:
https://datatracker.ietf.org/doc/draft-iab-rze= rc/

The Call for Comment will last until 2016-10-26. Please send comments to architecture-discuss@ietf.= org and iab@iab.org.

Abstract

=C2=A0 =C2=A0This memo outlines the process by which the IETF makes an appo= intment
=C2=A0 =C2=A0to the ICANN Root Zone Evolution Review Committee (RZERC).

--001a11447d2e0ac5e4053de93514-- From nobody Sun Oct 2 15:40:26 2016 Return-Path: X-Original-To: architecture-discuss@ietfa.amsl.com Delivered-To: architecture-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74F8612B029 for ; Sun, 2 Oct 2016 15:40:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.719 X-Spam-Level: X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 ZQkik_o3mfzz for ; Sun, 2 Oct 2016 15:40:21 -0700 (PDT) Received: from mail-qt0-f181.google.com (mail-qt0-f181.google.com [209.85.216.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85DE512B03D for ; Sun, 2 Oct 2016 15:40:21 -0700 (PDT) Received: by mail-qt0-f181.google.com with SMTP id f6so17350606qtd.2 for ; Sun, 02 Oct 2016 15:40:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=2ytzXY0u1ECwYCYcYmGLzkAi6pxKeaH2hiWCiMuVgf8=; b=Fxb8gMrgYQNYo+kFl8E/gnjMIDsIdDvBpc08HmGHFZC0Bqp6llcUk9cfNDVvV59VVa yGIRBeJVH8fX7TBi2RfarpW4EiaZqs6np8rP0n+VA2cUdzs4dNDlKKOspuCmMorIajGr L6aCNkMYlvq+Esr2+mCL4B7Sc5H9ggLXAAsbv8GfWQKtQ2lcwX4UffnyLJrbKbQYbF/d ZssXzvPYqKWATvA3llbJi49lkiUPcx6zkmsBVoUg0SRsLmNYw/HIt0+Kxr58qIY/p+TI oLbYPb/cJOsmMSD/fb3N9s63KtWlR+BBKU7qpBMs3iqnMr6AS0K9vU54Twfqx1RZE8yF QqGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=2ytzXY0u1ECwYCYcYmGLzkAi6pxKeaH2hiWCiMuVgf8=; b=HeJzk2Y6KP262779aSPc23szSlonQ7KP9zH/+5RqdKhhAZIZNGlPA9WpcPvCjzujs6 q6BjLaQDQ38/Qttf++Rkzu1P5RxAyTvoTIr/1kQOYt4wd7TW8xeShCuGt7+HOLapIBVC MNsZ7BPriLcndhxhjmBUMIXw0GB4+vssxZp1mGITQKMIdx08E88rJqL7G3zFvOQKz4Tz OOC4nyEAY/DETj2tf0u4XHvJogzXWB8xucADp3pWtGq7U/YVJOUSXw9DL7xoPliOSiIc g1H9G+xH6g26zqrrRISQuCBxLeaIvcgkfjOIqp4xu0RbrXZUXRMYRWLyBYIRNpUplGHU Bang== X-Gm-Message-State: AA6/9RmmGwXVFVEQjNnRjZL2C/JjgSeoiZ43IsxRZ/EQvQwMQ7oaDjWDgQjuzPk3+UhwfsYojWVq61KsXjhNbw== X-Received: by 10.237.55.232 with SMTP id j95mr18361162qtb.131.1475447960529; Sun, 02 Oct 2016 15:39:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.104.37 with HTTP; Sun, 2 Oct 2016 15:39:20 -0700 (PDT) In-Reply-To: References: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com> From: Abdussalam Baryun Date: Mon, 3 Oct 2016 00:39:20 +0200 Message-ID: To: architecture-discuss@ietf.org, IAB Content-Type: multipart/alternative; boundary=001a11447d2e927811053de97f23 Archived-At: Subject: Re: [arch-d] Call for Comment: (IETF ICANN Root Zone Evolution Review Committee Appointment Procedures) X-BeenThere: architecture-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: open discussion forum for long/wide-range architectural issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 22:40:24 -0000 --001a11447d2e927811053de97f23 Content-Type: text/plain; charset=UTF-8 AB> As in the draft-introduction, there is only one reference which is very very very important to this draft. However, it states: As stipulated in [RZERC-Charter] the IETF is called upon to name a delegate to the committee. AB> the reference never mentions IETF, also never mentions IAB, therefore, how it stipulates that IETF to name the delegate? I am sorry if my questions are strange, I think I may not be understanding some thing!!!! AB On Mon, Oct 3, 2016 at 12:18 AM, Abdussalam Baryun < abdussalambaryun@gmail.com> wrote: > I have a question, > Has this been reviewed by few? it is good to know, I don't see only one > author but not sure of the answer. If some reviewed, could I know about the > number, however, if it is zero, I recommend that I don't review until some > one either than the author reviews, > > AB > > On Wed, Sep 28, 2016 at 8:04 PM, IAB Executive Administrative Manager < > execd@iab.org> wrote: > >> This is an announcement of an IETF-wide Call for Comment on >> draft-iab-rzerc-01. >> >> The document is being considered for publication as an Informational RFC >> within the IAB stream, and is available for inspection at: >> https://datatracker.ietf.org/doc/draft-iab-rzerc/ >> >> The Call for Comment will last until 2016-10-26. Please send comments to >> architecture-discuss@ietf.org and iab@iab.org. >> >> >> Abstract >> >> This memo outlines the process by which the IETF makes an appointment >> to the ICANN Root Zone Evolution Review Committee (RZERC). >> >> > --001a11447d2e927811053de97f23 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

AB> As in the=C2=A0draft-introduction, there is on= ly one reference which is very very very important to this draft. However, = it states:

As stipulated in [RZERC-Charter] the IETF is called

upon to name a delegate to the committee.

= AB> the reference never mentions IETF, also never mentions IAB, therefor= e, how it stipulates that IETF to name the delegate?

I am sorry if my= questions are strange, I think I may not be understanding some thing!!!!

On Mon, Oct 3, 2016 at 12:18 AM, Abdussalam Baryun = <abdussalambaryun@gmail.com> wrote:

I have a question,

Has= this been reviewed by few? =C2=A0it is good to know, I don't see only = one author but not sure of the answer. If some reviewed, could I know about= the number, however, if it is zero, I recommend that I don't review un= til some one either than the author reviews,

On Wed, Sep 28, 2016 at 8:04 PM, IAB Execut= ive Administrative Manager <execd@iab.org> wrote:
This is an announcement of an IETF-wide Call for Comment on
draft-iab-rzerc-01.

The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection at:
https://datatracker.ietf.org/doc/draft-iab-rze= rc/

The Call for Comment will last until 2016-10-26. Please send comments to architec= ture-discuss@ietf.org and iab@iab.org.

Abstract

=C2=A0 =C2=A0This memo outlines the process by which the IETF makes an appo= intment
=C2=A0 =C2=A0to the ICANN Root Zone Evolution Review Committee (RZERC).

--001a11447d2e927811053de97f23-- From nobody Sun Oct 2 16:08:12 2016 Return-Path: X-Original-To: architecture-discuss@ietfa.amsl.com Delivered-To: architecture-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7CE212B0FA for ; Sun, 2 Oct 2016 16:08:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 sJQNLJc0mjAz for ; Sun, 2 Oct 2016 16:08:09 -0700 (PDT) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0395F128E19 for ; Sun, 2 Oct 2016 16:08:09 -0700 (PDT) Received: by mail-qt0-x233.google.com with SMTP id 38so73215537qte.1 for ; Sun, 02 Oct 2016 16:08:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QP4M1ivqrz/6qnsvw6+meeIE9N/hWc06BWFZr0uLybM=; b=aKLY/vbpPT9t2ALB5hFHyr6Ryr9b4pYh6+7s3qmIdt7hJA79TIwojDfs6gA4vceeHF DeL9YCdJsy5smVMbeUsKSYkWOohc8jeqD/YBOvzFQwQv2H0v+I0Er0ioojpxR/MCQ/oI 1+1leexmQ/RouXAjGRpsr66/70stNHZVB1mMbUUtqahW4Icr5dtVM6oU507x18bOQ6rW PIR06Py9o6J3kbc7Mqk3VCAbw3ago83aPqgQE72es05ndVrWHX0Jr/MrJroWl5yUIUVR EE7cC9JD08ym2F3lsAoJB906apG5Giy278rxE1tkuE0bgcGq5fDGXO3sDDNBQRa3b8JX J/ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QP4M1ivqrz/6qnsvw6+meeIE9N/hWc06BWFZr0uLybM=; b=NAsi32EZmAmyhpv/SK7RR+f4PT4/SsierwrEJSHqDfbhNN0nSsz/OK3nzlPAHY1aKE K6gwOAg+lXr3El0fVjB1eQMkdFqoJMZ600ZI4uNzCRLgWtq7KVz6kRJwwwTl+98FIz3x U1xqMht7RnhYHUqxC7sgd2lLa+w6ZNPJpfhdyvUDfuzceW2p6zLJTMd9mwcCXcXd5m+S Zo7Q/brsdP8QUH265QMYxpIAPSuQpZjhK16yz/Gm83skxy8Uj3GXsTdDBYyEnz+2EKCo DXM179qurVHWjKrGYcMTeH05eOsYf55inMdTrsrnvhcCbVWxDRGr7f/sNVsp+/rscqGO WKMg== X-Gm-Message-State: AA6/9RkJoTVU0Hr/kOLp5qdkDxs9v77wHa/jgOafVmENlt0lLWn4q9Y9ULJ0KukwUh1fWQ== X-Received: by 10.200.40.53 with SMTP id 50mr18849289qtq.86.1475449688131; Sun, 02 Oct 2016 16:08:08 -0700 (PDT) Received: from ?IPv6:2601:181:c003:1360:a555:183:d606:4a6d? ([2601:181:c003:1360:a555:183:d606:4a6d]) by smtp.gmail.com with ESMTPSA id h126sm15916101qkd.18.2016.10.02.16.08.07 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 02 Oct 2016 16:08:07 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Suzanne Woolf In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C117F89197@eusaamb107.ericsson.se> Date: Sun, 2 Oct 2016 19:08:05 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <661DAD19-DAD4-4A10-8668-94946FDDF672@gmail.com> References: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com> <58d46edf-e59c-7ee2-46c6-facbf5ab6919@cs.tcd.ie> <2DD56D786E600F45AC6BDE7DA4E8A8C117F89197@eusaamb107.ericsson.se> To: Daniel Migault X-Mailer: Apple Mail (2.2104) Archived-At: Cc: "iab@iab.org" , "architecture-discuss@ietf.org" Subject: Re: [arch-d] [IAB] Call for Comment: (IETF ICANN Root Zone Evolution Review Committee Appointment Procedures) X-BeenThere: architecture-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: open discussion forum for long/wide-range architectural issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 23:08:11 -0000 Hi Daniel, Thanks for this review. > On Sep 29, 2016, at 2:55 PM, Daniel Migault = wrote: >=20 > Hi,=20 >=20 > Reading the draft, here are my thoughts. >=20 > Maybe we should have some rules that should prevent someone to be the = ICANN Root Zone Evolution Review Committee (RZERC) member for multiple = organizations. I would expect something like this with of course a more = appropriated and a better wording: >=20 > The candidate for representing IETF at the RZERC a candidate MUST = disclose 1) the organizations he is already a RZERC member, 2) the = organizations processing a RZERC member application and 3) the relation = toward the organization represented at RZERC. In addition, when = appointed by the IETF, he MUST NOT apply to represent another = organization at RZERC without an explicit agreement from the IAB/IETF.=20= This is a reasonable point. The IAB appoints a lot of people to a lot of = different roles, and commonly this specific question (what other roles a = person has, and whether those are compatible with being the IETF/IAB=E2=80= =99s appointee to a particular role) isn=E2=80=99t specified=E2=80=94 = it=E2=80=99s left to the discretion of the IAB.=20 > I do not either see any procedure to revoke a member. Suppose the = nominated person does not respond to emails or is not representing the = IETF/IAB views. My understanding is that we will have to wait its term = ends. Maybe we should provide some ways so the IAB can revoke the = nomination. =20 IMO this is covered by Sec. 3.5, =E2=80=9CMid-term Vacancies=E2=80=9D. = It would be within the discretion of the IAB to decide a vacancy existed = under the conditions you describe. I think both of your questions are worth considering, however. Thanks = for raising them. > Evaluation of the load seems to me a bit premature for now and the = activity may vary upon time.=20 I quite hope the load will be pretty minimal. It seems to me that = changes that are within scope for the RZERC shouldn=E2=80=99t occur = often. But others may expect otherwise. best, Suzanne > On 28/09/16 19:04, IAB Executive Administrative Manager wrote: >> This is an announcement of an IETF-wide Call for Comment on=20 >> draft-iab-rzerc-01. >>=20 >> The document is being considered for publication as an Informational=20= >> RFC within the IAB stream, and is available for inspection at: >> https://datatracker.ietf.org/doc/draft-iab-rzerc/ >>=20 >> The Call for Comment will last until 2016-10-26. Please send comments=20= >> to architecture-discuss@ietf.org and iab@iab.org. >>=20 >>=20 >> Abstract >>=20 >> This memo outlines the process by which the IETF makes an = appointment >> to the ICANN Root Zone Evolution Review Committee (RZERC). >>=20 >>=20 >=20 From nobody Mon Oct 3 08:49:44 2016 Return-Path: X-Original-To: architecture-discuss@ietfa.amsl.com Delivered-To: architecture-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3A51293D8 for ; Mon, 3 Oct 2016 08:49:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.617 X-Spam-Level: X-Spam-Status: No, score=-5.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 yC4WkHGnAItr for ; Mon, 3 Oct 2016 08:49:41 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72F741293E3 for ; Mon, 3 Oct 2016 08:49:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A6D401E55CF; Mon, 3 Oct 2016 08:42:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MSAnL4P7mz3S; Mon, 3 Oct 2016 08:42:33 -0700 (PDT) Received: from [10.0.1.6] (c-73-189-62-172.hsd1.ca.comcast.net [73.189.62.172]) by c8a.amsl.com (Postfix) with ESMTPSA id 80C8E1E55BE; Mon, 3 Oct 2016 08:42:33 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Cindy Morgan In-Reply-To: Date: Mon, 3 Oct 2016 08:49:20 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com> To: Abdussalam Baryun X-Mailer: Apple Mail (2.2104) Archived-At: Cc: IAB , architecture-discuss@ietf.org Subject: Re: [arch-d] Call for Comment: (IETF ICANN Root Zone Evolution Review Committee Appointment Procedures) X-BeenThere: architecture-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: open discussion forum for long/wide-range architectural issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 15:49:42 -0000 Hi AB, Please see inline. > On Oct 2, 2016, at 3:39 PM, Abdussalam Baryun = wrote: >=20 > AB> As in the draft-introduction, there is only one reference which is = very very very important to this draft. However, it states: >=20 > As stipulated in [RZERC-Charter] the IETF is called >=20 > upon to name a delegate to the committee. >=20 >=20 >=20 > AB> the reference never mentions IETF, also never mentions IAB, = therefore, how it stipulates that IETF to name the delegate? The RZERC charter = (https://www.icann.org/en/system/files/files/revised-rzerc-charter-08aug16= -en.pdf) does not use the IETF acronym; however, section IV states that = "The Committee shall be comprised of 9 committee members," and that one of those is "The = Chair or delegate of the Internet Engineering Task Force." One of the responsibilities in the IAB's charter (see RFC 2850) is to = act as representative of the interests of the IETF in technical liaison = relationships with other organizations, thus the IAB makes the = appointment on behalf of the IETF. > I am sorry if my questions are strange, I think I may not be = understanding some thing!!!! >=20 > AB >=20 >=20 > On Mon, Oct 3, 2016 at 12:18 AM, Abdussalam Baryun = wrote: > I have a question, > Has this been reviewed by few? it is good to know, I don't see only = one author but not sure of the answer. If some reviewed, could I know = about the number, however, if it is zero, I recommend that I don't = review until some one either than the author reviews, The document was reviewed by the IAB before it went out for community = review. Best regards, Cindy >=20 > AB >=20 > On Wed, Sep 28, 2016 at 8:04 PM, IAB Executive Administrative Manager = wrote: > This is an announcement of an IETF-wide Call for Comment on > draft-iab-rzerc-01. >=20 > The document is being considered for publication as an Informational = RFC > within the IAB stream, and is available for inspection at: > https://datatracker.ietf.org/doc/draft-iab-rzerc/ >=20 > The Call for Comment will last until 2016-10-26. Please send comments = to > architecture-discuss@ietf.org and iab@iab.org. >=20 >=20 > Abstract >=20 > This memo outlines the process by which the IETF makes an = appointment > to the ICANN Root Zone Evolution Review Committee (RZERC). >=20 >=20 >=20 > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss From nobody Tue Oct 4 22:43:13 2016 Return-Path: X-Original-To: architecture-discuss@ietfa.amsl.com Delivered-To: architecture-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2A9D126FDC for ; Tue, 4 Oct 2016 22:43:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 sNJjk5ZP8rEo for ; Tue, 4 Oct 2016 22:43:09 -0700 (PDT) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22C9126B6D for ; Tue, 4 Oct 2016 22:43:08 -0700 (PDT) Received: by mail-qk0-x234.google.com with SMTP id t7so210660137qkh.2 for ; Tue, 04 Oct 2016 22:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mUHC+qRvQUfGb7z1+10n3ru+j0mp95C1ynOmUE5o+vs=; b=P5N15MXpb6F9xcIPh6tcYpAp65IEZgIYBMQMMlnjxz2N5/ax7VgZnt2lLWBrouJjAq nfRvSpequjEY3ip9hwkAxiwfju84WKBoyX0j14Yvw+WEnFUC1MFdgOFFH99eZtYyKcdR dWB3lt4TgEhC9Zh5aH9witdVcCMt5RAriaKdYZdTZpRXTYdUTgwUgmUtMzqdZopXSMF4 KMAL5mX3Wm0SY0OqJHUPZHmVdESNcE4+hBP6jtV76pENo8jYZZi9pVPuoDd9WtQlxgxo 3qArj6dvFMnmQ0OAaf9Et1se5DVxk2cwndXQYXy6sqE9N7MFouP29JoTt4k/YFaY5GzY GQRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mUHC+qRvQUfGb7z1+10n3ru+j0mp95C1ynOmUE5o+vs=; b=dnCmvNNDTqxAGoZWgcnRWyNOcBzsL1r0YGQko6q5sfBihQMxwjk3hgO5SguLpiS0pF CCHaIWVGwux04vL/KifYtB620ObhbyIcTu6aGi7Ha1VvU03zhQdlYtoj2z8sX9SYi3Xf hJOCZpvq9ovDMKCbfz7L0+eERj04KZAspPcBeCEM861Sh1UCEVErtYx6RPqefnJA3bk7 4gS9vN+gLeAQlemXQnxgZ7Oxr9JXh4qtHF+QsTSb8GdwSRfKUxJ2pUW+A4difa4FAbms bSzT9bIyptcdySFiYP/rH3waX+XBbmytuCV0qG4yvbPWuLr8j2JAoYUFSVTthMqXwEfj gyNQ== X-Gm-Message-State: AA6/9RnTqwhlPt/cscCI515SBNI5pobkx+UZkrtZCTPKX4kBrWmYWZdZpw6I/jecca7U5VYAoY2B9Sm0ZGEbiA== X-Received: by 10.55.82.195 with SMTP id g186mr6949683qkb.220.1475646187910; Tue, 04 Oct 2016 22:43:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.104.37 with HTTP; Tue, 4 Oct 2016 22:43:07 -0700 (PDT) In-Reply-To: References: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com>

From: Abdussalam Baryun Date: Wed, 5 Oct 2016 07:43:07 +0200 Message-ID: To: Cindy Morgan Content-Type: multipart/alternative; boundary=001a114a6a4ed83ea9053e17a681 Archived-At: Cc: IAB , architecture-discuss@ietf.org Subject: Re: [arch-d] Call for Comment: (IETF ICANN Root Zone Evolution Review Committee Appointment Procedures) X-BeenThere: architecture-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: open discussion forum for long/wide-range architectural issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 05:43:11 -0000 --001a114a6a4ed83ea9053e17a681 Content-Type: text/plain; charset=UTF-8 Hi Cindy, Ok, then the Abstract needs to clarify that IETF is appointing its delegate, as saying that IAB appoints the IETF delegate in the committee. The Abstract mentions as that IETF appoints the delegate, but it is the IAB. You may think that they are the same because they work together but it is confusing for me. Also in the introduction: As stipulated in [RZERC-Charter] the IETF is called upon to name a delegate to the committee. AB> change to> As stipulated in [RZERC-Charter] the IETF is called upon to name its delegate to the committee. AB> in section 3.1> This appointment will be renewable for up to three additional one-year terms. AB> change to> This appointment can be renewable for up to three additional one-year terms. AB> My new question is:- AB> Why the appointment is one year only and renewable? I think we need to know the appointment period for other delegates, is it one year, if yes then ok we must do the same but if other delegates have more than one, I prefer we agree on something below 4 years and above one. Regards, AB On Mon, Oct 3, 2016 at 5:49 PM, Cindy Morgan wrote: > Hi AB, > > Please see inline. > > > On Oct 2, 2016, at 3:39 PM, Abdussalam Baryun < > abdussalambaryun@gmail.com> wrote: > > > > AB> As in the draft-introduction, there is only one reference which is > very very very important to this draft. However, it states: > > > > As stipulated in [RZERC-Charter] the IETF is called > > > > upon to name a delegate to the committee. > > > > > > > > AB> the reference never mentions IETF, also never mentions IAB, > therefore, how it stipulates that IETF to name the delegate? > > The RZERC charter (https://www.icann.org/en/system/files/files/revised- > rzerc-charter-08aug16-en.pdf) does not use the IETF acronym; however, > section IV states that "The Committee shall > be comprised of 9 committee members," and that one of those is "The Chair > or delegate of the Internet Engineering Task Force." > > One of the responsibilities in the IAB's charter (see RFC 2850) is to act > as representative of the interests of the IETF in technical liaison > relationships with other organizations, thus the IAB makes the appointment > on behalf of the IETF. > > > I am sorry if my questions are strange, I think I may not be > understanding some thing!!!! > > > > AB > > > > > > On Mon, Oct 3, 2016 at 12:18 AM, Abdussalam Baryun < > abdussalambaryun@gmail.com> wrote: > > I have a question, > > Has this been reviewed by few? it is good to know, I don't see only one > author but not sure of the answer. If some reviewed, could I know about the > number, however, if it is zero, I recommend that I don't review until some > one either than the author reviews, > > The document was reviewed by the IAB before it went out for community > review. > > Best regards, > Cindy > > > > > AB > > > > On Wed, Sep 28, 2016 at 8:04 PM, IAB Executive Administrative Manager < > execd@iab.org> wrote: > > This is an announcement of an IETF-wide Call for Comment on > > draft-iab-rzerc-01. > > > > The document is being considered for publication as an Informational RFC > > within the IAB stream, and is available for inspection at: > > https://datatracker.ietf.org/doc/draft-iab-rzerc/ > > > > The Call for Comment will last until 2016-10-26. Please send comments to > > architecture-discuss@ietf.org and iab@iab.org. > > > > > > Abstract > > > > This memo outlines the process by which the IETF makes an appointment > > to the ICANN Root Zone Evolution Review Committee (RZERC). > > > > > > > > _______________________________________________ > > Architecture-discuss mailing list > > Architecture-discuss@ietf.org > > https://www.ietf.org/mailman/listinfo/architecture-discuss > > --001a114a6a4ed83ea9053e17a681 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi Cindy,

Ok, then the Abstr= act needs to clarify that IETF is appointing its delegate, as saying that I= AB appoints the IETF delegate in the committee. The Abstract mentions as th= at IETF appoints the delegate, but it is the IAB. You may think that they a= re the same because they work together but it is confusing for me.

Also in the introduction:

As stipulated in [RZERC-Charter] the = IETF is called

upon to name a delegate to the committee.

AB> change= to>

<= font face=3D"Courier" size=3D"2">As stipulated in [RZER= C-Charter] the IETF is called

upon t= o name=C2=A0its delegate to the committee.

AB> in section 3.1><= /p>

This appointment will be renewable for up to three additional= one-year terms.

AB> change to>

This appointment=C2=A0can be renewable for up to three additional one-= year terms.

AB> = My new question is:-

AB> Why the appointment is one = year only and renewable?

I think we need to know the appoi= ntment period for other delegates, is it one year, if yes then ok we must d= o the same but if other delegates have more than one, I prefer we agree on = something below 4 years and above one.

Regards,

On Mon, Oct 3, 2016 at 5:49 PM, Cindy Morgan <cmorgan@ams= l.com> wrote:

Hi AB,

Please see inline.

> On Oct 2, 2016, at 3:39 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>
> AB> As in the draft-introduction, there is only one reference which= is very very very important to this draft. However, it states:
>
> As stipulated in [RZERC-Charter] the IETF is called
>
> upon to name a delegate to the committee.
>
>
>
> AB> the reference never mentions IETF, also never mentions IAB, the= refore, how it stipulates that IETF to name the delegate?

The RZERC charter (https://www.icann.org/en/system/files/files/revised-rzerc-c= harter-08aug16-en.pdf) does not use the IETF acronym; however, section = IV states that "The Committee shall
be comprised of 9 committee members," and that one of those is "T= he Chair or delegate of the Internet Engineering Task Force."

One of the responsibilities in the IAB's charter (see RFC 2850) is to a= ct as representative of the interests of the IETF in technical liaison rela= tionships with other organizations, thus the IAB makes the appointment on b= ehalf of the IETF.

> I am sorry if my questions are strange, I think I may not be understan= ding some thing!!!!
>
> AB
>
>
> On Mon, Oct 3, 2016 at 12:18 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote: > I have a question,
> Has this been reviewed by few?=C2=A0 it is good to know, I don't s= ee only one author but not sure of the answer. If some reviewed, could I kn= ow about the number, however, if it is zero, I recommend that I don't r= eview until some one either than the author reviews,

The document was reviewed by the IAB before it went out for communit= y review.

Best regards,
Cindy

>
> AB
>
> On Wed, Sep 28, 2016 at 8:04 PM, IAB Executive Administrative Manager = <execd@iab.org> wrote:
> This is an announcement of an IETF-wide Call for Comment on
> draft-iab-rzerc-01.
>
> The document is being considered for publication as an Informational R= FC
> within the IAB stream, and is available for inspection at:
> https://datatracker.ietf.org/doc/draft-= iab-rzerc/
>
> The Call for Comment will last until 2016-10-26. Please send comments = to
> architecture-discuss@= ietf.org and iab@iab.org.
>
>
> Abstract
>
>=C2=A0 =C2=A0 This memo outlines the process by which the IETF makes an= appointment
>=C2=A0 =C2=A0 to the ICANN Root Zone Evolution Review Committee (RZERC)= .
>
>
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@= ietf.org
> https://www.ietf.org/mailman/lis= tinfo/architecture-discuss

--001a114a6a4ed83ea9053e17a681-- From nobody Tue Oct 4 23:38:17 2016 Return-Path: X-Original-To: architecture-discuss@ietfa.amsl.com Delivered-To: architecture-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBE7C129541 for ; Tue, 4 Oct 2016 23:38:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 EZElvc-xN3Zw for ; Tue, 4 Oct 2016 23:38:12 -0700 (PDT) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0137129504 for ; Tue, 4 Oct 2016 23:38:12 -0700 (PDT) Received: by mail-it0-x234.google.com with SMTP id o19so155907782ito.1 for ; Tue, 04 Oct 2016 23:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EKaJP1Rfji+gqdHhyUugKGAWaCbZoGipdjNKGqOVBfI=; b=bWP/RfZ/a9kLpAhisDuYeFv56W7EYi7mMErT684M0rXDg0j2EWAYdkCxjdICyLBfE7 sVmZ33/lhu9rTWnI+GoHgZ2S4EQNHenvF0Xbb3QdCwcgI/zsMU0obOb3mh3lyTVXaiwp shrnNjfEiwKxGcHVx7RG+drWrv6a3Z8E4AQc3BhH+nxWa+oFhQb5uKSXbhRlCFqCvUt0 aqTxghvsYQJP3MHqfXbSoaaxh9A73DE4QRJ4VG5GXSFxrNe2pH4KSlBE2Hzqv1bz6AoT /bc0u334CxKiMOPP7aQO7wHUh31wiBhy7wOyuqo3Ut/MsmLY9ZaW0XfXYlqydYomoMvb Frcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=EKaJP1Rfji+gqdHhyUugKGAWaCbZoGipdjNKGqOVBfI=; b=g6azb3EAIN3dy9awPkuJqNdH31N8xMsXdx1VcO3qLcvKZVAxsb5J7aLEFlO/DwAU1C v1jo5K5eK7DYTFc6wEOCKQ1wZTua5qskZBokxZgcYI327jvvAZYpIezsdHBiWlSUVCSd NLn8rBT6pKBH0KO+qXpeJNAUJDPFWrKDlRCsr88RYcYkTjRmDb5ttu48Z0096HfXBXkx L6wppZ+lr5D7CGblVOZCoQ7hYIYGRWpCLDXaSCKbMMxmVRjJGQAKoKQ9UxvQqWxB6k1H YAd97uOatKVpCVDmfh+Wwydjq1BEiZnLVGGVxxskzFd9kF5rsRqMBUzuWceJ/b7t08c/ yP2w== X-Gm-Message-State: AA6/9RleYGO7XJ2zfjXmdQnXnR5UaNZJIQDbIqFRxjlxLdsZ4UgtKqfH8CEDKe0NVe+pUTIwd5/VkUdPmYgekw== X-Received: by 10.107.164.103 with SMTP id n100mr8068056ioe.35.1475649491880; Tue, 04 Oct 2016 23:38:11 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 10.107.170.70 with HTTP; Tue, 4 Oct 2016 23:38:11 -0700 (PDT) In-Reply-To: <661DAD19-DAD4-4A10-8668-94946FDDF672@gmail.com> References: <147508589098.16615.14694976330501894410.idtracker@ietfa.amsl.com> <58d46edf-e59c-7ee2-46c6-facbf5ab6919@cs.tcd.ie> <2DD56D786E600F45AC6BDE7DA4E8A8C117F89197@eusaamb107.ericsson.se> <661DAD19-DAD4-4A10-8668-94946FDDF672@gmail.com> From: Daniel Migault Date: Wed, 5 Oct 2016 08:38:11 +0200 X-Google-Sender-Auth: zYbsZ5D-ArTuJVV3Z585xh9vAn4 Message-ID: To: Suzanne Woolf Content-Type: multipart/alternative; boundary=001a1141c956c6d078053e186bff Archived-At: Cc: "iab@iab.org" , "architecture-discuss@ietf.org" Subject: Re: [arch-d] [IAB] Call for Comment: (IETF ICANN Root Zone Evolution Review Committee Appointment Procedures) X-BeenThere: architecture-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: open discussion forum for long/wide-range architectural issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 06:38:16 -0000 --001a1141c956c6d078053e186bff Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Suzanne, Thank you for the response. It addresses my comments. BR, Daniel On Mon, Oct 3, 2016 at 1:08 AM, Suzanne Woolf wrote: > Hi Daniel, > > Thanks for this review. > > > On Sep 29, 2016, at 2:55 PM, Daniel Migault > wrote: > > > > Hi, > > > > Reading the draft, here are my thoughts. > > > > Maybe we should have some rules that should prevent someone to be the > ICANN Root Zone Evolution Review Committee (RZERC) member for multiple > organizations. I would expect something like this with of course a more > appropriated and a better wording: > > > > The candidate for representing IETF at the RZERC a candidate MUST > disclose 1) the organizations he is already a RZERC member, 2) the > organizations processing a RZERC member application and 3) the relation > toward the organization represented at RZERC. In addition, when appointed > by the IETF, he MUST NOT apply to represent another organization at RZERC > without an explicit agreement from the IAB/IETF. > > This is a reasonable point. The IAB appoints a lot of people to a lot of > different roles, and commonly this specific question (what other roles a > person has, and whether those are compatible with being the IETF/IAB=E2= =80=99s > appointee to a particular role) isn=E2=80=99t specified=E2=80=94 it=E2=80= =99s left to the > discretion of the IAB. > > > I do not either see any procedure to revoke a member. Suppose the > nominated person does not respond to emails or is not representing the > IETF/IAB views. My understanding is that we will have to wait its term > ends. Maybe we should provide some ways so the IAB can revoke the > nomination. > > IMO this is covered by Sec. 3.5, =E2=80=9CMid-term Vacancies=E2=80=9D. It= would be within > the discretion of the IAB to decide a vacancy existed under the condition= s > you describe. > > I think both of your questions are worth considering, however. Thanks for > raising them. > > > Evaluation of the load seems to me a bit premature for now and the > activity may vary upon time. > > I quite hope the load will be pretty minimal. It seems to me that changes > that are within scope for the RZERC shouldn=E2=80=99t occur often. But ot= hers may > expect otherwise. > > > best, > Suzanne > > > On 28/09/16 19:04, IAB Executive Administrative Manager wrote: > >> This is an announcement of an IETF-wide Call for Comment on > >> draft-iab-rzerc-01. > >> > >> The document is being considered for publication as an Informational > >> RFC within the IAB stream, and is available for inspection at: > >> https://datatracker.ietf.org/doc/draft-iab-rzerc/ > >> > >> The Call for Comment will last until 2016-10-26. Please send comments > >> to architecture-discuss@ietf.org and iab@iab.org. > >> > >> > >> Abstract > >> > >> This memo outlines the process by which the IETF makes an appointmen= t > >> to the ICANN Root Zone Evolution Review Committee (RZERC). > >> > >> > > > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss > --001a1141c956c6d078053e186bff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi Suzanne,

Thank you for the= response. It addresses my comments.

BR,

Daniel

On Mon, Oc= t 3, 2016 at 1:08 AM, Suzanne Woolf <suzworldwide@gmail.com> wrote:

Hi Daniel,

Thanks for this review.

> On Sep 29, 2016, at 2:55 PM, Daniel Migault <daniel.migault@ericsson.com> wrote:
>
> Hi,
>
> Reading the draft, here are my thoughts.
>
> Maybe we should have some rules that should prevent someone to be the = ICANN Root Zone Evolution Review Committee (RZERC) member for multiple orga= nizations.=C2=A0 I would expect something like this with of course a more a= ppropriated and a better wording:
>
> The candidate for representing IETF at the RZERC a candidate MUST disc= lose 1) the organizations he is already a RZERC member, 2) the organization= s processing a RZERC member application and 3) the relation toward the orga= nization represented at RZERC. In addition, when appointed by the IETF, he = MUST NOT apply to represent another organization at RZERC without an explic= it agreement from the IAB/IETF.

This is a reasonable point. The IAB appoints a lot of people to a lo= t of different roles, and commonly this specific question (what other roles= a person has, and whether those are compatible with being the IETF/IAB=E2= =80=99s appointee to a particular role) isn=E2=80=99t specified=E2=80=94 it= =E2=80=99s left to the discretion of the IAB.

> I do not either see any procedure to revoke a member. Suppose the nomi= nated person does not respond to emails or is not representing the IETF/IAB= views. My understanding is that we will have to wait its term ends. Maybe = we should provide some ways so the IAB can revoke the nomination.

IMO this is covered by Sec. 3.5, =E2=80=9CMid-term Vacancies=E2=80= =9D. It would be within the discretion of the IAB to decide a vacancy exist= ed under the conditions you describe.

I think both of your questions are worth considering, however. Thanks for r= aising them.

> Evaluation of the load seems to me a bit premature for now and the act= ivity may vary upon time.

I quite hope the load will be pretty minimal. It seems to me that ch= anges that are within scope for the RZERC shouldn=E2=80=99t occur often. Bu= t others may expect otherwise.

best,
Suzanne

> On 28/09/16 19:04, IAB Executive Administrative Manager wrote:
>> This is an announcement of an IETF-wide Call for Comment on
>> draft-iab-rzerc-01.
>>
>> The document is being considered for publication as an Information= al
>> RFC within the IAB stream, and is available for inspection at:
>> https://datatracker.ietf.org/doc/dra= ft-iab-rzerc/
>>
>> The Call for Comment will last until 2016-10-26. Please send comme= nts
>> to architecture-d= iscuss@ietf.org and iab@iab.org.
>>
>>
>> Abstract
>>
>>=C2=A0 =C2=A0This memo outlines the process by which the IETF makes= an appointment
>>=C2=A0 =C2=A0to the ICANN Root Zone Evolution Review Committee (RZE= RC).
>>
>>
>

_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.= org
https://www.ietf.org/mailman/listinf= o/architecture-discuss

--001a1141c956c6d078053e186bff--