Re: [salud] AD review of draft-ietf-salud-alert-info-urns-12

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 11 April 2014 20:12 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A29F1A03A8 for <salud@ietfa.amsl.com>; Fri, 11 Apr 2014 13:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fli2VzEIs7xF for <salud@ietfa.amsl.com>; Fri, 11 Apr 2014 13:12:11 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3E51A0767 for <salud@ietf.org>; Fri, 11 Apr 2014 13:12:02 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta06.westchester.pa.mail.comcast.net with comcast id obtC1n00B0vyq2s56kC0kD; Fri, 11 Apr 2014 20:12:00 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta05.westchester.pa.mail.comcast.net with comcast id okC01n00m3ZTu2S3RkC0j1; Fri, 11 Apr 2014 20:12:00 +0000
Message-ID: <53484C90.9050905@alum.mit.edu>
Date: Fri, 11 Apr 2014 16:12:00 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: salud@ietf.org
References: <CAL02cgR9SAtq3hxck1zkJmUYOSqNfPDQzZPYX5ztpWNTOnYfYQ@mail.gmail.com> <201404111920.s3BJKelZ012894@hobgoblin.ariadne.com> <CAL02cgSx2p+XCNNcp39GrKvhQaVMq3nr=rGg+vGnFRAWFuPS7w@mail.gmail.com>
In-Reply-To: <CAL02cgSx2p+XCNNcp39GrKvhQaVMq3nr=rGg+vGnFRAWFuPS7w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397247120; bh=loz4WbCle1JfuWZvhxKy/u4VrvGD4i5+Nf+qrpWnOHE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZM49NHL3cBNrMkQWMbcTFdXqgwifZWpWwEGETsmEk5KALNmFnrVjzsYPJnlOykXyp 2V20qq78Wz28tIuSgdx6BVlPQ75Uvvdn5UKNhRowau8G1CR41XdDiMHUI1uVIfv078 ynAEnkH98qWRsgtn9Z+el+CVJyCPssOkRDOIgXk3XM6OnM6XhTETdnxd6T91CeC4ru 43B3wJE+3LOAlLSXXopWjo53ZXgzxiNZQaCOJcqgPO6cYdGVD0jzm49+pdbvhIiJ6T YfnAtlUYUtysgFkO1Wfl6kd9oR7NgyPzETZwcBrfz+iEjorppUEKDdOkhy/XiSfm8+ b5gmxhKfL12ZA==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/o1sSo5FxRPhoRzggMy4hjupsHY4
Subject: Re: [salud] AD review of draft-ietf-salud-alert-info-urns-12
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud/>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 20:12:13 -0000

Richard,

Following up on what Dale said - we originally didn't have any of the 
date stuff. We were "forced" to add it, for reasons Dale explained, by 
the URN "police". There was quite a lot of thought and effort put into 
the details of how the semantics are specified, and on the syntax, to 
make it as convenient as possible to use. (E.g., what the defaults are.)

	Thanks,
	Paul

On 4/11/14 3:35 PM, Richard Barnes wrote:
> On Fri, Apr 11, 2014 at 3:20 PM, Dale R. Worley <worley@ariadne.com
> <mailto:worley@ariadne.com>> wrote:
>
>      > From: Richard Barnes <rlb@ipv.sx>
>      >
>      > I have reviewed this document in preparation for IETF LC.  Thanks
>     for a
>      > clearly written document!  I especially liked the style of the
>     Terminology
>      > section.  I've requested LC, and a few comments to address along
>     with any
>      > LC comments are below.
>
>     [as chair]
>
>     Many thanks!
>
>     [as an author]
>
>     We will review your comments carefully.
>
>     I'll start off with the one I can give an immediate answer to:
>
>      > It's not clear to me why you need all the date machinery in
>     provider IDs.
>      > This things are ephemeral -- why not just use the org that has
>     the domain
>      > now?
>
>     The problem is that these are URNs and so their meanings, once set,
>     have to be fixed for all time.  That point was raised vividly by the
>     URN people.  Adding the date to a domain name gives it a
>     time-invariant meaning.
>
>     And though the "visible" use of an alert-info URN is transient, from
>     the caller to the callee, both the caller and the callee keep a list
>     of the alert-info URNs that they understand and the meanings that they
>     attach to them.  And this is telephony equipment, which can have a
>     lifetime of over a decade.  So you don't want the expiration of some
>     company's domain registration to require that all the phones that know
>     of their private extension URNs to have to be reprogrammed.
>
>
> Fair enough.  Just wondering if we could simplify things, but it sounds
> like not.  Thanks!
>
> --Richard
>
>
>     Dale
>
>
>
>
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>