Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?

Joe Touch <touch@isi.edu> Mon, 22 August 2011 16:04 UTC

Return-Path: <touch@isi.edu>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5539321F89B8; Mon, 22 Aug 2011 09:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.944
X-Spam-Level:
X-Spam-Status: No, score=-102.944 tagged_above=-999 required=5 tests=[AWL=-0.945, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h+9npu9+nWEf; Mon, 22 Aug 2011 09:04:38 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id E66EB21F87F0; Mon, 22 Aug 2011 09:04:37 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p7MG5QRT016155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Aug 2011 09:05:26 -0700 (PDT)
Message-ID: <4E527E46.7060002@isi.edu>
Date: Mon, 22 Aug 2011 09:05:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
References: <AANLkTimq3hcdK7-f_Pa9sWJJOTzF_GBLcYu36sB3WszN@mail.gmail.com><CAL9jLaaVbmExEM2ZwBf5Ur6aRbBayxX13xGBL27r-svOmC3Wvg@mail.gmail.com><001801cc60bb$19329d00$4001a8c0@gateway.2wire.net> <CAL9jLabhV7AFNnZkgdAF-iK2Pcuz0_3F8Qm8aygjrDk8qRjZdg@mail.gmail.com> <002801cc60c9$1fe9a2c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <002801cc60c9$1fe9a2c0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Christopher Morrow <christopher.morrow@gmail.com>, sidr-chairs@ietf.org, sidr@ietf.org
Subject: Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 16:04:38 -0000

On 8/22/2011 5:42 AM, t.petch wrote:
...
> Oddly, 'CONTACT' there is a person? or a WG? a 'person' seems
> non-scalable in a number of dimensions. :(
> <tp>
> Chris
>
> CONTACT can be a WG, the ietf or iesg, or even a person.

Contact is always a person. It can be a role (WG-chair email, IETF 
chair, etc.), but it's always a person -- typically the person who 
issues the request for the port, FWIW.

> My thinking was, be prepared for this to come back to us with a request for
> information, rather than spin a new draft; I suspect there will be other
> requests as
> well.

The doc needs to have sufficient information for IANA handling of the 
request, but the info in the doc on that point can change if needed 
(e.g., it's not unusual to ask for a port number and have the final RFC 
text include that value, which is assigned before AUTH48).

> I have been waiting for a port request to appear since the iana draft was
> approved and have not seen one - this may be the first.

Port requests for IETF docs typically happen during the final 
assignment, and are generated automatically from the IANA actions 
portion of the doc.

> The port registry is one of those that IANA has converted to XML rendering it
> almost unusable:-(

It would be useful to know (off-list if desired) why you have this view; 
the conversion was intended to make the information more useful to 
programs (e.g., than 'screen scraping'), more complete, and sortable on 
each field to show relationships more clearly.

Joe