Re: [dispatch] Conceptual proposal for extensibility of Alert-Info URNs
Paul Kyzivat <pkyzivat@cisco.com> Thu, 17 June 2010 20:13 UTC
Return-Path: <pkyzivat@cisco.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E93143A6B10 for <dispatch@core3.amsl.com>; Thu, 17 Jun 2010 13:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.207
X-Spam-Level:
X-Spam-Status: No, score=-10.207 tagged_above=-999 required=5 tests=[AWL=0.392, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 s-zkbMECSERD for <dispatch@core3.amsl.com>; Thu, 17 Jun 2010 13:13:13 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 55E3C3A68CB for <dispatch@ietf.org>; Thu, 17 Jun 2010 13:13:13 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKweGkxAZnwM/2dsb2JhbACeenGnW5o5hRoE
X-IronPort-AV: E=Sophos;i="4.53,433,1272844800"; d="scan'208";a="122716503"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 17 Jun 2010 20:13:17 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5HKDHCM001468; Thu, 17 Jun 2010 20:13:17 GMT
Message-ID: <4C1A81DD.9060400@cisco.com>
Date: Thu, 17 Jun 2010 16:13:17 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B21FD73619B@DC-US1MBEX4.global.avaya.com> <AANLkTik6DISW4wY-q4yoJsOfuRk_dWsr-_N_iKC9vy6x@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B21FD7361A2@DC-US1MBEX4.global.avaya.com> <AANLkTiksRlgdu7HIjSbPqq6u-XM-wtbnlX3U9a3Nerb8@mail.gmail.com> <AANLkTimrLwQklCZG31MT19ddULanpOozJe_z2Dz4rvRY@mail.gmail.com>, <4C1A26AE.2060401@cisco.com> <CD5674C3CD99574EBA7432465FC13C1B21FD7361AF@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21FD7361AF@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] Conceptual proposal for extensibility of Alert-Info URNs
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 20:13:18 -0000
I don't feel especially strongly one way or the other regarding the multiple URNs vs. single URN issue. Thanks, Paul WORLEY, Dale R (Dale) wrote: > From: dispatch-bounces@ietf.org [dispatch-bounces@ietf.org] On Behalf Of Paul Kyzivat [pkyzivat@cisco.com] > >> I don't see a problem there. In the general case, if there are multiple >> URIs then the recipient has to decide how to rationalize them into >> something to be done. So what is wrong with giving some guidance in that >> regard? > > We could do that, but it seems to me to be opening a can of worms, in > that the guidance would be (in the general case) how to rationalize an > arbitrary set of URIs. If we limit the rationalization process to the > elements of a single URN of a particular namespace, the problem > becomes simpler. > >> Requiring all the categories to be specified in one URN has the downside >> that all category values need to be standardized as part of a single URN >> spec. > > Strictly speaking, you don't have to define the entire set of standard > categories in one RFC. You do need some sort of registry for them and > their standardized values, but you can extend the registry with new > RFCs. Of course, the vendor-specific extensions aren't cataloged > anywhere. > >> Conversely, consolidating multiple URNs gives the potential to >> define a new category via an entirely new URN scheme. (I guess we >> should discuss if that is a good thing or a bad thing.) > > I'd vote for considering that to be a bad thing. > > Dale >
- [dispatch] Conceptual proposal for extensibility … WORLEY, Dale R (Dale)
- Re: [dispatch] Conceptual proposal for extensibil… Paul Kyzivat
- Re: [dispatch] Conceptual proposal for extensibil… Laura Liess
- Re: [dispatch] Conceptual proposal for extensibil… Paul Kyzivat
- Re: [dispatch] Conceptual proposal for extensibil… Laura Liess
- Re: [dispatch] Conceptual proposal for extensibil… Paul Kyzivat
- Re: [dispatch] Conceptual proposal for extensibil… WORLEY, Dale R (Dale)
- Re: [dispatch] Conceptual proposal for extensibil… Paul Kyzivat
- Re: [dispatch] Conceptual proposal for extensibil… Peter Saint-Andre
- Re: [dispatch] Conceptual proposal for extensibil… Paul Kyzivat
- Re: [dispatch] Conceptual proposal for extensibil… Peter Saint-Andre