IETF Logo Mail Archive

Re: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard

"Cantor, Scott" <cantor.2@osu.edu> Sun, 07 October 2012 18:19 UTC

Return-Path: <cantor.2@osu.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D0521F8714; Sun, 7 Oct 2012 11:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level:
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id otZ18U5g9Uf8; Sun, 7 Oct 2012 11:19:38 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD6721F8711; Sun, 7 Oct 2012 11:19:37 -0700 (PDT)
Received: from mail98-va3-R.bigfish.com (10.7.14.240) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Sun, 7 Oct 2012 18:19:36 +0000
Received: from mail98-va3 (localhost [127.0.0.1]) by mail98-va3-R.bigfish.com (Postfix) with ESMTP id DEC953C0127; Sun, 7 Oct 2012 18:19:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:164.107.81.43; KIP:(null); UIP:(null); IPV:NLI; H:CIO-KRC-HT03.osuad.osu.edu; RD:cio-krc-ht03.osuad.osu.edu; EFVD:NLI
X-SpamScore: -4
X-BigFish: VPS-4(z551bizbb2dI98dI9371I1432I4015Izz1d77h1202h1d1ah1d2ahzz17326ah8275dhz2fh2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1155h)
Received-SPF: pass (mail98-va3: domain of osu.edu designates 164.107.81.43 as permitted sender) client-ip=164.107.81.43; envelope-from=cantor.2@osu.edu; helo=CIO-KRC-HT03.osuad.osu.edu ; suad.osu.edu ;
Received: from mail98-va3 (localhost.localdomain [127.0.0.1]) by mail98-va3 (MessageSwitch) id 1349633975520260_11442; Sun, 7 Oct 2012 18:19:35 +0000 (UTC)
Received: from VA3EHSMHS031.bigfish.com (unknown [10.7.14.249]) by mail98-va3.bigfish.com (Postfix) with ESMTP id 7AC442A0044; Sun, 7 Oct 2012 18:19:35 +0000 (UTC)
Received: from CIO-KRC-HT03.osuad.osu.edu (164.107.81.43) by VA3EHSMHS031.bigfish.com (10.7.99.41) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 7 Oct 2012 18:19:35 +0000
Received: from CIO-KRC-D1MBX01.osuad.osu.edu ([fe80::450b:35e6:80f4:f3e0]) by CIO-KRC-HT03.osuad.osu.edu ([fe80::2572:c08d:8186:46a4%12]) with mapi id 14.02.0309.002; Sun, 7 Oct 2012 14:19:34 -0400
From: "Cantor, Scott" <cantor.2@osu.edu>
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
Thread-Index: AQHNo+K8KYVCRSrcB0SaMmyLw5NQppeuKM0A
Date: Sun, 07 Oct 2012 18:19:34 +0000
Message-ID: <BA63CEAE152A7742B854C678D949138339A567CD@CIO-KRC-D1MBX01.osuad.osu.edu>
In-Reply-To: <874nm7v92k.fsf@latte.josefsson.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.146.178.47]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2C1BF4FA0905EB4E9D0980C5F6555BAF@osu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: osu.edu
Cc: Sam Hartman <hartmans@painless-security.com>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Oct 2012 18:19:39 -0000

On 10/6/12 12:50 PM, "Simon Josefsson" <simon@josefsson.org> wrote:
>
>Thanks, now I understand better.  I would feel more comfortable if there
>were a precise reference to what "well-formed serialization" means,
>especially since there is a MUST here.  It ought to be possible to
>determine algorithmically whether something conforms or not.  Sometimes
>I get the impression that "well-formed" just refers to syntactical
>correctness, whereas namespace considerations are more semantic.

Actually namespaces extend the notion of syntax in XML, so they're not
just semantic. When you parse while namespace-aware, there are normative
rules for that grammar that include having namespaces declared properly. I
think you probably want to reference the notion of "namespace
well-formed", so my suggested text could be adjusted to include that
instead of just "well-formed".

http://www.w3.org/TR/2009/REC-xml-names-20091208/#Conformance

>If there is a suitable reference to some XML standard, that is probably
>better.

See above.

-- Scott

v2.23.0 | Report a Bug | By Email