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

Richard Barnes <rlb@ipv.sx> Fri, 11 April 2014 19:35 UTC

Return-Path: <rlb@ipv.sx>
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 738541A03BD for <salud@ietfa.amsl.com>; Fri, 11 Apr 2014 12:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 BcQOFWcZ4FbP for <salud@ietfa.amsl.com>; Fri, 11 Apr 2014 12:35:45 -0700 (PDT)
Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) by ietfa.amsl.com (Postfix) with ESMTP id C38B21A02D4 for <salud@ietf.org>; Fri, 11 Apr 2014 12:35:45 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id l6so6729476oag.11 for <salud@ietf.org>; Fri, 11 Apr 2014 12:35:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1QHNT8EI+q2WC0edgDCBEfvRFZfdBHjRuhfppaNIoI8=; b=Z0A0NFcK5cY5dKETCxHCaLAqXgiiyNTapzXIYyjOi05PDkslw62vm6Y0uxZBY2IWTC 6nJw97tcTzNl5mLL1pzKDJJXyT+itYFot3GpkRCMTouy7tAkY0guWK7cZ3dM7jX9MrPh A3Dsuz1KegnbBeEa4Kz0dB2+7NUXdE9bwPc+p/jWyFkf188KrmW+nwQoLkntxpPAFZ68 IxWkPJ03bGIhPBgUj3vJly1bo9aQQshnfxsd801oO8DZsaGyEfcEBj4S9MPf55yJXZVH XAMzlYQSbuletgFNxMPC/C0NKrzf9amUaKwryY1t3/pvZKg0Y8beDZ5mFvpnd/1sGWN5 WxMQ==
X-Gm-Message-State: ALoCoQlha3Z1wyTta+k8+mYylByBgC5rbweeQUPfcrSZ3uYhJ3tQwKgzKg6+1c54Bg7ILkJKoU2G
MIME-Version: 1.0
X-Received: by 10.60.141.70 with SMTP id rm6mr21059862oeb.27.1397244944378; Fri, 11 Apr 2014 12:35:44 -0700 (PDT)
Received: by 10.60.136.231 with HTTP; Fri, 11 Apr 2014 12:35:44 -0700 (PDT)
In-Reply-To: <201404111920.s3BJKelZ012894@hobgoblin.ariadne.com>
References: <CAL02cgR9SAtq3hxck1zkJmUYOSqNfPDQzZPYX5ztpWNTOnYfYQ@mail.gmail.com> <201404111920.s3BJKelZ012894@hobgoblin.ariadne.com>
Date: Fri, 11 Apr 2014 15:35:44 -0400
Message-ID: <CAL02cgSx2p+XCNNcp39GrKvhQaVMq3nr=rGg+vGnFRAWFuPS7w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=047d7b33c8fa9303d104f6c970c6
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/cPihRZpS42H2SCp4cpbnQaQ-IdA
Cc: draft-ietf-salud-alert-info-urns@tools.ietf.org, salud@ietf.org
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 19:35:50 -0000

On Fri, Apr 11, 2014 at 3:20 PM, Dale R. Worley <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
>