IETF Logo Mail Archive

Re: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-16.txt

"Roman D. Danyliw" <rdd@cert.org> Thu, 17 March 2016 19:13 UTC

Return-Path: <rdd@cert.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B11E912DA70 for <mile@ietfa.amsl.com>; Thu, 17 Mar 2016 12:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 gqwhrYEaKxJi for <mile@ietfa.amsl.com>; Thu, 17 Mar 2016 12:13:36 -0700 (PDT)
Received: from shetland.sei.cmu.edu (shetland.sei.cmu.edu [192.58.107.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E74312D666 for <mile@ietf.org>; Thu, 17 Mar 2016 12:13:36 -0700 (PDT)
Received: from pawpaw.sei.cmu.edu (pawpaw.sei.cmu.edu [10.64.21.22]) by shetland.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u2HJDZmP012164; Thu, 17 Mar 2016 15:13:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1458242015; bh=12prAPhgjri18us+qJ0ZO100iC5XHuj5A9qHoDk8ENc=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=MGWz4GGoHXGerPgmVXlO4Oe9t5ncpvMWrpkuq1FFajfYLAg1H28vpUJJvxfFfd9JE qkDdlQAmGJQzvl32W0LHtcq0ukLHbyXkjoFmP+Qvg8A0IiuQL0Yu3xaB45Q16q7gLd fc+1NIXamB9lqvRrJZPFRi0iZthMPNp7ODwTtPCA=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by pawpaw.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u2HJCuga001650; Thu, 17 Mar 2016 15:12:56 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0266.001; Thu, 17 Mar 2016 15:12:56 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Thread-Topic: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-16.txt
Thread-Index: AQHRXT91TJA3LDC0mk2tekVZ52U1nZ8YDBZAgAk4SoCAB7+HAIA1O5Cw
Date: Thu, 17 Mar 2016 19:12:56 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD96E9730@marathon>
References: <20160201220552.16506.51013.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD969F185@marathon> <DBCB2C3E-1AF3-44EB-BBF5-A3B0A46CAF96@isode.com> <56BE0D04.5090307@isode.com>
In-Reply-To: <56BE0D04.5090307@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/QvLW15d6HPRUFHwsEodvEKpvImk>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-16.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2016 19:13:41 -0000

Hi Alexey!

Thanks for the feedback.

> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
>
> In 2.17:
> 
> formatid might need a bit more details. Can you provide some examples?

This @formatid is a holdover from the original RFC5070.  It is an opaque identifier that an implementer could use to provide guidance on how to parse this extension.

I'm struggling to come up with a good use case, but it would work as follows:

<Extension name="custom field1" dtype="string" meaning="explanation1" formatid="string-type1">
<Extension name="custom field2" dtype="string" meaning="explanation2" formatid="string-type2">

The parser would know to process "custom field1" as a "string-type1" and "custom field 2" as a "string-type2".

Why the format information couldn't be inferred from @name assuming they are uniquely assigned; or an enumerated value set with @ext-dtype="string-type1 or string-type2" isn't clear.  

Remove?

> In 3.9.4:
> 
> When one would use "direct" or when "mobile"? Is "direct" referring to a
> landline number or something else?

It is referring to a landline/wireline phone.  I can see the confusion so this enumerated value has been renamed to "wired" in -17.
 
> In 3.21:
> 
> In EmailHeaderField description: I don't know what is "SMTP header field". I
> think you should revert the change to make it "email header field" again.

Good point.  Corrected in -17.

> Also, it should be "zero or more", not "zero or one".

Corrected in -17.

> In 3.25.1:
> 
> FileType - this is just media type name, right?

Yes.  More specifically the "Template" column of http://www.iana.org/assignments/media-types/media-types.xhtml.

Roman

v2.23.0 | Report a Bug | By Email