Re: [apps-discuss] apps-team review of draft-ietf-sidr-ghostbusters-09

Barry Leiba <barryleiba@computer.org> Tue, 13 September 2011 18:09 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A20321F8B73; Tue, 13 Sep 2011 11:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.007
X-Spam-Level:
X-Spam-Status: No, score=-103.007 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 ObYdg3lFIi2h; Tue, 13 Sep 2011 11:09:18 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC4821F8B21; Tue, 13 Sep 2011 11:09:18 -0700 (PDT)
Received: by yxt33 with SMTP id 33so779772yxt.31 for <multiple recipients>; Tue, 13 Sep 2011 11:11:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jqKViO941gBGG3N9q2bQ+nyLSgrgL2vHHgT01PTOCEw=; b=fGYwM2E3fDoMQSAqhYxoXhaUipTakBLZIe/GT6FbLjexacNyQ+lZ/cZjDt7iOWtz1n npUeZemWsU4Cb7j5om2kADThby7S5FqfM4RokySJ7BfMfi7qdCG80CFLZvesSF43oukB ufMKnXTPSLVm5f2eo4Uk9ZUy+di3BW86smJhM=
MIME-Version: 1.0
Received: by 10.236.73.195 with SMTP id v43mr36570687yhd.5.1315937484619; Tue, 13 Sep 2011 11:11:24 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.203.68 with HTTP; Tue, 13 Sep 2011 11:11:24 -0700 (PDT)
In-Reply-To: <BA1B475C8188F22B71411158@caldav.corp.apple.com>
References: <CALaySJJfu8T6QZ2fQfAwUL32hgOG9kPkioPO+tQZZLNGf12HNQ@mail.gmail.com> <BA1B475C8188F22B71411158@caldav.corp.apple.com>
Date: Tue, 13 Sep 2011 14:11:24 -0400
X-Google-Sender-Auth: 0LUUhyWR98vJHhVroKr2ouqpOso
Message-ID: <CALaySJLJJP2iUFd+ocSDhre1bSYOE13E43P-Q3dh-LTkKAv-fQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: draft-ietf-sidr-ghostbusters.all@tools.ietf.org, iesg@ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] apps-team review of draft-ietf-sidr-ghostbusters-09
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2011 18:09:19 -0000

>> NEW
>>   Per [RFC6350], the BEGIN, VERSION, FN, N, and END properties MUST be
>>   included in a record.  To be useful, one or more of ADR, TEL, and
>>   EMAIL MUST be included.  Other properties MUST NOT be included.
>
> Actually vcard does not require the N property to be present, only VERSION
> and FN in addition to BEGIN/END (as per
> <http://tools.ietf.org/html/rfc6350#section-3.3>).

I took the requirement as one that comes from SIDR, not from vCard...

> Note: vcard v3 used to require that N was present, but that requirement was
> dropped in vcard v4.

...but it's possible that SIDR included "N" because vCard v3 did, and
they didn't know they could drop it now.  Good catch, and they can
decide whether they want it in or not.

> The "Other types MUST NOT be included." is perhaps a little strong. I can
> certainly see situations where it might be useful to have other properties
> such as SOURCE, KIND or REV present. Perhaps that can be changed to a
> "SHOULD NOT"?

It seems clear from the SIDR doc that they very much *want* a MUST
NOT.  For their use case, it's not too strong; it's exactly what they
want in order to keep this record simple.  They could certainly extend
this later, allowing additional properties if such turn out to make
sense for their use case.

Barry