Re: draft-duerst-iana-namespace-00.txt

To: "Ned Freed" <ned.freed at mrochek.com>
Subject: Re: draft-duerst-iana-namespace-00.txt
From: "Tim Bray" <tbray at textuality.com>
Date: Sun, 2 Mar 2008 17:49:37 -0800
Cc: Julian Reschke <julian.reschke at gmx.de>, Tony Finch <dot at dotat.at>, ietf at ietf.org
Delivered-to: ietfarch-ietf-web-archive at core3.amsl.com
Delivered-to: ietf at core3.amsl.com
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=8U7ldveF4FRCeU6wSjXZW0pzhLTSX1RGucdFVZRZJWc=; b=QKmI7QDYzJtvEGUaj5a20p3KUmHzI+hVbmdDzIX4qAwJqcrnqUYABJT7hgBp3YjhPFI2G2TiWS9CMR0dIVAtlXZL1usijVGPvraA6vyD0sfSgBVxG1Qb6dvb/NrVcGe0KQ64sQod0m3NeWEt4xmrCLr4Vd8qqypjNUX35HtOv4I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=MuZEgvUVQRM4DjSooeTiQ3iVvK6cqu1dJOFroV/9j9zt99Iu6hFN6yBqvrPEF60+lX/9x3kI+Cw+L/sNeCUOc9efhXwHaSyP28K08IOV+upbTl8N1bqdAjCTX0oY/9XPO0aCTQPmBDdxCdEjuYzkrtrKHO5G0Ln9eg0WdduHOs4=
In-reply-to: <01MRY8ZTDY68000RLZ at mauve.mrochek.com>
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <alpine.LSU.1.00.0803022045470.30472 at hermes-1.csi.cam.ac.uk> <47CB13F4.8090207 at gmx.de> <01MRY8ZTDY68000RLZ at mauve.mrochek.com>
Reply-to: tbray at textuality.com
Sender: ietf-bounces at ietf.org

On Sun, Mar 2, 2008 at 3:23 PM, Ned Freed <ned.freed at mrochek.com> wrote:
>  > Contrary to that, XML processors do not resolve namespace URIs, they are
>  > purely used as identifiers.
>
>  That's certainly how things are supposed to work. It may or may not be how they
>  actually work.

I agree with Ned that the Security considerations or some other piece
of the doc should explicitly cover this issue.  -Tim
_______________________________________________
IETF mailing list
IETF at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- Re: draft-duerst-iana-namespace-00.txt
  - From: Julian Reschke

References:
- draft-duerst-iana-namespace-00.txt
  - From: Tony Finch
- Re: draft-duerst-iana-namespace-00.txt
  - From: Julian Reschke
- Re: draft-duerst-iana-namespace-00.txt
  - From: Ned Freed

Prev by Date: Re: draft-duerst-iana-namespace-00.txt
Next by Date: Re: draft-duerst-iana-namespace-00.txt
Previous by thread: Re: draft-duerst-iana-namespace-00.txt
Next by thread: Re: draft-duerst-iana-namespace-00.txt
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: draft-duerst-iana-namespace-00.txt

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.