Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP

Cullen Jennings <fluffy@cisco.com> Mon, 31 January 2011 17:36 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03D193A6977; Mon, 31 Jan 2011 09:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.583
X-Spam-Level:
X-Spam-Status: No, score=-110.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E+HgLik5gDUG; Mon, 31 Jan 2011 09:36:49 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 256033A67B6; Mon, 31 Jan 2011 09:36:49 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADeDRk2rR7H+/2dsb2JhbACkeXOiOpsQhU4EhROHDoNF
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 31 Jan 2011 17:39:50 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0VHdmgZ020743; Mon, 31 Jan 2011 17:39:49 GMT
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <C96C2999.2BB2C%michelle.cotton@icann.org>
Date: Mon, 31 Jan 2011 10:39:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DF650F5-A5DA-4AB6-9553-40FE38CE6175@cisco.com>
References: <C96C2999.2BB2C%michelle.cotton@icann.org>
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.1082)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 31 Jan 2011 17:36:51 -0000

Thanks - yes that makes it clear and I like the way IANA handles all of this.

On Jan 31, 2011, at 9:55 , Michelle Cotton wrote:

> Cullen,
> 
> We do have some technical expertise within the IANA staff, however our
> expertise is more aligned with the process of creating and maintaining
> registries.  Part of that includes relying on the experts that the IESG
> designates to make the decisions for requests that utilize the "Expert
> Review" policy in RFC 5226.
> 
> In the past, if there is strong disagreement from an expert and the
> requester disagrees, we have brought the Transport Area Directors into the
> communications to see if all parties can come to an agreement.  In almost
> all cases, this is where a final decision is made.  If that set of folks can
> not come to a conclusion, we then would default to going to the IESG.  With
> all requests, if there is any uncertainty as to what decision should be
> made, we go to the IESG for guidance.
> 
> We do rely on the technical expertise of the appointed experts for all
> registries, but we ALWAYS have the possibility to seek guidance form the
> IESG.
> 
> I don't believe we have ever had an official appeals with ports (Knocking on
> wood really hard!).
> 
> Does that help?
> 
> --Michelle
> 
> 
> 
> On 1/31/11 8:33 AM, "Cullen Jennings" <fluffy@cisco.com> wrote:
> 
>> 
>> So IANA has a huge amount of technical expertise and takes maintaing the
>> registries very seriously. I've seen them catch technical mistakes that made
>> all the way through WG and IESG review. I've got huge respect for technical
>> competence of IANA and in particular Michelle. So I'm not questions that but
>> I don't recall seeing them override an expert on a technical issue. I'd be
>> happy to hear of examples but lets consider the example I am actually
>> concerned about here.
>> 
>> I put in a request for a latency sensitive protocol that uses DTLS and request
>> a different port for the secure version. Joe as expert review says we should
>> redesign the protocol to use something like STARTLS and run on one port. I
>> assert, with very little evidence, that will not meet the latency goals of the
>> protocol. Joe does not agree.
>> 
>> So Michelle, in that case, would you be willing to override Joe? I'm sure you
>> would be willing to help facilitate any conversations, bring in other people
>> such as ADs that can help etc. I was sort of working on the assumption that
>> you would not override Joe in this case and the the only path forward would be
>> an appeal to Lars but perhaps that is just a bad assumption on my part.
>> Appeals are really the worst way possible to resolve things. I have a hard
>> time imagining that IANA would want to engage in a technical discussion to
>> resolve this and instead relies on the expert reviewer. I'll note that the
>> expert review may report to IANA but they are selected by and replaced by the
>> IESG. 
>> 
>> The important point here is that I really don't care if it is Joe or IANA that
>> is saying no - I think this document should be clear that this BCP can not be
>> used as grounds for rejecting the request for a second port for security.
>> 
>> 
>> 
>> On Jan 30, 2011, at 12:09 , Michelle Cotton wrote:
>> 
>>> David has said this well.  Thank you.
>>> 
>>> Please let me know if there are any other questions.
>>> 
>>> --Michelle
>>> 
>>> 
>>> 
>>> On 1/30/11 10:52 AM, "David Conrad" <drc@virtualized.org> wrote:
>>> 
>>>> Cullen,
>>>> 
>>>> On Jan 29, 2011, at 8:54 PM, Cullen Jennings wrote:
>>>>>> AFAICT, the experts team reports to IANA. We make recommendations to
>>>>>> them. They are the ones who have the conversation with the applicant.
>>>>>> They can take our advice or not - that's their decision.
>>>>> 
>>>>> I think you are pretty misrepresenting the situation. My impression of the
>>>>> reality of the situation is that if the IANA did not like the advice of the
>>>>> expert reviewer, they might ask the AD to override but short of that they
>>>>> pretty much do whatever the expert says.
>>>> 
>>>> 
>>>> Joe is closer. 
>>>> 
>>>> In general, IANA staff are not technical experts in any of the wide variety
>>>> of
>>>> areas for which they are asked to provide registry services.  As such, they
>>>> rely on technical experts to provide input/advice/recommendations.  In the
>>>> past, there were some very rare cases in which the advice provided by the
>>>> technical experts was deemed insufficient and IANA staff looked to the ADs
>>>> or
>>>> the IESG for additional input.  However, at least historically, IANA staff
>>>> viewed the maintenance of the registries as their responsibility (at the
>>>> direction of the IESG), not the technical experts' responsibility. I would
>>>> be
>>>> surprised if this had changed.
>>>> 
>>>> Regards,
>>>> -drc
>>>> 
>>>> _______________________________________________
>>>> Ietf mailing list
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>> 
>> 
>> 
>> Cullen Jennings
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>> 
>> 
> 


Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html