IETF Logo Mail Archive

Re: [calsify] Barry Leiba's Discuss on draft-ietf-calext-eventpub-extensions-12: (with DISCUSS and COMMENT)

Doug Royer <douglasroyer@gmail.com> Thu, 27 June 2019 14:52 UTC

Return-Path: <douglasroyer@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0D9C120167 for <calsify@ietfa.amsl.com>; Thu, 27 Jun 2019 07:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Sf11RojfvyCB for <calsify@ietfa.amsl.com>; Thu, 27 Jun 2019 07:52:58 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78EEC12015F for <calsify@ietf.org>; Thu, 27 Jun 2019 07:52:58 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id f25so1128409pgv.10 for <calsify@ietf.org>; Thu, 27 Jun 2019 07:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=BXfMJuY3QrGhDesxMmtFgd1rfXScFBWARzgLN603ONU=; b=newm5Gib6S5+eUJTIjA41ENgJyTDO1tCA2HxcCJSw0bNQyLMU3SM4sG0vDFTLmzFoP G11J/qzqv6PqCMm6V795ChyjG3WMheSY0hWd38ihv68nzG9QRPbC2x+HsbpmmNGE9wUs sQIY4yrNDw+HAa7c6Q84G7QQ2qbDajdTcFopR5mSzP0/wzjZcewB7Q8gbkbfJbbkyd4G gp9L3f7rX1JEmBp5+mNP18vj4TszdyJ6HnWD7MBLxYR6uj4eNLjSpk88cMiUCy101hvW b8odvj2er9WF6shHz2bpEzWAlleAFaiAJlJ3KAeYUxmwhUCdg6ucI+HtMmGg7KFfs5kH lz1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=BXfMJuY3QrGhDesxMmtFgd1rfXScFBWARzgLN603ONU=; b=NVeVTCJMEVbkE29xG9KSc2pQhKen4UuPxuKEA/bCxJLbuHZp93EOd0rV0XvDP/vb1g lG5ck+zGdCMhfUT/ufR0K2lbGheNj20eCw0ZkpctLO2Hg1D7lwyebeBULeEpO9uC88BZ 0/+E1iMuSQ7YRYQyRuPy+7Uws5XJEfpmBigHNaBsTb/NTBal62hMif7WZNT9Gkvr/u9A CUoN2J7zHHOSGELZxf0b1C+l+bXOPC9iNtOmIwZ+nJ+Vc6CA+zgW/kBj7i60hmh2p46Z EGmXt/wE52x6fZh256tN+hT2LHT0DQ68ejyOVRTG6g4iZNXX+vw2uTSRcb4sUQDARIhO 179A==
X-Gm-Message-State: APjAAAUqNH0ZifFrACqid1hcDniEhjKa46nBjw57NYGhzUfvI+f1982C bEghx+n+sgK4BhyeVIUjwAbW4Cda5DqG
X-Google-Smtp-Source: APXvYqzQTb2g1ZsESc3xANN1ijRnCaCmPC21PGJydru4RPl8mceHvZLF88a1z89/rTNXMuhiLt2/Mg==
X-Received: by 2002:a17:90a:a404:: with SMTP id y4mr6824940pjp.58.1561647177569; Thu, 27 Jun 2019 07:52:57 -0700 (PDT)
Received: from [192.168.1.7] ([174.27.175.146]) by smtp.googlemail.com with ESMTPSA id w22sm2861878pfi.175.2019.06.27.07.52.56 for <calsify@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Thu, 27 Jun 2019 07:52:56 -0700 (PDT)
From: Doug Royer <douglasroyer@gmail.com>
X-Google-Original-From: Doug Royer <DouglasRoyer@gmail.com>
To: calsify@ietf.org
References: <155799446016.19593.5421721957765362252.idtracker@ietfa.amsl.com> <309a7ae1-09fb-137b-a639-f0b04328aeed@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <9382a364-b9e7-b054-1add-19e6553cb130@gmail.com>
Date: Thu, 27 Jun 2019 08:52:55 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <309a7ae1-09fb-137b-a639-f0b04328aeed@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Aivo1YXhMuR8FLSqHADCRNfgdlY>
Subject: Re: [calsify] Barry Leiba's Discuss on draft-ietf-calext-eventpub-extensions-12: (with DISCUSS and COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2019 14:53:00 -0000

On 5/25/19 8:44 PM, Michael Douglass wrote:
>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> Thanks for the work in this document; I think there’s useful stuff here, and I
>> appreciate what it took to put it together.  Two things at the DISCUSS level:
>>
>> — Sections 5.2, 7.1, and 8.1 —
>> Please see BCP 178 (RFC 6648), and then remove x-name and x-prop.  Thanks.
> Removed

Your really limiting *ALL* resources to *ONLY* these: "ROOM", "PROJECTOR", "REMOTE-CONFERENCE-AUDIO",
"REMOTE-CONFERENCE-VIDEO" ? I have seen many more over the years. Such as: Car, Laptop, Cabin, Test-Station, ...

At a more global level. I think that resource type is one of the most free-for-all value types in iCalendar. It is not going to be possible to define what vertical market calendar applications need. The removal of x-name will be ignored (as it is now). I have seen many that do not start with "X-" and are not IANA defined. It started off years ago (before 2445) with a suggestion or example. So examples were added, that became IANA defined. However *MANY* non standard values exist in the WWW wild world.

Would it be more realistic to open it up to any name the user or application needs?
I am guessing that closing it down - will be ignored, as it is now.

Similar with x-prop. Vendors add properties they need in vertical market calendaring applications. They are going to add them. They are going to be seen. So now your going to remove a preferred way and almost invite confusion. Currently an implementation can simply ignore x-whatever. Now it is easy to filter out vendor specific X-PROP properties. It is going to be a mess for an existing implementation to guess if it is vendor specific, or a new IANA defined property that should be preserved. For the most part, they prefix their vendor specific properties with X-, now your removing that restriction?

What was the reasoning for removing them?

Without them, this looks more like a candidate for an FYI-only RFC documentation that describes how a single (or few) vendor does things.

-- 

Doug Royer - (http://DougRoyer.US)
Douglas.Royer@gmail.com
714-989-6135

v2.23.0 | Report a Bug | By Email