IETF Logo Mail Archive

Re: [dsii] Potential IETF Work Items

Melinda Shore <melinda.shore@nomountain.net> Tue, 14 August 2012 15:56 UTC

Return-Path: <melinda.shore@nomountain.net>
X-Original-To: dsii@ietfa.amsl.com
Delivered-To: dsii@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F333621F8644 for <dsii@ietfa.amsl.com>; Tue, 14 Aug 2012 08:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 0PI85EP09Eqd for <dsii@ietfa.amsl.com>; Tue, 14 Aug 2012 08:56:49 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6182121F85AC for <dsii@ietf.org>; Tue, 14 Aug 2012 08:56:49 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 14AD754075 for <dsii@ietf.org>; Tue, 14 Aug 2012 08:56:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=nomountain.net; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=nomountain.net ; b=j1WylPE0SaP8ffBRGOElniq1nCxuo7ZhZW1iZBEM0JPITIHnZssDIrD97k9T ffSRwcoQvmu8UoCJi0Tj7K3P0sbNpxJ/YKRF9EX6xKgibeNpiXHlU6ujkxIdNDwT rlr6INjyBPuaRN+ruDbOc3QrxVLs4TiEgl/VLBFk8rooucU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nomountain.net; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= nomountain.net; bh=6lcL9NTig3CLb5t0ZIgSW7/j+14=; b=J2iL5Q9gFjcrq 9wuK2IQX4XVMFpHAkS8ObPM1XsdsuM8nCZevY/yQw6YH7Q/1S3Ba6Z5A2z/5SYHI BFGLPzW2lpNEsc2hIA1IS8qLTafeD6FRxZDyEbgeXV/jh0FX70GiQ3ZirrPRXPrp ydO8EWj+2UqVgmfuXWTDYU1EVGCKRw=
Received: from spandex.local (66-230-82-208-rb1.fai.dsl.dynamic.acsalaska.net [66.230.82.208]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: melinda.shore@nomountain.net) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id BDE565405B for <dsii@ietf.org>; Tue, 14 Aug 2012 08:56:48 -0700 (PDT)
Message-ID: <502A753F.4010001@nomountain.net>
Date: Tue, 14 Aug 2012 07:56:47 -0800
From: Melinda Shore <melinda.shore@nomountain.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: dsii@ietf.org
References: <E1AB8352-7B89-4D5A-9B36-4872DF105392@vigilsec.com> <7F45CB6F-2FE2-4A25-8A18-C94674489E39@vigilsec.com>
In-Reply-To: <7F45CB6F-2FE2-4A25-8A18-C94674489E39@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [dsii] Potential IETF Work Items
X-BeenThere: dsii@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dsii.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dsii>, <mailto:dsii-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dsii>
List-Post: <mailto:dsii@ietf.org>
List-Help: <mailto:dsii-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dsii>, <mailto:dsii-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 15:56:50 -0000

On 8/14/12 6:16 AM, Russ Housley wrote:
> At the DSII BOF in Vancouver, Andy Maffei gave a list of potential
> work items.  Is there interest in pursuing any of them in the IETF?

I think that given our history with other standards bodies trying to
standardize IP technologies and our reaction to those, it might not be
a terrible idea to tread a little lightly here, and make sure that
the IETF wouldn't be stepping on anybody else's toes.

I'm generally not a fan of bringing this work to the IETF, but if
there really is support for it I think that we do have the expertise
within the organization for working on identifiers and we definitely
do not have the expertise for working on what's basically library
metadata.  I also think that we shouldn't be in the business of
attempting to limit PIDs, because, basically, we can't.

I'm unconvinced that much thought has been given to what sort of
expertise the IETF can bring to bear on any of these questions.

Melinda

-- 
Melinda Shore
No Mountain Software
melinda.shore@nomountain.com

"Software longa, hardware brevis."

v2.23.0 | Report a Bug | By Email