RE: [Ianaplan] last call and IESG processing summary for draft-ietf-ianaplan-icg-response

Milton L Mueller <> Wed, 07 January 2015 18:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9941A1A1A20; Wed, 7 Jan 2015 10:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Pc-slkvc2rUb; Wed, 7 Jan 2015 10:11:56 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 51D161A1A9A; Wed, 7 Jan 2015 10:05:51 -0800 (PST)
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id t07I5RMg023900 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Jan 2015 13:05:27 -0500
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 7 Jan 2015 13:05:26 -0500
Received: from ([]) by ([]) with mapi id 15.00.0847.030; Wed, 7 Jan 2015 13:05:26 -0500
From: Milton L Mueller <>
To: Jari Arkko <>
Subject: RE: [Ianaplan] last call and IESG processing summary for draft-ietf-ianaplan-icg-response
Thread-Topic: [Ianaplan] last call and IESG processing summary for draft-ietf-ianaplan-icg-response
Date: Wed, 7 Jan 2015 18:05:26 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68, 1.0.33, 0.0.0000 definitions=2015-01-07_08:2015-01-07,2015-01-07,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1501070188
Cc: "Ianaplan@Ietf. Org" <>, "" <>, "" <>, IETF-Discussion list <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 07 Jan 2015 18:12:10 -0000

> -----Original Message-----
> > I am afraid this is incorrect. The WG consensus said that it was not
> necessary to specify the exact supplemental agreements to be negotiated -
> that this should be left to the IAOC. My understanding of the document, and
> my basis for agreeing to rough consensus, was that the IAOC could pursue
> these or not, as it saw fit.
> I think we may be trying to say the same thing. The document discusses what
> needs to be achieved. The WG's opinion of what is necessary for the
> transition. But the WG did not want to put into the document (a) detailed
> contractual language as that is an IAOC task or (b) additional requests
> beyond the ones listed in the document. However, the IAOC certainly is in
> charge of all specific contract language already, and will be also in this case.
> They will also consider any additional elements that they think will be useful
> or needed, as they will always.

Great, this is my understanding, too. So you should modify the assessment of my comments because they say "The recommendation also states that the advocated actions are in line with the current IANAPLAN draft. The IAOC has taken this input for consideration. It should be noted that these recommendations were discussed as part of the WG deliberations, however. The WG consensus did not agree with the recommendations."

That's the part that is not correct. 

The WG consensus was that there should not be detailed contractual language in the document, as you say. It did not, however, foreclose or negate the suggestions I made for future IAOC requests, it simply said that they should not be specified or required by the IANAPlan document. The IAOC retains the ability to request them if it thinks it appropriate in the near term negotiations. 

I hope you understand the distinction. It was crucial to achieving rough consensus.