IETF Logo Mail Archive

Re: [Gen-art] Gen-ART review of 04 draft-ietf-appsawg-http-problem-01

Jari Arkko <jari.arkko@piuha.net> Thu, 17 December 2015 13:02 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97BD1B2C75 for <gen-art@ietfa.amsl.com>; Thu, 17 Dec 2015 05:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, T_RP_MATCHES_RCVD=-0.01] 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 9epgVPYBJ6_G for <gen-art@ietfa.amsl.com>; Thu, 17 Dec 2015 05:02:18 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 60D0D1B2C63 for <gen-art@ietf.org>; Thu, 17 Dec 2015 05:02:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ABF1B2CCBF; Thu, 17 Dec 2015 15:02:14 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z64-KenqW9Pt; Thu, 17 Dec 2015 15:02:14 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 01CAF2CCAE; Thu, 17 Dec 2015 15:02:13 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_2F7526BD-B222-47D8-999E-05DEED32C752"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5.1
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA6BEAB07A@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 17 Dec 2015 15:02:14 +0200
Message-Id: <922CCCE8-B1CE-44CA-AB85-E36652E1A00E@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA6BEA9E49@AZ-FFEXMB04.global.avaya.com> <565D5AAB.2040109@dret.net> <9904FB1B0159DA42B0B887B7FA8119CA6BEAB07A@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/MzjjoXiCbiDAIYVNOSG84BWIEf4>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-appsawg-http-problem.all@tools.ietf.org" <draft-ietf-appsawg-http-problem.all@tools.ietf.org>, Erik Wilde <erik.wilde@dret.net>
Subject: Re: [Gen-art] Gen-ART review of 04 draft-ietf-appsawg-http-problem-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2015 13:02:23 -0000

Thanks for the review, Dan! Erik, is there anything in the clarification that would be beneficial for future readers? (Just asking, not suggesting.)

I have balloted no-obj.

Jari

On 01 Dec 2015, at 12:28, Romascanu, Dan (Dan) <dromasca@avaya.com> wrote:

> Hi,
> 
> Makes sense. Thanks for the clarification.
> 
> Regards,
> 
> Dan
> 
> 
>> -----Original Message-----
>> From: Erik Wilde [mailto:erik.wilde@dret.net]
>> Sent: Tuesday, December 01, 2015 10:31 AM
>> To: Romascanu, Dan (Dan); General Area Review Team
>> Cc: draft-ietf-appsawg-http-problem.all@tools.ietf.org
>> Subject: Re: Gen-ART review of 04 draft-ietf-appsawg-http-problem-01
>> 
>> On 2015-11-30 14:31, Romascanu, Dan (Dan) wrote:
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.tools.ietf.or
>>> g_area_gen_trac_wiki_GenArtfaq&d=BQID-
>> g&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4d
>>> 
>> zGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=4RJRXp2cq8Xy_5qOfh6O
>> emlR2tw
>>> Pw7BGuM3S8hPxYf8&s=Y0uKQ8c94in5AWFrviUQeeRYogDlW-
>> ZvW60mKhRuaVs&e=
>>> Document: draft-ietf-appsawg-http-problem-01
>>> Reviewer:  Dan Romascanu
>>> Review Date: 11/30/15
>>> IETF LC End Date: 12/4/15
>>> IESG Telechat date:
>>> Summary: Ready (with one clarification question).
>>> 
>>> Minor issues:
>>> 
>>> One question which may be a matter of clarification rather than an issue:
>>> 
>>> In Section 3:
>>> 
>>> ØIf such additional members are defined, their names SHOULD start with
>>> a letter (ALPHA, as per [RFC5234]) and SHOULD consist of characters
>>> from ALPHA, DIGIT, and "_" (so that it can be serialized in formats
>>> other than JSON), and SHOULD be three characters or longer.
>>> 
>>> What is the rationale here for the SHOULDs? What are the exception
>>> cases that require using SHOULD rather than MUST in this paragraph?
>> 
>> at least part of the reason was that the XML serialization would not be able to
>> deal with names starting with numbers (because of XML's naming rules), and
>> that this should be taken into account when using additional members.
>> 
>> on the other hand, the JSON serialization is meant to be the normative one,
>> which means that this XML constraint should not mean that any JSON using
>> legal JSON names for new members should be considered invalid, even if the
>> names do not conform to XML's naming rules.
>> 
>> mark, am i recalling this correctly? thanks,
>> 
>> dret.
>> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

v2.23.0 | Report a Bug | By Email