Fwd: [Ianaplan] Last Call: <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries) to Informational RFC
Jari Arkko <jari.arkko@piuha.net> Tue, 16 December 2014 12:25 UTC
Return-Path: <jari.arkko@piuha.net>
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 DA2271A1AA6 for <ietf@ietfa.amsl.com>; Tue, 16 Dec 2014 04:25:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 gvkp4AHTZj0D for <ietf@ietfa.amsl.com>; Tue, 16 Dec 2014 04:25:36 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 59EA51A1AE0 for <ietf@ietf.org>; Tue, 16 Dec 2014 04:25:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 58FB12CC61; Tue, 16 Dec 2014 14:25:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8VVo3IYUxrF; Tue, 16 Dec 2014 14:25:31 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3B9A82CCAE; Tue, 16 Dec 2014 14:25:30 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Fwd: [Ianaplan] Last Call: <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries) to Informational RFC
From: Jari Arkko <jari.arkko@piuha.net>
X-Priority: 3 (Normal)
Date: Tue, 16 Dec 2014 06:35:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <78FD53B6-2950-41AB-A3D4-2CE2C2E6BECB@piuha.net>
References: <GLEAIDJPBJDOLEICCGMNMEDJCPAA.rhill@hill-a.ch>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/X6sTSGJF5HeWMJrCmiBoFSB_niM
Cc: rhill@hill-a.ch
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: Tue, 16 Dec 2014 12:25:39 -0000
This is the third forwarded message. Begin forwarded message: > From: "Richard Hill" <rhill@hill-a.ch> > Subject: RE: [Ianaplan] Last Call: <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries) to Informational RFC > Date: 14 Dec 2014 03:56:58 EST > To: "Jari Arkko" <jari.arkko@piuha.net> > Cc: ietf@ietf.org, iesg@ietf.org > Reply-To: rhill@hill-a.ch > > Why don't my messages get posted in the IETF list archive? > > I see JFC's reply to my message, but not my message. > > Is there some blocking or filtering going on that prevents my messages from > being posted? > > Best, > Richard > >> -----Original Message----- >> From: Richard Hill [mailto:rhill@hill-a.ch] >> Sent: jeudi, 11. décembre 2014 12:39 >> To: Jari Arkko >> Cc: ietf@ietf.org; iesg@ietf.org >> Subject: RE: [Ianaplan] Last Call: >> <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the >> Internet Coordination Group Request for Proposals on the IANA protocol >> parameters registries) to Informational RFC >> >> >> Dear Jari, >> >> Thank you for this. I do understand the consensus call is a >> judgement call. But, as I understand RFC 7282, a justification >> should be provided for the judgement call. And that is what I am >> requesting. >> >> Regarding the "sheperd writeup", I have requested some changes, see: >> >> http://www.ietf.org/mail-archive/web/ianaplan/current/msg01415.html >> >> Regarding the IESG, that body requested comments, and that is why >> I submitted my comments to the IETF list. >> >> Best, >> Richard >> >>> -----Original Message----- >>> From: Jari Arkko [mailto:jari.arkko@piuha.net] >>> Sent: mercredi, 10. décembre 2014 11:28 >>> To: rhill@hill-a.ch >>> Cc: ietf@ietf.org; iesg@ietf.org >>> Subject: Re: [Ianaplan] Last Call: >>> <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the >>> Internet Coordination Group Request for Proposals on the IANA protocol >>> parameters registries) to Informational RFC >>> >>> >>> Richard, >>> >>>> On 27 November, I requested that the co-chairs provide a >>> justification for >>>> the conclusion that rough consensus has been achieved, see: >>>> >>>> http://www.ietf.org/mail-archive/web/ianaplan/current/msg01402.html >>>> >>>> The requested justification has not yet been provided. >>> >>> Calling the consensus is a judgment call. For what it is worth, I >>> have been >>> quite satisfied with the chairs and the document shepherd reading the >>> opinions of the group. Their thoughts have been discussed in the thread >>> “draft-ietf-ianaplan-icg-response moving to next step”, see the thread >>> beginning at >>> >>> http://www.ietf.org/mail-archive/web/ianaplan/current/msg01401.html >>> >>> See in particular this e-mail: >>> >>> http://www.ietf.org/mail-archive/web/ianaplan/current/msg01406.html >>> >>> as well as the shepherd writeup: >>> >>> >> https://datatracker.ietf.org/doc/draft-ietf-ianaplan-icg-response/ > shepherdwriteup/ > > Also, for information, the IESG has not yet considered this draft. But they > will. Right now it's in IETF last call, the outcome of which will first be > evaluated by the responsible AD, in this case me. And then by the IESG > as a whole. At that point the IESG will determine if there have been any > process or other issues that need consideration or action. > > Jari > >
- RE: [Ianaplan] Last Call: <draft-ietf-ianaplan-ic… Richard Hill
- Re: [Ianaplan] Last Call: <draft-ietf-ianaplan-ic… Jari Arkko
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… John Levine
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Brian E Carpenter
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Eliot Lear
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Jari Arkko
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… John Levine
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Eliot Lear
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Brian E Carpenter
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Eliot Lear
- Re: [Ianaplan] Last Call: <draft-ietf-ianaplan-ic… Jari Arkko
- Re: [Ianaplan] Last Call: <draft-ietf-ianaplan-ic… Jefsey
- Re: [Ianaplan] Last Call: <draft-ietf-ianaplan-ic… Jari Arkko
- Fwd: [Ianaplan] Last Call: <draft-ietf-ianaplan-i… Jari Arkko
- Fwd: [Ianaplan] Last Call: <draft-ietf-ianaplan-i… Jari Arkko
- Fwd: [Ianaplan] Last Call: <draft-ietf-ianaplan-i… Jari Arkko
- Fwd: [Ianaplan] Last Call: <draft-ietf-ianaplan-i… Jari Arkko
- Re: Fwd: [Ianaplan] Last Call: <draft-ietf-ianapl… Andrew Sullivan
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Jari Arkko
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Eliot Lear
- Re: Last Call: <draft-ietf-ianaplan-icg-response-… Jari Arkko