IETF Logo Mail Archive

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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 01 December 2015 10:28 UTC

Return-Path: <dromasca@avaya.com>
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 EA7641B3AB4 for <gen-art@ietfa.amsl.com>; Tue, 1 Dec 2015 02:28:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.91
X-Spam-Level:
X-Spam-Status: No, score=-8.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-5, 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 ASZbOfxPdQOt for <gen-art@ietfa.amsl.com>; Tue, 1 Dec 2015 02:28:20 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21F051B3AB3 for <gen-art@ietf.org>; Tue, 1 Dec 2015 02:28:19 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2D+BABBP8ZV/xUHmMZbGQEBAYJTLFRpBqluBpM/ggSFeQKBJjkTAQEBAQEBAYEKhCMBAQEBAxJnDAQCAQgNBAMBAQEBCgsSBzIUCQgCBAENBQgaiAwBDKxsoD4BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIYfhTKEWDEHBgSDDoEUBY0Oh30BhQGQWpEEFw+CDhyBU28BAYFGgQQBAQE
X-IPAS-Result: A2D+BABBP8ZV/xUHmMZbGQEBAYJTLFRpBqluBpM/ggSFeQKBJjkTAQEBAQEBAYEKhCMBAQEBAxJnDAQCAQgNBAMBAQEBCgsSBzIUCQgCBAENBQgaiAwBDKxsoD4BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIYfhTKEWDEHBgSDDoEUBY0Oh30BhQGQWpEEFw+CDhyBU28BAYFGgQQBAQE
X-IronPort-AV: E=Sophos;i="5.15,634,1432612800"; d="scan'208";a="131515823"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Dec 2015 05:28:17 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 01 Dec 2015 05:28:14 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Tue, 1 Dec 2015 05:28:13 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Erik Wilde <erik.wilde@dret.net>, General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART review of 04 draft-ietf-appsawg-http-problem-01
Thread-Index: AQHRLBLLtG8NseLFvke+ufYIZkipap617asg
Date: Tue, 01 Dec 2015 10:28:13 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BEAB07A@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA6BEA9E49@AZ-FFEXMB04.global.avaya.com> <565D5AAB.2040109@dret.net>
In-Reply-To: <565D5AAB.2040109@dret.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/4EBDCH6liruodo1EZ-hSuTefDRY>
Cc: "draft-ietf-appsawg-http-problem.all@tools.ietf.org" <draft-ietf-appsawg-http-problem.all@tools.ietf.org>
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: Tue, 01 Dec 2015 10:28:22 -0000

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.
>

v2.29.0 | Report a Bug | By Email | System Status